I am wondering if there isn’t a planned action that will wait for workflow to move from one workflow state to another before processing the rest of the logic. I believe this could be quite handy in many instances.
Hi Stefanus!
No, there is not and will not be. Any process that waits for another to finish ties up server resources. In a logic block with an open query, it can also tie up database resources. This can have negative performance impacts for the whole system, which is not something we would want to expose.
The recommended pattern for this is to queue something up at the end of your workflow transition via a Post-transition Logic Block.
If you need something that requires two processes to finish before it can begin running, we can discuss some other options. But there are ways to accomplish that, too, without tying up resources for a long time.
That makes sense. I wondered about it and therefore the question.
I’m definitely interested in knowing about situations where it seems like using waits is the only way to get something to work. Please reach out to me in those situations so I can be aware of any gaps that are preventing the developer from using a more ‘loosely coupled’ strategy (orchestration, eventing) to solve the requirement.