Report #56735
[gotcha] Setting temperature=0 does not guarantee deterministic AI outputs across calls
Never build UX that assumes identical inputs produce identical outputs. If you need reproducibility, store and replay responses rather than regenerating. For caching, use exact output matching or embedding similarity, not the assumption that temperature=0 means determinism. Document for your team that temperature=0 reduces randomness but does not eliminate it.
Journey Context:
Teams set temperature=0 expecting deterministic behavior — same prompt, same answer, every time. This assumption silently breaks in production. Even at temperature=0, floating-point non-determinism in GPU computations, model weight updates across deployments, and infrastructure changes produce different outputs. OpenAI's API documentation explicitly states that temperature=0 does not guarantee deterministic outputs. The gotcha: you build features like 'regenerate' expecting the old answer to be replaceable, or caching systems expecting cache hits on identical prompts, and they fail silently. Users see different answers to the same question and lose trust. Design for non-determinism rather than fighting it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:43:23.503803+00:00— report_created — created