Cancel a running or pending automation execution.
execution_status to failed. Participants already processed retain their generated events; remaining participants are skipped. The automation stays active and fires again on its next scheduled trigger unless you also pause or archive it.API key passed in the X-API-Key header.
Program ID
Automation ID
Automation cancelled
When this automation was created
Cron expression defining the recurring schedule (cron trigger only)
Optional human-readable description of what this automation does
Error message if the one-time automation failed
The event name generated when this automation fires
When the current fan-out execution completed
Error message if the fan-out execution failed
When the current fan-out execution started
Current fan-out execution state: idle, pending, executing, completed, or failed (participant-scoped only)
Optimization hints for the participant filter (e.g., has_tag, has_attribute)
CEL expression evaluated at trigger time; skips the participant if false
Unique identifier for this automation
Error message from the most recent cron execution, if any (cron trigger only)
When participant filters were last evaluated (participant_state trigger only)
When this automation last fired (cron trigger only)
Human-readable label for this automation
When this automation will next fire (cron trigger only)
CEL expression that determines which participants are enrolled
Target participant for program-scoped one-time automations
Participants processed so far in the current fan-out run
Total participants to process in the current fan-out run
Custom data included in the generated event
When this one-time automation was processed
The program this automation belongs to
Configuration for the schedule type (participant_state trigger only)
How participant subscriptions are scheduled: ATTRIBUTE_DATE, INTERVAL, CRON, or THRESHOLD (participant_state trigger only)
Whether the automation fires once at the program level or fans out per participant: program or participants
How this automation was created: api or rule_action
Current state: active, paused, completed, failed, or archived
IANA timezone used for scheduling (e.g., America/New_York)
When this automation is scheduled to fire (one_time trigger only, RFC 3339)
How this automation is triggered: cron, one_time, participant_state, or immediate
When this automation was last updated