Implementation Notes for Version-Aware Retries

Retries should be version-aware so the system does not repeat work against state that has already been superseded by another actor.

If a retry does not know which version of state it is acting against, it is not controlled enough for a contested workflow.

Before retrying, check

• The last known state version.
• Whether another actor already completed the work.
• Whether the workflow phase still permits the action.

Use the quickstart, architecture guide, and examples to make retries version-aware.