Workflow Evolution: Versioning + Continue-As-New
When to use
Use when the user wants to:
- •change workflow logic in production
- •reorder steps / change branching
- •add/remove activities or timers
- •manage history size for long-running workflows
Required output
- •A safe change plan using
Workflow.GetVersion(show old + new branches) - •A removal policy for old branches (only after all executions that might replay old history are complete)
- •If relevant: continue-as-new trigger strategy (history thresholds, state carryover)
Guardrails
- •Workflow history is immutable.
- •Never delete old branches prematurely.