Hey guys!
I need help clarifying some things about the “wait” step for workflows.
For example, if a workflow is triggered by an “identity attribute changed” trigger, and there is a wait step in it, when another event that would trigger this workflow happens, will it create another instance for this workflow?
If so, how many “waiting” instances can exist at the same time?
Hi @Caio_Nakayama ,
The wait step in ISC workflows doesn’t block new triggers. Each time the workflow trigger condition is met (e.g. an identity attribute changed event), ISC will spin up a new workflow instance, regardless of whether a previous one is still sitting at a wait step.
So in your example:
Event 1 → workflow starts, hits the wait step, and pauses.
Event 2 (same identity or another) → a separate instance of the workflow is created and starts its own execution path.
This means you can definitely have multiple “waiting” instances of the same workflow running in parallel. There isn’t a strict limit on how many can exist at once. but keep in mind that if you expect a large number of triggers, this can lead to many paused instances in your tenant, so it’s good practice to design carefully (e.g., avoid long waits if not needed, or add conditions to reduce unnecessary runs).
thanks
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.