Forum Discussion
PBI API limit exceeded error when trying to copy Notebook on Fabric
Hi,
I have a workspace with F4 capacity, where I am running Notebooks and Pipelines. My account itself does not seem to have the same capacity as the one associated with the workspace (my account shows I am on Trial capacity). My guess is that this disparity is because the Workspace capacity is managed by my client's IT services partner, who has attached the capacity to the workspace.
When I tried to copy a Notebook in the workspace, I was hit with "PbiApiError: Failed to invoke PBI API. (HTTP 429)". I am trying to understand what's causing the rate limit. I am still unsure which capacity (whether my workspace's or my account's) is being applied when I do operations in the said workspace.
I'd appreciate if someone could help me figure this out. I can provide more details as needed.
Hi PyyneCST ,
Thank you for the update.
The HTTP 429 error indicates request throttling on the Fabric/Power BI service side. Even though the operation was simply duplicating a Notebook, this action can internally trigger multiple Power BI REST API calls (for example, retrieving metadata, copying artifacts, permissions, and workspace item registration). If several operations occur within a short time window, the service may temporarily enforce throttling.
Currently, the exact request limits for many Fabric operations are not publicly documented, as they can vary depending on factors such as capacity load, concurrent requests, and backend service protection policies. This is why the documentation does not list a fixed limit.
Since the issue resolved automatically, it confirms the throttling was temporary service-side protection rather than a configuration problem with your account or workspace capacity.
If the issue starts occurring frequently, we recommend:
Monitoring capacity metrics for spikes in activity
Avoiding rapid repeated artifact operations (copy/create/update)
Implementing retry logic with backoff when automating Fabric API operationsPlease let us know if the issue reoccurs or if additional details are needed.
Best Regards,
Chaithra E.
7 Replies
- tayloramy
Super User
Hi PyyneCST,
Capacities are attached to workspaces, not to accounts, so all actions in a workspace go against the capacity that the workspace is attached to.
The trial message at the top right just indicates that you have an active trial capacity, not that all your work is being billed to it.
Have you checked capacity metrics at all to see how much usage the capacity has? I've never seen a 429 when copying/creating notebooks before.
- svenchio
HI PyyneCST I think tayloramy summarizes perfectly "Capacities are attached to workspaces, not to accounts", for instance, in the image below is two examples, in red shows my license to be premium per user (formely power bi pro) and in gray Microsoft Fabric (Free) ... this has nothing to do with the capacity assigned to the workspace
What you need to check is the capacity of the workspace, you can check this by click on the workspace settings > workspace type and check on the details sectinos as shown below.
With regards to the error, I'm guessing the pipeline runs some task related to Power BI, most likely I would assume you are orchestrating the refresh of the semantic model? If so, this error is basically the capacity on the workspace you'ære using it's hitting its limit and throttling in response sending you the 429 error.
There's no solution other than wait for the throttling to subside and/or increse your workspace capacity.
Hope this helps, if so, a thumbs up will be nice and mark this as a solution if appropiate. All the best.
- deborshi_nag
Hi PyyneCST very appropriate comments from tayloramy and svenchio. HTTP return code indicates throttling - more about this on this Microsoft page.
Throttling - Microsoft Fabric REST APIs | Microsoft Learn
v-echaithraCommunity Support
HI PyyneCST ,
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Best Regards,
Chaithra E.The throttling issue was resolved – but this was expected because throttling is time bound. I still have not understood why it happened though. The documentation is not clear on the request limits, and the operation that caused the issue for me was duplicating a Notebook.
- v-echaithra
Hi PyyneCST ,
Thank you for the update.
The HTTP 429 error indicates request throttling on the Fabric/Power BI service side. Even though the operation was simply duplicating a Notebook, this action can internally trigger multiple Power BI REST API calls (for example, retrieving metadata, copying artifacts, permissions, and workspace item registration). If several operations occur within a short time window, the service may temporarily enforce throttling.
Currently, the exact request limits for many Fabric operations are not publicly documented, as they can vary depending on factors such as capacity load, concurrent requests, and backend service protection policies. This is why the documentation does not list a fixed limit.
Since the issue resolved automatically, it confirms the throttling was temporary service-side protection rather than a configuration problem with your account or workspace capacity.
If the issue starts occurring frequently, we recommend:
Monitoring capacity metrics for spikes in activity
Avoiding rapid repeated artifact operations (copy/create/update)
Implementing retry logic with backoff when automating Fabric API operationsPlease let us know if the issue reoccurs or if additional details are needed.
Best Regards,
Chaithra E.
- v-echaithra
Hi PyyneCST ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
