docs: document missing version parameter in Durable Functions HTTP API - #128741
docs: document missing version parameter in Durable Functions HTTP API#128741Teos (teofanis) wants to merge 2 commits into
version parameter in Durable Functions HTTP API#128741Conversation
The official Microsoft docs for the Durable Functions management HTTP API don't document the `version` query parameter on the Start Orchestration endpoint. This parameter controls which version is assigned to the new instance (available as `context.df.version` in the orchestration body).
|
Teos (@teofanis) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Teos (@teofanis) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 4603883: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 3871df3: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
Bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Documents the previously undocumented version query parameter on the Durable Functions “Start Orchestration” management HTTP API so users can explicitly set the instance version (surfaced as context.df.version).
Changes:
- Adds
&version={version}to the Start Orchestration request URL examples for both runtime endpoints. - Adds a request-parameter table entry documenting purpose, default behavior, and constraints of
version.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The official Microsoft docs for the Durable Functions management HTTP API don't document the
versionquery parameter on the Start Orchestration endpoint. This parameter controls which version is assigned to the new instance (available ascontext.df.versionin the orchestration body).