Evaluation error

[SGRS]

After transforming a dataflow I did a refresh and this message occured: An error occurred while communicating with another service, please try again later. If this problem recurs, please contact support with this message. (Request ID: ad746fc7-80ea-406e-8055-78a8741f8d5b). I can't even start a new query in this flow. 

[v-agajavelly]

Hi @SGRS 
Thanks for confirming that recreating the new dataflow you can able to resolve the issue.
If you still faces any issues please do reach out to the community.
We are happy to assist you.

Thanks.

[v-agajavelly]

Hi @SGRS ,

just checking in were you able to get in touch with Microsoft Support and share the Request ID with them? let me  know if they were able to identify the root cause. It would be great if you could update the thread when you get a chance, as it might help others facing similar issues.

Regards,
Akhil.

[SGRS]

Goodmorning @v-agajavelly ,

Our ICT team sent the Request ID to them but they didn't get the specific cause. I rewrote the dataflow and changed the dataflow ID in the report, so I can still use all visuals. 

[v-agajavelly]

Hi @SGRS ,

Thanks @rohit1991 for taking the time to walk through those steps. Since the quick test worked, it points to something specific in this dataflow rather than a workspace or capacity issue. At this stage, reaching out to Microsoft Support is the right call they’ll be able to check the backend logs for the Request ID and find what’s failing.

Do share back here if they find the root cause, so it can help others facing the same issue

Regards,
Akhil.

[SGRS]

Hi @rohit1991 

Thanks for the try

1. basic refresh after sig out/in - fail; also in other browser

2. quick test: works

3. check credentials: ok

4. Clone dataflow: same result

5. Undo last step: same result

I'll check with MS Support.

[rohit1991]

Hi @SGRS 

The error message suggests that connectivity is failing at some point. Can you try the steps below to troubleshoot and narrow down the cause of the issue?

• Basic refresh : Sign out/in, try again in another browser or in a private window.
• Quick test : In the same workspace, create a brand-new dataflow with just. Save it. If even that fails, it’s a workspace/capacity problem, not your query.

= #table({"Test"}, {{1}})

• Check credentials : In dataflow settings, re-authenticate every data source. If you’re on a gateway, make sure it’s online and mapped right.
• Clone the dataflow : Export to .json (or Save As in Gen2) and re-import. Sometimes the current instance just gets stuck.
• Undo the last step : If the error started right after a change, remove that step and see if it opens. Large merges or certain Web.Contents calls can cause this.

If none of that works, grab the Request ID, Activity ID, and timestamp from the error and send it to Microsoft Support  they can check the backend logs.