Skip to content

Expose a public, typed orchestration ID reuse policy #26

Open

Description

@kaibocai

Current behavior

The synchronous and asynchronous schedule_new_orchestration() APIs already accept reuse_id_policy and forward it to the backend. Callers must construct durabletask.internal.orchestrator_service_pb2.OrchestrationIdReusePolicy, so the capability is exposed through an internal generated type rather than a supported, typed public API.

Proposed scope

Expose a public orchestration ID reuse policy using OrchestrationStatus values. Align its public semantics with the current .NET and Go SDKs: statuses selected for deduplication reject an existing instance; other statuses permit replacement where supported by the backend.

  • Preserve backend defaults when the policy or its status list is omitted.
  • Distinguish an explicit empty deduplication list from omission: an empty list permits replacement in every supported stable status.
  • Preserve compatibility with callers passing the existing protobuf policy.
  • Support synchronous and asynchronous clients, including the inherited Azure Managed and Azure Functions client APIs.
  • Document status polarity, backend-dependent behavior, and the difference between omission and an explicit empty list.

Protocol constraints

The original January 2024 proposal described ERROR, IGNORE, and TERMINATE actions. The shared protocol removed its obsolete action field in March 2025 and now carries only replaceableStatus: microsoft/durabletask-protobuf#35.

This issue does not propose restoring those action enums or promising atomic no-op/IGNORE behavior. Replacement must remain a backend operation rather than a client-side terminate-then-start sequence.

Related APIs

  • .NET: StartOrchestrationOptions.DedupeStatuses
  • Go: OrchestrationIDReusePolicy.DedupeStatuses
  • JavaScript/TypeScript: StartOrchestrationOptions.dedupeStatuses on the current development branch

Activity

  1. added a commit that references this issue on Nov 16, 2025
  2. changed the title [-]Support orchestration ID reuse policy[/-] [+]Expose a public, typed orchestration ID reuse policy[/+] on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions