GitHub Actions / GitHub Actions

GitHub Actions GITHUB_TOKEN Secondary Rate Limit — Concurrent Requests Exceeded

Resolve secondary rate limit error in GitHub Actions workflow caused by excessive concurrent API calls; understand point calculation for secondary limits Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated May 23, 2026 1 source Needs local verification

Category: GitHub Actions
Error signature: Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: May 23, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold is a GitHub Actions failure pattern reported for developers trying to resolve secondary rate limit error in github actions workflow caused by excessive concurrent api calls; understand point calculation for secondary limits. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GITHUB_TOKEN primary rate limit is only 1,000 requests/hour (vs 5,000 for PAT). Secondary rate limits include 100 concurrent request cap, 900 points/minute for REST, and 60s CPU/60s wall time per minute. Fetched from official GitHub docs. High commercial value because CI/CD pipeline failures affect paid GitHub teams and enterprise orgs.

Common causes

GITHUB_TOKEN primary rate limit is only 1,000 requests/hour (vs 5,000 for PAT). Secondary rate limits include 100 concurrent request cap, 900 points/minute for REST, and 60s CPU/60s wall time per minute. Fetched from official GitHub docs. High commercial value because CI/CD pipeline failures affect paid GitHub teams and enterprise orgs.

Quick fixes

Confirm the exact error signature matches Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold mean in GitHub Actions?

Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold indicates the workflow described by "GitHub Actions GITHUB_TOKEN Secondary Rate Limit — Concurrent Requests Exceeded" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold?

Check whether this cause matches your environment: GITHUB_TOKEN primary rate limit is only 1,000 requests/hour (vs 5,000 for PAT). Secondary rate limits include 100 concurrent request cap, 900 points/minute for REST, and 60s CPU/60s wall time per minute. Fetched from official GitHub docs. High commercial value because CI/CD pipeline failures affect paid GitHub teams and enterprise orgs.

Is the Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold guidance source-backed?

The "GitHub Actions GITHUB_TOKEN Secondary Rate Limit — Concurrent Requests Exceeded" page is labeled source-backed. It has 1 public source URL from docs.github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold?

For "GitHub Actions GITHUB_TOKEN Secondary Rate Limit — Concurrent Requests Exceeded", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Secondary rate limit triggered: too many concurrent requests (exceeds 100 concurrent limit) or 900 points/minute REST endpoint threshold?

For "GitHub Actions GITHUB_TOKEN Secondary Rate Limit — Concurrent Requests Exceeded", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.