-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix(workflows-sdk): name for when/then step #10459
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
🦋 Changeset detectedLatest commit: a34735b The changes in this PR will be included in the next version bump. This PR includes changesets to release 65 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, were these the only steps we needed to change to not have the warning for our core workflows?
Yes, only these 2. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
What:
when/then
composition creates a step with a random name (ulid) under the hood when thethen
function is not returning a step. This is causing multiple Medusa instances fail to continue the execution ofasync
flows because the step name will differ on each instance.This PR removes the creation of a step if the
when/then
doesn't return anything, and it introduces thename
parameter when creating awhen/then
that will return a value different than a step.Some other fixes were applied to execute the same workflow in parallel.
FIXES: FRMW-2824