workflow resume on workflow as step not working
Or I should say, it's not working using the client JS even though it does appear to work in the playground. But we're stuck not understanding what the difference is.
Here is our workflow:
gatherStep
is the suspended step and when using the client :
Even when resumeData is passed in correctly, it always ends up undefined in the step. This is working for steps which are NOT workflows like the above and we are not able to see why.5 Replies
And in the browser console I have a step that DOES include the resumeData:
But somehow that's not making it to the step within the sub-workflow.
GitHub
[BUG] Resuming a suspended step runs the workflow from the first st...
Describe the Bug No matter how I resume a workflow, whether I pass the step name or a step instance in the step property, the workflow always starts from the beginning and provides resumeData to th...
This is a pretty old issue, but I'm not sure -- was this ever resolved?
So just to clarify:
📝 Created GitHub issue: https://github.com/mastra-ai/mastra/issues/8972
GitHub
[DISCORD:1428704762848870462] workflow resume on workflow as step n...
This issue was created from Discord post: https://discord.com/channels/1309558646228779139/1428704762848870462 Or I should say, it's not working using the client JS even though it does appear t...
@flippyhead I believe the issue is that you need to pass the whole resume path:
[stepId, nestedWorkflowStepId]
instead of just the path to the nested workflow that was resumed. Alternatively, if it's the only step that is currently suspended, you can resume without passing the step
property in which case it will figure it out for you.
The whole path to what has been suspended should be recorded on result.suspended
of the workflow execution result.
Let me know if this helps