The Workflow Runs area lets you monitor every time a workflow runs. You can see which contacts entered a workflow, what status each run is in, and open the run details to review what happened step by step.
This opens the full list of workflow executions across your account.
The Workflow Runs list shows one row for each workflow execution. Common columns include:
| Column | Description |
|---|---|
| Actions | Options such as View details or View template. |
| # | The run number. |
| Name | The workflow name, along with the related contact, owner, and category information. |
| Status | The current state of the workflow run. |
| Started at | The date and time the run began. |
Each run can show one of the following statuses:
| Status | Meaning |
|---|---|
| Running | The workflow is actively executing for that contact. |
| Waiting on queue | The run is queued and waiting to be processed. |
| Waiting for event | The workflow is paused until something else happens, such as a task being completed. |
| Waiting for delay | The workflow is paused at a Wait node and will resume later. |
| Completed | The workflow finished successfully. |
| Failed | The workflow encountered an error and could not continue. |
| Terminated | The run was manually stopped. |
| Filtered | The contact entered the workflow but did not pass a filter condition, so the run stopped. |
Use the search bar to find runs by workflow name, contact name, email, or phone number. You can also narrow the list with filters such as:
This helps you quickly locate runs that need attention, such as failed, terminated, or filtered runs.
To open the full execution history for a run:
The detail view shows:
This view is especially useful for troubleshooting why a contact did or did not receive a message, task, or update.
If a workflow run is still in progress, you can stop it manually from the detail view.
Once terminated, the run stops immediately and the remaining workflow actions do not execute.
Important: Terminating a run does not delete it from history. It only stops that run from continuing.
It means the contact entered the workflow but did not match a filter condition, so the workflow stopped for that contact.
Yes. You can manually trigger the workflow again for the contact if the workflow supports manual runs, or you can let it trigger again naturally if the trigger conditions occur again.
No. A terminated run only stops that specific run. It does not create a permanent block unless the workflow also uses an Exit Step.
Open the run details and review the step-by-step execution history. That will usually show whether the run was filtered, waiting, failed, or stopped before reaching the action.
Some workflow-related views may include reporting options, but the main use of Workflow Runs is monitoring and troubleshooting inside LeadCenter.
If you need help reviewing workflow runs, contact support@leadcenter.ai.
If you can’t find the answers you’re looking for, our support specialists are available to answer your questions and troubleshoot if necessary.