Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
carolina_k
New Member

Error Code 430: Too Many Requests For Capacity

Hi,

 

I'm trying to run a notebook in Fabric but keep getting the below error:

 

carolina_k_0-1699523759124.png

 

I have tried to go the notebook in the stacktrace but it doesn't look like it's running.  I can't seem to find where the actively running jobs are listed in Fabric so I can cancel them.  The only solution I've found is to wait for the spark pool to stop completely and start it up again from scratch.  I've tried to add a delay to a new cell at the end of the notebook but this doesn't seem to work.  There must be a faster/more efficient way of solving this issue though...

 

Any help or advice that anyone can provide would be very much appreciated!  I am very very new to Fabric...

 

Many thanks!

1 ACCEPTED SOLUTION
Anonymous
Not applicable

HI @carolina_k,

I'd like to suggest you take a look at the official document about fabric notebook usage and limitations part if these help for your scenario:

Concurrency limits and queueing for Fabric Spark - Microsoft Fabric | Microsoft Learn

Regards,

Xiaoxin Sheng

View solution in original post

4 REPLIES 4
MartinFM
Helper I
Helper I

Hello,

 

I do not understand how this is the solution. I have a F2 capacity. I am the only person on the platform. I have nothing running according to Monitor. But it still gives me a HTTP 430 message. So something must be running but I cannot see what it is. Where can I see evertyhing that is using my capacity so that I can make an informed decision on how to run my notebooks?

 

Br. Martin

Agree. I'm at F8 right now - one user, one notebook, one lakehouse - and I can't both have a notebook processing a simple ELT job in one tab, and then explore a table in the onelake hub on another tab. Get: TooManyRequestsForCapacity.

This can't be right. 

I figured out somewhere that the problem is related to the Spark pools. I do not fully understand the Spark pools yet but it worked significantly better when I created a new Spark pool and used that instead of using the Starter Park pool.

 

Hope this can work for you too.

 

Br. Martin

Anonymous
Not applicable

HI @carolina_k,

I'd like to suggest you take a look at the official document about fabric notebook usage and limitations part if these help for your scenario:

Concurrency limits and queueing for Fabric Spark - Microsoft Fabric | Microsoft Learn

Regards,

Xiaoxin Sheng

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.