Skip to content

Adds multi app workflow operations example - #859

Open
JoshVanL wants to merge 3 commits into
dapr:mainfrom
JoshVanL:example-cross-app-workflow-operations
Open

JoshVanL wants to merge 3 commits into
dapr:mainfrom
JoshVanL:example-cross-app-workflow-operations

Conversation

@JoshVanL

@JoshVanL JoshVanL commented Nov 3, 2026

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: joshvanl <me@joshvanl.dev>
@JoshVanL
JoshVanL requested a balanced review from Copilot November 3, 2026 13:03
@JoshVanL
JoshVanL requested review from a team as code owners November 3, 2026 13:03
@codecov

codecov Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.38%. Comparing base (e28f61c) to head (9ff7aa2).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #859   +/-   ##
=======================================
  Coverage   57.38%   57.38%           
=======================================
  Files          53       53           
  Lines        3888     3888           
=======================================
  Hits         2231     2231           
  Misses       1503     1503           
  Partials      154      154           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Purge verification treats any fetch error with nil metadata as success, so timeouts or an unavailable sidecar can falsely confirm deletion instead of requiring an instance-not-found error.

1 open issue
What changed in this PR

Adds a two-app example demonstrating how a client manages workflows owned by a separate Dapr host using explicit target app IDs.

Changes:

  • Adds a workflow host and client covering scheduling, status checks, suspension, resumption, events, completion, termination, and purging.
  • Documents execution and expected output, with shared Redis state-store configuration.
  • Includes the example in automated example validation.
File Description
examples/​workflow-cross-app/​README.md Documents cross-app options, run commands, cleanup, and expected output.
examples/​workflow-cross-app/​host/​host.go Registers and runs the workflow and its activities.
examples/​workflow-cross-app/​config/​redis.yaml Configures Redis as the actor state store.
examples/​workflow-cross-app/​client/​client.go Drives workflow lifecycle operations on the host app.
.github/​workflows/​validate_examples.yaml Adds the example to the validation matrix.

Review effort: Balanced

@cicoyle cicoyle left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we name it multi app instead of cross app? That was something I got feedback on when this feature was introduced and all our existing examples/docs use the phrasing multi app

ex: https://docs.dapr.io/developing-applications/building-blocks/workflow/workflow-multi-app/ && https://github.com/dapr/samples/tree/master/multi-app-workflows

@JoshVanL JoshVanL changed the title Adds cross app workflow operations example Adds multi app workflow operations example Nov 16, 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.

4 participants