429 Too Many Requests
HTTP 429 means the API is rejecting requests because you’ve exceeded a limit — usually requests-per-minute or tokens-per-minute, sometimes quota. The fix is to back off, retry, and reduce burst load.
Standard Compute doesn’t throw 429 for load — it degrades gracefully (slows and batches) instead of failing the request, so a bursty client keeps working.
Retry with exponential backoff, not immediately — hammering the endpoint makes it worse. Respect the Retry-After header when the provider sends one.