output-error-nondeterminism

Temporal workflow replay fails due to non-determinism when code uses dynamic values like Math.random or Date.now. Fixing non-determinism ensures replays match the original history exactly during recovery and retries.

Fix non-deterministic Output SDK workflows by moving dynamic values to steps or passing them as explicit inputs. Replace Math.random, Date.now, and crypto.randomUUID with deterministic step-generated values to guarantee reproducible history.

Non-deterministic replays are caused by dynamic imports, environment-dependent values, and random number generation inside workflows. Using static imports and explicit configuration inputs ensures deterministic history during workflow recovery.

Using Date.now or crypto.randomUUID inside a Temporal workflow breaks determinism and causes replay failures. Generate these values in workflow steps or pass them as inputs to ensure consistent results across all runs.

Ensure deterministic history by applying static imports, explicit environment inputs, and step-generated values. Avoiding dynamic imports and random functions guarantees identical workflow replays across recovery and retry attempts.