Dataflow Gen2 (CI/CD) Refresh Error - MetadataEvaluationGatewayTimeout

[Nasif_Azam]

Hello Guys,

I hope you are all doing well. I am encountering an issue when refreshing my dataflow in Microsoft Fabric. The error message is as follows:

"Something went wrong, please try again later. If the error persists, please contact support."

Error code: MetadataEvaluationGatewayTimeout
Request ID: 2d5e10c7-db82-4cd0-9245-d3a9ea6061c2

Despite multiple attempts, I am unable to resolve the issue.
Has anyone experienced something similar or have any insights on how to troubleshoot or resolve this error?

Any guidance or suggestions would be greatly appreciated!

Thank you in advance for your help.

Best regards,
Nasif Azam

[v-tejrama · Accepted solution]

Hi @Nasif_Azam ,

Thanks for reaching out to the Microsoft fabric community forum.

This error generally indicates a timeout during the metadata evaluation stage of a Dataflow Gen2 refresh, rather than an issue with CI/CD or a temporary service disruption. Before data loading begins, Fabric must connect to the source, validate credentials, resolve the schema, and assess the query structure. If the source query is slow to provide metadata, involves complex logic or joins, uses dynamic parameters that hinder query folding, or is accessed via an outdated or overloaded gateway, this process may exceed the allowed time, resulting in a MetadataEvaluationGatewayTimeout.

Simply re-running the refresh is unlikely to resolve the issue. To confirm, try refreshing the dataflow manually in the Fabric UI with the same settings; if it fails, focus on simplifying the source query, resolving parameters effectively, and ensuring the gateway is updated and functioning properly. Once metadata evaluation completes successfully in the UI, the configuration should also work in CI/CD.

Best Regards,
Tejaswi.
Community Support

[Nasif_Azam]

Hello @v-tejrama,

Thanks for the detailed explanation and guidance.

I followed your suggested approach and updating the on-premises data gateway to the latest version and restarting the gateway which resolved the issue.

Really appreciate you taking the time to explain the root cause and resolution so clearly. This was very helpful.

Best regards,
Nasif Azam