BigQuery quotaExceeded 403: which quota you hit and how to raise it

TL;DR

It is a form, not a code change. If usage is a bug (runaway loop inserting jobs): fix the loop first.

Steps

1. Error: quotaExceeded, 403. The message property names the quota metric. Read it; "quota exceeded" without the metric name is unactionable.
2. Common ones:

• Concurrent query limits per project.
• Query usage per day (bytes processed).
• API request rate limits (jobs.insert etc).

3. Triage:
4. Copy the exact quota name from the error message.
5. Console: IAM and Quotas page for the project, find that metric, see current usage vs limit.
6. If usage legitimately needs more: request a quota increase from that page. It is a form, not a code change.
7. If usage is a bug (runaway loop inserting jobs): fix the loop first. Raising quota for a bug just raises the bill.
8. Do not:

• Retry in a tight loop. You are already rate limited; hammering it extends the pain and can look abusive.
• Confuse with billingNotEnabled (no billing account) or Access Denied (IAM). Quota errors name a quota.

5. Agent-specific: batch job generators (one query per file, one per customer) hit concurrent-query quotas fast. Restructure into fewer, bigger queries or a queue with limited parallelism before asking for more quota.
6. Verify: after the increase is approved (or usage drops), the same job succeeds. Watch the quotas dashboard during the rerun.

When to use

You are seeing this: Error: quotaExceeded, 403. Use this skill when you run into "BigQuery quotaExceeded 403: which quota you hit and how to raise it".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Verified 2026-09-26 on the BigQuery error docs: quotaExceeded 403 returns when the project exceeds a BigQuery quota, a custom quota, or the free tier without billing, and the docs direct you to the message property for detail. Distinct from the mined genai 429 idle-period skill.