Dataflow Gen 1 failing to refresh - fails with an ambigous error code

[penda_fabric]

I have a dataflow that runs some SQL query on an Azure SQL Database that is scheduled to run 12:30am. The dataflow failed today with an ambigous error like: Error: Request ID: BLAH-BLAH-BLAH Activity ID: BLAH-BLAH-BLAH (I have replaced the actual ID with a dummy id). 

Has anyone come across this? Is there a way I can turn on or a setting to allow a verbose reporting? Because the above error doesn't explain what went wrong. 

[v-priyankata]

Hi @penda_fabric 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@rohit1991 Thanks for the all inputs.

I hope the information shared by the users was helpful. Did you have a chance to try those suggestions? If you still have questions, please don't hesitate to reach out to the community

[v-priyankata]

Hi @penda_fabric  

I wanted to check if you had the opportunity to review the information provided by users. Please feel free to contact us if you have any further questions.

[rohit1991]

Hi @penda_fabric 

Those vague errors with just a Request ID and Activity ID aren’t helpful at all.

Couple of things to try:

• First, check the refresh history sometimes it’ll give a bit more context (like a timeout or auth issue).

• If you're using an on-prem gateway, take a look at the logs they can be more insightful than the Power BI UI.

• Also worth running the same SQL query manually (SSMS or Azure Data Studio) around that 12:30 AM mark  mostly queries time out or hit throttling when the DB is under load.

• Sadly, Gen 1 doesn't have any verbose logging or diagnostics toggle.  You might want to test moving it to Dataflow Gen 2 logging and error handling is much better there.