Forum Discussion
Solution SpecialistFabric Dataflow Gen2 – MetadataEvaluationGatewayTimeout
Hi everyone,
We have a Fabric Dataflow Gen2 that is consistently failing with the following error:
MetadataEvaluationGatewayTimeout
We have already checked the following:
- On-premises Data Gateway is Online
- Gateway Windows service is Running
- Gateway VM is healthy
- Manual refresh was attempted, but it failed again with the same error
Since the gateway and VM appear to be working normally, we would like to understand what could be causing the metadata evaluation timeout and what would be the recommended permanent fix.
Has anyone faced this issue before? Could this be related to the source metadata evaluation, gateway processing, or Fabric service-side processing?
Any guidance or troubleshooting steps would be appreciated. Thank you!
Hi Omkar_1712,
Thanks for reaching out to the Microsoft Fabric Community forum.The documented troubleshooting considerations for Dataflow Gen2 point to a few areas worth checking in this scenario.
• Validation/publish time: Microsoft documents a 10-minute limit per query for the validation and publish process. If a query exceeds this limit, the recommendation is to simplify the query or split it across multiple queries/dataflows.
• Gateway version: Dataflow Gen2 requires a currently supported gateway, with at least the last six released gateway versions supported.
• Referenced or staged queries: If the dataflow contains queries that reference other queries or staged data, the gateway may need to access the Dataflow Gen2 staging Lakehouse using TDS over TCP 1433. Microsoft documents that firewall or proxy restrictions blocking this traffic can cause refresh failures.
• Gateway processing: Microsoft also notes that gateways can introduce additional latency and overhead. For complex dataflows, Microsoft recommends separating the gateway-based data movement from subsequent transformation work to reduce the processing performed through the gateway.
Therefore, I would first review the affected query's validation/execution time, check whether referenced or staged queries are involved, verify the gateway version, and confirm the required TCP 1433 connectivity where applicable.
If the query is exceeding the documented 10-minute validation/publish limit, simplifying or splitting the query is the documented approach.
For more details, please refer to the below Official Microsoft documentation
Data Factory limitations overview - Microsoft Fabric | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you.
3 Replies
v-abhinavmuCommunity Support
Hi Omkar_1712,
Thanks for reaching out to the Microsoft Fabric Community forum.The documented troubleshooting considerations for Dataflow Gen2 point to a few areas worth checking in this scenario.
• Validation/publish time: Microsoft documents a 10-minute limit per query for the validation and publish process. If a query exceeds this limit, the recommendation is to simplify the query or split it across multiple queries/dataflows.
• Gateway version: Dataflow Gen2 requires a currently supported gateway, with at least the last six released gateway versions supported.
• Referenced or staged queries: If the dataflow contains queries that reference other queries or staged data, the gateway may need to access the Dataflow Gen2 staging Lakehouse using TDS over TCP 1433. Microsoft documents that firewall or proxy restrictions blocking this traffic can cause refresh failures.
• Gateway processing: Microsoft also notes that gateways can introduce additional latency and overhead. For complex dataflows, Microsoft recommends separating the gateway-based data movement from subsequent transformation work to reduce the processing performed through the gateway.
Therefore, I would first review the affected query's validation/execution time, check whether referenced or staged queries are involved, verify the gateway version, and confirm the required TCP 1433 connectivity where applicable.
If the query is exceeding the documented 10-minute validation/publish limit, simplifying or splitting the query is the documented approach.
For more details, please refer to the below Official Microsoft documentation
Data Factory limitations overview - Microsoft Fabric | Microsoft LearnI hope this helps. Please feel free to reach out if you have any further questions.
Thank you.- v-abhinavmu
Hi Omkar_1712,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you. - v-abhinavmu
Hi Omkar_1712,
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank you