Automation run started

An event matched a live automation's trigger and Commune created a run for it. The run is one subscriber's passage through that automation.

It fires when the run row is written, which is before the first step executes, so the email a send_email step sends has not been sent yet when this arrives. Pair it with automation.run.completed and automation.run.exited to know how the run ended; exactly one of those two follows every run that ends.

Nothing is published for a run that was not created. An event the trigger filter declined, a subscriber the reentry rule has already sent through, and a run the loop guard refused all leave no row and so no message. A creator's second automation that never fires is a question for the dashboard, not a silence this topic reports.

data.subscriber_id is null when the run's trigger is not about a person, which is every topic except the subscriber.* and delivery.* ones. Such a run can branch on its event and wait, but it has nobody to email or tag.

actor names this run. See automation.run.completed for what the loop guard does with it.

Delivered as a single HTTPS POST to the consumer's registered endpoint, with the message as the JSON request body. Respond 2xx to acknowledge. Anything else, or a timeout, is retried with backoff, so acknowledge fast and do the work afterwards.