Forum Discussion
really high CU usage from Dataflow throttled capacity
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.
