Start with the final outbound request. Use the instruction field and message positions supported by that exact endpoint, preserve tool-call pairs, and verify the full task after the role error clears.
A Nano Banana Pro 503 can include Deadline expired wording. Check the responding service and error code first, retry with a clear limit, and count recovery only when the same image request produces a usable result.
If Pro returns a restriction message or no image, first recover the correct Pro route: More → Redo with Pro in Gemini, the Pro menu in eligible AI Mode accounts, or gemini-3-pro-image in the API. Then check the actual response before calling the failure a policy block.
For "Unsupported file URI type," check the exact image value your app sent and the endpoint that rejected it. Native Gemini can accept supported HTTPS URLs; local paths, unresolved templates and base64 data URLs need a different payload. Verify the repair by getting an edited image from the same Pro request.
Gemini app image failures are usually sign-in, age, quota or a policy refusal. In the API, retry 429 and 5xx with backoff, and never retry 400, 402 or 403.
Google defines blockReason OTHER as a prompt blocked for unknown reasons. Save the response, test one change at a time, and don't retry it in a loop.
Nano Banana 2 returns 400 when a follow-up edit resends its earlier image without the thought signature. Use previous_interaction_id or SDK chat history.
For an OpenClaw 401, first identify who rejected the request. An invalid provider token, a missing outgoing auth header, and a Gateway or device-token mismatch require different fixes. Check the failing agent and session before replacing credentials.
For a large OpenClaw session, save the task state and try supported manual compaction. If the summary request also exceeds its limit, resume in a fresh session from a short record of completed work. Fresh-session failures require checking fixed overhead and the local model's loaded context.
Repair an OpenClaw invalid beta flag error by identifying which feature header the selected provider rejected and where it was added. Remove an unsupported optional flag, or repair the required feature's route, then confirm both configuration loading and a completed request.
When OpenClaw reports a 429, pause extra requests and identify whether the rejection came from the model provider or ClawHub. Wait for a temporary limit, repair exhausted quota or access, and check whether the current selection permits fallback. Preserve completed work before continuing.
A paid Gemini project can still return free_tier_requests limit 0 if the running app uses another project's key, billing setup is incomplete, or the requested model has no usable allowance. Match the request to AI Studio's project, billing status, and active model limits before retrying or replacing keys.
For Nano Banana Pro RESOURCE_EXHAUSTED errors, check the actual project, model, and exhausted limit before retrying. Pause zero allowances, daily limits, and billing blocks; retry transient pressure within a time budget and save confirmed images so a restart does not generate them again.
Signed in with ChatGPT and never set a key? That 401 came from OpenAI's September 25, 2026 outage. The URL and key text in the error tell you if yours differs.
"Authentication failure: user is blocked" most likely means an account block only xAI can lift. Most other Grok sign-in errors you can fix yourself.
A Claude 400 on Amazon Bedrock can be a stripped beta header, old Claude Code, full context, a bad model ID or an account setting. Fix it by the exact message.
No image from the Nano Banana API usually means a text-only reply, a policy block or cut-off output. The raw response shows which, and whether a retry helps.
If Gemini 3.8 Flash feels slow in Antigravity, first identify what is waiting: the first answer, an active tool, server capacity, a repeated command, or the app itself. Each calls for a different response.
Fix ChatGPT’s “Unknown Error Occurred” when uploading a PDF. Two file-and-browser checks help you choose a document, upload-limit, or connection fix.
A static page cannot prove that every Nano Banana 2 surface is up or down. Use the failing surface, its first-party status owner, and the exact error signal to classify the incident before retrying.
Keep the old thread, run one small prompt in a fresh chat, and let that control decide whether to hand off the work or troubleshoot the broader path.
OpenClaw Anthropic API key errors need an owner-first read: prove whether Anthropic auth is missing, the key is rejected, OAuth cannot refresh, an env var overrides config, the selected model is unavailable, or OpenClaw is only showing a provider cooldown after an earlier failure.
A fast route board for the Grok heavy-usage message: status first, one surface switch, paid-plan recognition, bounded retry, and support evidence.
If OpenAI says your file type is not supported and tells you to try again with a PDF, the useful first move is to identify the rejecting surface. Current official OpenAI docs are not blanket PDF-only, but some lagging Azure or connector paths still behave that way.