Skip to content

Commit affd112

Browse files
committed
Clarify description of the Reject strategy in orchestration versioning
1 parent c651755 commit affd112

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -274,7 +274,7 @@ The `versionFailureStrategy` setting determines what happens when an orchestrati
274274

275275
**Available strategies:**
276276

277-
- **`Reject`** (default): Don't change the orchestration state. The orchestration instance remains in its current state and can be retried later when a compatible worker becomes available. This strategy is the safest option as it preserves orchestration state.
277+
- **`Reject`** (default): Don't process the orchestration. The orchestration instance remains in its current state and can be retried later when a compatible worker becomes available. This strategy is the safest option as it preserves orchestration state.
278278

279279
- **`Fail`**: Fail the orchestration. This strategy immediately terminates the orchestration instance with a failure state, which may be appropriate in scenarios where version mismatches indicate serious deployment issues.
280280

0 commit comments

Comments
 (0)