Read run statuses and event logs
Translate each run status into the next customer action and use the timeline before changing a profile.
When to use this
Use this reference when a run stops moving, ends below target, or shows a warning or failure.
Requirements and availability
- Open the exact run so the diagnosis is based on its events.
How to do it
- Open Runs.
- Open the affected run.
- Read outcome, requested and delivered counts, timestamps, and duration.
- Read the timeline from oldest to newest; error is more severe than warning, then info.
- Follow the next action named by the most recent relevant event.
Fields and controls
| Control | What it does |
|---|---|
| Queued | Waiting to start. |
| Running | Actively changing. |
| Completed | The run ended; Delivered, Partial, or No prospects describes the count outcome, not a separate CRM receipt. |
| Failed | Ended because an operation failed. |
| Blocked | A prerequisite or restriction prevented progress. |
| Cancelled | Ended early after a Stop request or a system cancellation. Read the event log for the actual reason. |
| Stopped (low yield) | Ended because continued sourcing was not producing enough qualified records. |
| Setup required | Complete the named setup before retrying. |
What happens next
The event log gives the closest customer-visible explanation for the selected run. Run status, run count outcome, stored prospect state, and destination delivery are separate facts; a 'Delivered' run label alone does not prove ClickUp or CRM arrival.
States you may see
| State | Meaning |
|---|---|
| Info | Normal progress or context. |
| Warning | A condition affected progress or result quality. |
| Error | An operation failed and may need retry or support. |
Credits and usage
Opening logs does not use credits. Do not retry until the prior request is terminal.
Common problems
| Problem | What to check |
|---|---|
| The latest event is unclear | Contact support with the run, time, status, and exact safe message. |