A workflow-event trigger never fires on a run that it started itself, or on that run’s descendants, so two workflows cannot trigger each other forever, and a chain of event-launched runs stops at five hops. If a name in
workflows does not resolve yet, validation warns that the trigger matches nothing until the workflow exists.
What the run sees
trigger.payload describes the run that reached the outcome. Every key is always present, empty when it does not apply:
Use
filter to narrow further, in the same way as for any other kind (filter: "trigger.payload.error.contains('timeout')"), and see Automations for the shared fields.