CapacityLimitExceeded

[MHakki]

Greetngs;

I mistakenly, created my data warehouse using a trial workspace.  Now I am getting the capcityLimitExceeded every time I access the warehouse.  I can't even download the code so I can import to a new workspace.  There is lots of work in the warehouse, am I needing to start all over again?

Thank yu very much.

[Srisakthi · Accepted solution]

Hi @MHakki ,

Have you scheduled any notebook to run at regular intervals?

Only way to figure out the bottleneck is to by installing Capacity Metrics app and figure out which item is consuming more CUs and try to reduce more CU consumption.

Here is the link to install MS fabric capacity metrics app

https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-install?tabs=1st

Thanks,

Srisakthi

[Anonymous]

Hi @MHakki,

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[Anonymous]

Thankyou, @MohdZaid_ and @Srisakthi  for your responses.

Hi @MHakki 

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solutions provided by @MohdZaid_  and @Srisakthi to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[MohdZaid_ · Accepted solution]

Hey @MHakki  , 

You do not need to start over this is recoverable.

What’s happening is that your warehouse was created in a trial capacity workspace in Microsoft Fabric, and that trial capacity has either expired or reached its limit. When that happens, Fabric blocks compute access to items like Warehouses and Lakehouses, which is why you’re seeing CapacityLimitExceeded and can’t even open or script the warehouse.

The good news is: your data and objects are still there. The issue is compute capacity, not deletion.

Here’s what you can do.

First option (fastest fix): temporarily enable capacity again. If you still have the ability, re-enable a Fabric trial or assign the workspace to an active Fabric capacity (F SKU or P SKU). Once the workspace has active capacity again, you’ll be able to open the warehouse and extract your scripts or deploy it properly to a new workspace.

Second option: ask your Fabric or Power BI admin to move the workspace to an active capacity. In the Admin Portal of Microsoft Power BI, an admin can reassign the workspace to a paid Fabric capacity. Once reassigned, access should return.

Third option (if trial is fully expired and cannot be restored): open a Microsoft support ticket immediately. In many cases, Microsoft can temporarily rehydrate expired trial capacity long enough for you to retrieve your work — but this needs to be done quickly.

Going forward, once you regain access, the safe approach is:

• Script out all Warehouse objects (tables, views, procedures)
• Export notebooks and pipelines
• Recreate the workspace under a proper paid capacity
• Redeploy everything there

Important: CapacityLimitExceeded does not mean your warehouse was deleted. It only means there is no compute available to execute queries.

So no you don’t need to rebuild everything from scratch. You just need capacity reattached to that workspace.

If you tell me whether the trial has fully expired or just hit usage limits, I can guide you on the fastest recovery path.

If this explanation helped, please mark it as the solution so others can find it easily.

If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.

Thanks for being part of the discussion!

[Srisakthi · Accepted solution]

Hi @MHakki ,

Have you scheduled any notebook to run at regular intervals?

Only way to figure out the bottleneck is to by installing Capacity Metrics app and figure out which item is consuming more CUs and try to reduce more CU consumption.

Here is the link to install MS fabric capacity metrics app

https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-install?tabs=1st

Thanks,

Srisakthi