Currently, we pass the workflow-is which is absolutely useless because the user doesn't have a way to retrieve our state.
To better understand what is the best solution for this problem, first, if there is anything that the user can't do unless we provide him with some extra functionality.
What I thought so far:
the user may want to restrict the number of times a workflow is running in parallel: x times in parallel at most in y seconds with a t timeout.
if a flow function is async, he may want to restrict the number of times that flow function is running in parallel: x times in parallel at most in y seconds with a t timeout.
solutions:
pass the hole state and let the user use custom helper functions for extracting useful information from that. for example we can build a custom function that calculated how many times in parallel a specific function was called between 2 dates or even now. with this information, the user can restrict the number of times a flow or workflow is running in parallel.
Currently, we pass the workflow-is which is absolutely useless because the user doesn't have a way to retrieve our state.
To better understand what is the best solution for this problem, first, if there is anything that the user can't do unless we provide him with some extra functionality.
What I thought so far:
x
times in parallel at most iny
seconds with at
timeout.x
times in parallel at most iny
seconds with at
timeout.solutions: