We recently implemented programmatic pausing and resuming of Microsoft Fabric capacity using the API. While testing this setup with a Power BI embedded report, we noticed an interesting behavior.
When filters are applied to the embedded report and the report is left idle for a few minutes, the Fabric capacity automatically transitions to a paused state. Later, when we try to access the report again, the capacity begins to resume, but during this process, the report throws an error. Once the capacity becomes active, the report refreshes automatically—however, this refresh clears all previously applied filters and resets the report to its default page.
Our goal is to maintain the applied filters even after the capacity resumes.
on:
Accelerate ontology adoption with out-of-the-box i...
on:
DO NOT CONVERT my Workspace to Fabric Free Trial W...
on:
MS Fabric: Manage Connections and gateways with Fo...
on:
CU% over time: Filter by workspace (Capacity Metri...
YSD
on:
Support the SSE protocol as Fabric Eventstream sou...