CDSA Usage Keeps Rising After Pausing All Triggers – No Burndown, No Response

Hi TayRob16, 
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to tayloramy, for those inputs on this thread.

I understand that seeing CDSA usage continue to increase significantly, even after pausing triggers, can be quite concerning. It is important to note that pausing triggers only prevents new trigger activity it does not affect jobs that were already running, queued, or being retried by other services such as Power Automate, Logic Apps, or service principals. These jobs may continue to consume capacity in the background.

Fabric applies smoothing over a 24-hour window for background workloads. This means you won’t see immediate burndown usage can look “stuck” at 0% even when triggers are paused, because those jobs are still being accounted for gradually.

Open the Capacity Metrics app → Timepoint view to spot which operations and workspaces are consuming the most. https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app 

Cancel any active pipeline runs in the monitor. If the UI will not let you, you can use the pipelineRuns/cancel API. https://learn.microsoft.com/en-in/rest/api/datafactory/pipeline-runs/cancel?view=rest-datafactory-2018-06-01&tabs=HTTP 

Turn off all other entry points that can re-enqueue work things like scheduled semantic model refreshes or external retry loops in Power Automate/Logic Apps.
https://learn.microsoft.com/en-in/power-bi/connect-data/refresh-data 

Avoid using “pause capacity” to flush usage, pausing actually sums up all smoothed/overage usage immediately, which can make the spike look worse in your bill.
1. https://learn.microsoft.com/en-us/fabric/enterprise/pause-resume 
2. https://learn.microsoft.com/en-us/fabric/enterprise/monitor-paused-capacity 

Since you have already logged a support ticket, I would suggest updating it with:
• Screenshots or exports from the Metrics app (top operations).
• Run IDs and UTC timestamps for any cancelled jobs.
That information will help the support team quickly identify and clear any runaway background workloads.

Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

Thank you for using the Microsoft Fabric Community Forum.