Skip to content

Workflow: document staged operations (WorkflowsStagedOperations preview) - #5473

Open
famarting wants to merge 1 commit into
dapr:v1.20from
famarting:workflow-staged-operations
Open

famarting wants to merge 1 commit into
dapr:v1.20from
famarting:workflow-staged-operations

Conversation

@famarting

Copy link
Copy Markdown
Contributor

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane (no commands added)
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text (no images added)
  • Places where multiple code/command options are given have tabpane (none added)

In addition, please fill out the following to help reviewers understand this pull request:

Description

Documents the WorkflowsStagedOperations preview feature, which lands in Dapr 1.20. With it, Dapr accepts workflow operations while no workflow worker of the app is connected. Start, raise event, terminate, suspend, resume and rerun are saved and return at once. They run once a worker connects. Status reads and purges complete at once.

Changes:

  • New page workflow-staged-operations.md: what happens while no worker is connected, the staged response field, how fallback hosts work, how to enable the feature (and the mixed-version warning), and the metric.
  • Preview features table: new row for WorkflowsStagedOperations.
  • Workflow overview: short section linking to the new page.
  • How to: Manage workflows: the note that a start fails with no worker connected now says what happens with the feature enabled.
  • Metrics overview: short section on dapr_runtime_workflow_staged_operation_count.
  • Workflow API reference: the staged field in the start, terminate, raise event, pause and resume responses.

Source PRs:

Not merged yet: the staged response field comes with dapr/dapr#11061 (draft), and the Go SDK side with dapr/go-sdk#861 (draft). The parts of this PR about staged (the "The staged response field" section of the new page, the last sentence of the overview section, and the workflow API reference changes) should merge only once dapr/dapr#11061 does. If it doesn't make 1.20, I'll take those parts out.

Checked with a local Hugo build (hugo -e dev): the site builds, every ref resolves, and the new page renders with its alerts and anchors.

Issue reference

None.

🤖 Generated with Claude Code

Add a page on staged operations: what happens while no workflow worker
is connected, the staged response field, how fallback hosts work, how
to enable the feature and its metric. List the feature in the preview
features table, and mention it in the workflow overview, the manage
how-to, the metrics overview and the workflow HTTP API reference.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Fabian Martinez <46371672+famarting@users.noreply.github.com>
@famarting
famarting marked this pull request as ready for review November 10, 2026 07:54
@famarting
famarting requested review from a team as code owners November 10, 2026 07:54
@CasperGN CasperGN self-assigned this Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants