When a wait for event executes, activity within the current workflow branch ceases until the wait for event’s associated manual or scheduled trigger fires. During this time, the wait for event’s status is Waiting for Trigger.
Note that a wait for event can be associated with one or more database count constraints.
Upon the wait for event’s activation, the system commences checking database count constraints at a frequency accordant with a system configuration setting (TriggerCheckCriteriaInterval). The wait for event’s associated trigger may only fire when all database count constraints are met. If a manual wait for event, when all attached database count constraints are satisfied, the wait for event will fire immediately. If any outstanding database count constraints remain unsatisfied when the Stop checking at date and time have already passed, the associated trigger does not fire.
Constraints are ignored when firing a manual wait for event.
Following the firing of a wait for event’s manual or scheduled trigger, downstream activities within the workflow commence once again.
If an interaction workflow contains a scheduled wait for event that is configured with a date/time in the past, a runtime validation warning is shown at the workflow’s activation. If the warning is ignored, the wait for event will fire immediately at its activation.