really high CU usage from Dataflow throttled capacity

[LuukSteenbergen]

Hi,

I recently switched to a F2 capacity in Fabric to migrate some of our reports and warehouses. I created a dataflow for a copy job since I got an error when trying to use a pipeline. so i thought, lets try it with a dataflow. The moment I started this dataflow the capacity shot up to 112% and the cumulative  percentage started rising. This was 24 hours ago. I figured It would slowly go down overtime but the Cumulative percentage in the Burndown table for timerange (fabric capacity metrics app) is now at 264.422% and the burndown percentage is still 0. The report shows that the dataflow is still in progress while the fabric UI says status failed. this ofcourse resulted in the fact that I can't perform any action within the capacity, I cant even delete the dataflow. I tried to cancel the dataflow using the API but to no succes. What do I do in this situation? Thnx

[v-pbandela-msft]

Hi @LuukSteenbergen,

I wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.
If the community member's answer your query, please mark it as "Accept as Solution" and select "Yes" if it was helpful.
If you need any further assistance, feel free to reach out.

Thank you,
Pavan.

[v-pbandela-msft]

Hi @LuukSteenbergen,

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, kindly "Accept  as Solution" and give it a 'Kudos' so others can find it easily.

Thank you.
Pavan.

[Poojara_D12 · Accepted solution]

Hi @LuukSteenbergen 

You're facing an issue where a dataflow operation in your F2 capacity environment in Fabric has failed but continues to consume resources, causing the cumulative capacity usage to rise significantly (264%). This prevents you from performing actions such as deleting the dataflow or managing the capacity effectively. The overconsumption of resources results in a locked state, where you're unable to cancel or manage the dataflow through the Power BI UI or API. To resolve this, first try navigating to the Power BI Service and canceling the refresh in the dataflow if that option appears. If that doesn't work, you can use the Power BI REST API (specifically the Abort Refresh In Group API) to attempt stopping the refresh operation. If these steps fail, reaching out to Microsoft Support is crucial, as they can help terminate the process on the backend and restore normal operations. In the future, to prevent similar issues, regularly monitor capacity metrics, set up resource governance, and ensure all team members follow best practices for running dataflows.

[v-pbandela-msft]

Hi @LuukSteenbergen,

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. If my response has addressed your query, please "Accept  as  Solution" and give a 'Kudos' so other members can easily find it.

Thank you,
Pavan.

[v-pbandela-msft]

Hi @LuukSteenbergen,

Thank you for reaching out in Microsoft Community Forum.

Please follow below steps to solve the Fabric Capacity Overload Issue;

1.Try to pausing the capacity and then resuming it after a few minutes to reset the workload 

    Go to the Microsoft Fabric Admin Portal → Capacity Settings.

2.Check Fabric Capacity Metrics App for other high-consuming workloads that may need to be stopped.

3.Identify and eliminate any long-running queries or failed workloads and try moving the dataflow to another workspace and deleting it from there.

Please continue using Microsoft community forum.

If you found this post helpful, please consider marking it as "Accept as Solution" and give it a 'Kudos'. if it was helpful. help other members find it more easily.

Regards,

Pavan.