Runs and history
Find a workflow result and check whether it was delivered.
Each time a workflow starts, it creates a run. Open the workflow, then History, and select a run to see what happened.
| Status | Meaning |
|---|---|
| Queued or Pending | Waiting to start |
| Running | Still working |
| Completed | The run finished and saved a result; check delivery separately |
| No-op | The conditions matched nothing, so there was no result to send |
| Blocked | Something required is unavailable, such as a connection or credits |
| Failed | The run ended with an error |
| Cancelled | The run stopped before finishing |
Check a result and its delivery
- Open the run and read its saved result, sources, and dates.
- Open Delivery in that run. Check each channel's status and any skipped reason.
- If email or Slack did not arrive, use the delivery status to decide what to fix. A Completed run alone does not prove the message was sent.
See Delivering results and Workflow troubleshooting.
For a saved CSV, open Artifacts beside History, then select Download or View run. Access follows the workflow's permissions. A report may exist even if a later delivery step failed; review the report's limitations before using it.
To inspect an older workflow configuration, open its version history. Restoring an earlier version creates a draft; it does not replace the published version until you publish it.