You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand correctly the "wait" step is waiting on the Activity and not the ActivityTask. The inner state machine and lambda respond with send-success with the taskToken as a parameter. But that information seems to be lost in the wait step of the outer state machine.
A consequence would be that if I want to invoke the outer state machine multiple times in parallel, then a send-success for any taskToken would make all the outer state machines exit (or a random choice.) Either of those behaviors would cause havoc.
The text was updated successfully, but these errors were encountered:
It is important to use the input from the GetActivityTask response and not the one passed to Lambda due to the fact that in the result of the GetActivityTask call we may get the Task Token for the Activity in any execution of any State Machine that uses this Activity.
In essence, the "Start asynchronous action" Task in outer State Machine is only for technical purposes and when interpreting execution flow you should look only into "Wait for asynchronous action" input and output.
Anyway, IIUC, in the meantime AWS implemented something similar as part of AWS Step Functions (Callback with Task Token and Nested Workflows) so it is preferred way to implement nested State Machines now.
blog-step-functions-async-actions/state_machines/outer_state_machine.json
Line 35 in d086470
If I understand correctly the "wait" step is waiting on the Activity and not the ActivityTask. The inner state machine and lambda respond with send-success with the taskToken as a parameter. But that information seems to be lost in the wait step of the outer state machine.
A consequence would be that if I want to invoke the outer state machine multiple times in parallel, then a send-success for any taskToken would make all the outer state machines exit (or a random choice.) Either of those behaviors would cause havoc.
The text was updated successfully, but these errors were encountered: