Request runbookPreserve the first failure before you retry.
Keep the model ID, timestamp, request ID when available, response status, and error body. Change the condition that failed before sending another billable request.
401The request could not authenticate.
- First check
- Confirm the Authorization header, key value, environment, and whether the key was revoked.
- Recovery
- Load the intended key from the environment and send one small request. Do not paste the key into a ticket or client-side code.
402The account cannot fund this request.
- First check
- Check the available balance and effective request group in Console. Estimate the same payload against the dated rate.
- Recovery
- Open the wallet, confirm the checkout amount and method, then verify the balance before retrying.
429The route is asking the client to slow down.
- First check
- Keep the first response and identify whether the limit is request pacing, concurrency, or account policy.
- Recovery
- Use bounded exponential backoff with jitter. Stop after the application limit instead of creating an unbounded retry loop.
Specific next stepFix the failed boundary, then send one controlled request.
A different status needs a different remedy. If the same boundary repeats without new evidence, stop and inspect the preserved record.