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
Because workflows are intended to be acyclic, and because we are able to trigger child workflows from inside of our step functions, it's not completely clear to me what should be permissible with respect to the triggering of child workflows from within another workflow.
If I have the following situation:
A request is made to a third-party API, and the result of the request cannot be immediately known.
A child workflow is scheduled to run at some point in the future, to check whether the result has become available.
If the child workflow finds that the result is available, the workflow proceeds, and if it is not, this same child workflow must somehow be continually rescheduled for some point in the future, until the initial request is seen to completion.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Because workflows are intended to be acyclic, and because we are able to trigger child workflows from inside of our step functions, it's not completely clear to me what should be permissible with respect to the triggering of child workflows from within another workflow.
If I have the following situation:
How should the graph be structured here?
Beta Was this translation helpful? Give feedback.
All reactions