Automation run completed

A run of one of the newsletter's automations reached the end of its graph. Every step it was going to take has been taken.

A run is one subscriber's passage through one automation, so this fires once per person per entry rather than once per automation. Read GET /runs/{run} for the step history; this message carries the outcome, not the walk.

actor names the run, not a credential. Every automation.run.* message carries actor: {"type": "system", "id": "<run_id>"}, which is the same attribution Commune puts on the events a run's own actions cause, such as the subscriber.tagged of an add_tag step. That is what the loop guard reads: a run started by this message inherits this run's chain plus this run's automation, so an automation triggered by its own runs starts one further run and is then refused. data.chain_depth is how many automations' actions already led here, out of a limit of five.

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.