Workflow troubleshooting
Check why a workflow did not run or send a result.
Open Workflows → History and select the latest run. Start with its status and then check its result and Delivery record.
| What happened | What to check |
|---|---|
| No run appears | Is the workflow published and unpaused? Is its trigger scheduled or waiting for an event? |
| No-op | The trigger ran, but its conditions matched nothing. Check scope and thresholds. |
| Blocked | Check credits and the status of each required connection. |
| Failed | Read the error on the run and retry after fixing the cause. |
| Completed, but no message arrived | Check that Notify exists, then inspect each channel in Delivery for a skipped or failed status. |
An unpublished draft never runs on its trigger. Run now can test it. Some specialist reports are manual only; the current executor rejects scheduled CSA and reconciliation pilot runs. See Workflow blocks.
If a source is missing, check access, organization, and connection status. For a Slack delivery, check the workspace and member setup. If you still need help, contact support with the workflow link and run time, but no sensitive source data.
If a reconciliation result says No new report, read the reason and Requested reconciliation date. A Previous saved report is shown separately; its counts are not new findings. Missing current balance records do not mean zero. Retry when the required data is available.