Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Added support for executing a sub-workflow #1363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kfrajtak wants to merge 4 commits into danielgerlag:master
base: master
Choose a base branch
Loading
from kfrajtak:subworkflow

Conversation

Copy link

@kfrajtak kfrajtak commented Jun 16, 2025
edited
Loading

Describe the change
This PR adds a support to run a sub-workflow from the main workflow.

Describe your implementation or design
New step builder was added to support sub-workflow. The step starts a new workflow when executed with given workflow id (name). The workflow gets an reference to main workflow, the main workflow then waits for a workflow completed event triggered from the sub-workflow and continues.

If sub-event expects an event then the event should be published with parent workflow id since the sub-workflow id is not known.

An error in the sub-workflow terminates it and consequently terminates the parent workflow as well.

Tests
Yes

Breaking change

Copy link
Owner

@danielgerlag danielgerlag left a comment

Choose a reason for hiding this comment

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

Happy to merge this if we can revert the WaitFor primitive changes.

}

return ExecutionResult.WaitForEvent(EventName, EventKey, effectiveDate);
var eventKey = context.Workflow.Reference ?? EventKey;
Copy link
Owner

@danielgerlag danielgerlag Sep 20, 2025

Choose a reason for hiding this comment

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

This does not make sense, why would we default to the reference field as the wait key? This could be a major breaking change.

Copy link
Owner

@danielgerlag danielgerlag Sep 20, 2025

Choose a reason for hiding this comment

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

I don't think we should be changing the behaviour of the WaitFor primitive to support this feature

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@danielgerlag danielgerlag danielgerlag requested changes

@glucaci glucaci Awaiting requested review from glucaci glucaci is a code owner

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /