Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi,
I've had a refresh error for a dataflow that contains only three queries. I've checked the credentials and they all seem fine.
I also have other data flows accessing the same data source that are working perfectly fine. Can you please help me to figure out what happened here?
I'll paste here the error I get from the refresh history log and then the queries codes. The first query is the only one that loads to the data flow whilst the other ones have their option "Enable load" unmarked.
Error: Request ID: 313103cb-e96b-0357-13bb-894537de33c5 Activity ID: cb710714-a8a0-4d3f-8802-112c72ee8796
Query Project by stage full:
Solved! Go to Solution.
Sorry, I appreciate you are trying to help but I didn't raise a ticket to Microsoft Support as I spent 2 days with them trying to get this error fixed for another data flow and they couldn't find which step of the query was causing the issue. They said that this issue falls outside the scope of their current support boundaries and that I should seek help from a dev. I ended up deleting the data flow and moving the query somewhere else as I couldn't afford spending more time investigating the error.
Microsoft could improve the error log for data flow refresh as this would save time for the users debug when something breaks i.e. displaying the item that caused the error rather than the back end ids.
I'll close this ticket and mark my last comment as solution but there was no solution whatsoever as I deleted the data flow.
Hi Gerald,
Thanks for replying so fast. No, that's all I get from the refresh history.
Last week I had a similar problem with another data flow that retrieved an error with Request ID and Activity ID. When I contacted Microsoft they said it was an authentication issue but my credentials were fine. In the end, I've found out the connection via SharePoint.Folder was the issue because it timed out and lost credentials before processing the data. So I changed it to fetch data via SharePoint.Contents instead and it worked. For the current Data Flow I'm having errors here, I'm already using SharePoint.Contents so I don't know what else could be the issue here.
Hi @beatrizalbuqu,
Can you post the error message you are getting?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Error: Request ID: 313103cb-e96b-0357-13bb-894537de33c5 Activity ID: cb710714-a8a0-4d3f-8802-112c72ee8796
Hi @beatrizalbuqu ,
Thanks for reaching out to Microsoft Fabric Community and sharing the details.
Since other dataflows using the same SharePoint source are working and the error only shows a Request ID, it could be related to the size of the files or the complexity of transformations in this query.
You might check the file sizes in "POWER BI SOURCES" / MAPPINGS / SCREENDRAGON_DIMENSIONS", temporarily simplify or isolate some of the Expand or Merge steps, or try refreshing with a smaller number of rows to see if it succeeds.
Since the error provides limited information, raising a Microsoft support ticket is recommended so they can investigate the cause in the backend using the Request ID.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @beatrizalbuqu ,
Just checking in to see if your query has been resolved and whether any of the responses were helpful. Otherwise, feel free to reach out for further assistance.
Additionally, could you please confirm whether the issue has been addressed through the support ticket with Microsoft?
If the issue is now resolved, we’d greatly appreciate it if you could share any key insights or the resolution here for the benefit of the wider community.
Thank you.
Sorry, I appreciate you are trying to help but I didn't raise a ticket to Microsoft Support as I spent 2 days with them trying to get this error fixed for another data flow and they couldn't find which step of the query was causing the issue. They said that this issue falls outside the scope of their current support boundaries and that I should seek help from a dev. I ended up deleting the data flow and moving the query somewhere else as I couldn't afford spending more time investigating the error.
Microsoft could improve the error log for data flow refresh as this would save time for the users debug when something breaks i.e. displaying the item that caused the error rather than the back end ids.
I'll close this ticket and mark my last comment as solution but there was no solution whatsoever as I deleted the data flow.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.