Automations › Activity answers: what did this chain actually do?

Each row ties an execution to its chain, source event, entity, time, phase, and outcome. Open it when a live card, reminder, provider action, or scheduled delivery needs an audit trail.

Outcomes

Depending on the kind and step, activity can show outcomes such as:

• Completed.
• Reminded.
• Escalated.
• Condition met.
• Skipped.
• Cancelled.
• Failed.

Person-targeted delivery also distinguishes Delivered, Skipped, and Failed. A missing Slack binding is not rewritten as a successful DM.

Use it for

• Confirming a Review SLA reminder or owner escalation.
• Checking whether a wait condition stopped later steps.
• Seeing which PR, issue, deployment, workflow, or repository triggered a chain.
• Diagnosing a destination that was disconnected or not ready.
• Separating a report run from its later Slack announcement.

Activity is not dry-run

Dry-run is a no-side-effect replay of stored evidence. Activity records real executions after enablement. A dry-run result never appears as a delivered message.