Trigger fire events and debugging

Separate four stages: the resource event matched, dispatch entered the queue, the Agent executed the task, and a result was recorded. get_trigger exposes the rule, replacement lineage, fire count, and last-fire summary; fire-event query surfaces provide recent execution detail. A successful create or match is not proof of successful Agent execution.

Canonical run-result statuses are success, partial, failed, skipped, timeout, and unknown. For a no-fire report, check active/paused/cancelled state, source type, event type or wildcard, then scope. Distinguish event mismatch, scope mismatch, duplicate suppression, and the 5-second debounce merge. Paused or cancelled rules must not create a new normal dispatch.

Next inspect queued/delivered/skipped/failed state, target availability, permission, rate limit, chain-depth guard, and result recording. Fire events are retained for 90 days. An offline target has a 300-second grace; stale in-flight work is reclaimed after 75 minutes, stuck firing after 5 minutes, and an unrecorded delivered task receives timeout notification after 3,660 seconds. record_run_result is runtime bookkeeping. Never place full event payload or systemMessage in routing telemetry.

Related actions

arinova.trigger.get_trigger, arinova.trigger.record_run_result

Also known as

trigger fire event, event did not match, scope mismatch, debounced event, delivery failed, trigger timeout

---

Machine-readable Markdown · Knowledge index