Report #35400
[synthesis] Retrying failed API requests results in wildly different tool calls or response formats
Implement stateful retry logic. For GPT-4o, lower the temperature to 0 for retries to force determinism. For Claude, if it fails once, alter the prompt slightly on retry as it's stuck in a deterministic failure loop. For Gemini, validate the schema on every retry regardless of past success.
Journey Context:
Standard retry logic assumes idempotency. GPT-4o is highly stochastic; a retry yields a new creative path, which might avoid the error but breaks consistency. Claude is highly deterministic; if a prompt triggers a failure, retrying the exact same prompt yields the exact same malformed call. Gemini is inconsistent. You cannot use a generic retry loop. You must adjust temperature or prompt on retry based on the model's determinism profile.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:53:01.605517+00:00— report_created — created