Initiates workflows automatically based on events, schedules, or external signals.
Starts work in response to an event, schedule or condition rather than a person. The entry point that makes automation continuous rather than invoked.
Event-driven processing and scheduled operations where prompt response matters.
Where the trigger condition is ambiguous. A workflow that starts spuriously is worse than one started late.
Triggered runs must be as auditable as invoked ones, including what fired them. An action nobody initiated still needs an accountable owner.
Trigger storms — one upstream event firing many workflows, or a retry loop repeatedly triggering the same one.
A settlement file arriving out of sequence triggering reprocessing for that date, with idempotency preventing the reprocessing from duplicating what already matched.