Fabric Notebook - HTTP 430 TooManyRequestsForCapacity when running simple Spark SQL query

[Shahid12523]

Hi everyone,

I'm getting an HTTP 430 - TooManyRequestsForCapacity error when trying to run a very simple Spark SQL query in a Microsoft Fabric notebook.

Has anyone experienced this issue?

Is this caused by capacity overload or queued Spark jobs?
How can I check which Spark jobs are consuming the capacity?
Is there any workaround besides waiting or upgrading the capacity?
I've attached the error screenshot for reference.

Thanks in advance for any suggestions!

[v-anbandari]

Hi @Shahid12523 ,

Just checking in to see if your issue has been resolved. If you’re still facing any problems, please feel free to reach out and we’ll be happy to assist further.

Thank you.

[Shahid12523]

Not yet

[v-aatheeque · Accepted solution]

Hi @Shahid12523 

Thank you for sharing the screenshot.

Based on the error message, [TooManyRequestsForCapacity] typically indicates that the Fabric Spark request is being throttled because there aren't enough compute resources available on the assigned Fabric capacity at the time the notebook is executed.

To help isolate the issue, could you please check the following?

• Are there any other Spark notebooks or jobs running concurrently in the same workspace or on the same Fabric capacity?
• Are there any long-running or stalled Spark sessions that may still be consuming capacity? If so, please terminate them and retry the notebook.
• If you have access to the Fabric Capacity Metrics app, could you verify whether the capacity is under heavy Spark utilization when the issue occurs?
• If possible, try restarting the Fabric capacity to clear any orphaned Spark sessions, wait a few minutes, and then run the notebook again.
• If your organization has Autoscale Billing for Fabric Spark enabled, please verify that it is configured correctly, as this allows Spark workloads to use dedicated serverless compute instead of consuming Fabric capacity compute units.
• If the issue occurs frequently, you may also want to consider using a higher Fabric capacity SKU or, if applicable, a custom Spark pool instead of the shared Starter pool.

Additional reference : Troubleshoot Permission and Capacity Errors in Data Engineering - Microsoft Fabric | Microsoft Learn
Fabric Notebooks troubleshooting guide - Microsoft Fabric | Microsoft Learn

Hope this helps !!

Thank You.

[v-aatheeque]

Hi @Shahid12523 

Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.

[v-anbandari]

Hi @Shahid12523 ,
 

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to the @TomMartens  for sharing valuable insights.
 

Could you please confirm if your issue has been resolved using the suggested approach? This will help other community members facing similar scenarios.
 

Thank you for being part of the Microsoft Fabric Community.
 

[TomMartens]

Hey @Shahid12523 ,

all things regarding monitoring is mentioned in error message. You can watch everything in the Monitoring Hub (https://learn.microsoft.com/en-us/fabric/admin/monitoring-hub that consumes from your capacity). Next to that it also job management is mentioned.

It's not related to the task that the notebook is gooing to perform, no matter if it is a complex data engineering task or a simple Spark SQL query.

It's solely limited by the "capacity" of your capacity.

However, most likely this is not the answer you were hoping for, but besides adding more money to the capacity you only can wait, or stop currently running jobs. Stopping a currently running activity might not be a good idea, if it's a "production" activity though.

Regards,
Tom