Skip to content

Commit 147a61d

Browse files
Merge pull request #127439 from lilyjma/patch-2
Update durable-functions-orchestration-versioning.md
2 parents 3eb7ef7 + 56f49b2 commit 147a61d

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
@@ -9,7 +9,7 @@ ms.custom: fasttrack-edit
99
#Customer intent: As a Durable Functions developer, I want to deploy breaking changes to my orchestrations without interrupting in-flight instances, so that I can maintain zero-downtime deployments.
1010
---
1111

12-
# Orchestration versioning in Durable Functions (Azure Functions)
12+
# Orchestration versioning in Durable Functions (Azure Functions) - public preview
1313

1414
Orchestration versioning addresses [the core challenge](durable-functions-versioning.md) of deploying changes to orchestrator functions while maintaining the deterministic execution model that Durable Functions requires. Without this feature, breaking changes to orchestrator logic or activity function signatures would cause in-flight orchestration instances to fail during replay because they would break the [determinism requirement](durable-functions-code-constraints.md) that ensures reliable orchestration execution. This built-in feature provides automatic version isolation with minimal configuration. It's backend agnostic, so it can be used by apps leveraging any of the Durable Function's [storage providers](durable-functions-storage-providers.md), including the [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).
1515

0 commit comments

Comments
 (0)