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
In above case workflow will resume by scheduling the ActivateAccount lambda function on receiving the RegistrationVerified signal.
Currently by default signals are ignored. After the implementation of this idea the default behaviour of signal would be to resume any waiting execution
WaitForSignal can only be called in response to event of a workflow item- lambda function, activity....
Expose another workflow action - ResumeOnSignal("signalName"), This workflow action will be called on receiving the signal.
User can override signal handling and provide her own logic.
Workflow can wait multiple times for same signal
Multiple workflow items, in parallel branches, can wait for same signal.
In the absence of this feature you can still pause and wait for signals. Please browse through examples to get the idea about signal handling.
The text was updated successfully, but these errors were encountered:
It will be quite useful for some workflows to pause the execution of workflow until some signal arrives. Possibly something like below:
In above case workflow will resume by scheduling the ActivateAccount lambda function on receiving the RegistrationVerified signal.
In the absence of this feature you can still pause and wait for signals. Please browse through examples to get the idea about signal handling.
The text was updated successfully, but these errors were encountered: