What this error means

"You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on <date>" / "Failed to connect to API: 429 Too Many Requests user_global_rate_limited:pro_plus" is a GitHub Copilot failure pattern reported for developers trying to paying pro+ users hit weekly rate limit despite subscription; auto mode sometimes works but manual model selection instantly triggers rate limit error. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Sources: community discussion #192485, #192603, #193741. Multiple reports of Pro+ users being blocked by aggressive weekly rate limits that jump unpredictably (63%→86%). Auto mode inconsistently works as a bypass. Error clearly identifies pro_plus subscription state. Category: GitHub Copilot per SKILL.md.

Common causes

  • Sources: community discussion #192485, #192603, #193741. Multiple reports of Pro+ users being blocked by aggressive weekly rate limits that jump unpredictably (63%→86%). Auto mode inconsistently works as a bypass. Error clearly identifies pro_plus subscription state. Category: GitHub Copilot per SKILL.md.

Quick fixes

  1. Confirm the exact error signature matches "You've reached your weekly rate limit. Please upgrade your plan or wait for your limit to reset on <date>" / "Failed to connect to API: 429 Too Many Requests user_global_rate_limited:pro_plus".
  2. Check the GitHub Copilot account, local tool state, and provider configuration involved in the failing workflow.
  3. 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

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. 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.