Review workflow runs
Last updated: August 10, 2026
Workflow Runs records each contact's path through an automation. Use it to confirm whether a workflow started, see the selected branch, and identify the last completed or failed step.
Find a run
Open Workflows.
Select Runs.
Filter by run status or search for the workflow name.
To find one contact, enter the exact contact ID.
Select Refresh when you expect a recent step to appear.
Expand the run to review its steps.
Control | What it does |
|---|---|
Status tabs | Shows All, Running, In Progress, Completed, or Failed runs |
Workflow search | Matches part of a workflow name |
Contact ID | Matches one exact contact ID |
Refresh | Requests the latest run data |
Understand the run columns
Column | What it shows |
|---|---|
Last update | The displayed age is currently based on when the run started |
Run Status | The overall state of the run |
Workflow | The workflow name and a link to its editor when the workflow still exists |
Contact | The contact and a link to the Inbox conversation |
Channel | The channels supported by the workflow |
Steps | Completed steps compared with the recorded total |
Deleting a workflow does not necessarily remove its historical runs. A deleted workflow's link may no longer open, but its recorded step history can still help with diagnosis.
Interpret run statuses
Run status | Meaning | What to do |
|---|---|---|
Running | A step is currently executing | Refresh after a short interval and inspect the active step |
In Progress | The run is deferred until a later time, commonly because of a Delay | Compare the delay duration with the run and step timeline |
Completed | The recorded workflow path ended | Expand the run to confirm which branch and actions completed |
Failed | A step or execution job ended unsuccessfully | Open the steps and inspect the last action and visible details |
A Completed status means the path ended. It can also represent a controlled early end, such as a branch ending the workflow or an ineligible contact being removed.
Review step history
Expand a run to view each step's action, status, timeline, and details.
Step status | Meaning |
|---|---|
Completed | The step finished or recorded a supported skip outcome |
Running | The step is currently executing |
Queued | The step is waiting for its execution time or a worker |
Yet to Start | An earlier step must finish before this step can begin |
Failed | The step did not complete successfully |
The Details column can show:
The action outcome and any available response message.
The branch selected and its matching path.
A queued delay and its next execution time.
Tags added or removed.
The assigned owner or changed contact state.
Webhook response and retry information when available.
An existing run uses the workflow definition captured when it started. Editing the workflow does not rewrite the steps shown for that run.
When a workflow did not start
Use this checklist in order:
Check | What to confirm | Related guide |
|---|---|---|
Workflow status | The workflow was Active when the event occurred | Set the workflow status |
Trigger event | The contact produced the exact direct-message, comment, tag, or schedule event configured | Configure workflow triggers |
Text comparison | The incoming text matched the operator's actual behavior | Configure message or comment text |
Channel | The contact's channel is selected and every action supports it | Select workflow channels |
Re-enrollment | A prior run did not make the contact ineligible for another entry | Configure contact re-enrollment |
Existing contacts | The trigger supports existing-contact enrollment and it was chosen before first activation | Understand existing-contact enrollment |
Autopilot | The workflow permits the relevant Autopilot-handled contact, when that setting is available | Configure Autopilot Compatibility |
Chaining | A workflow-originated event is allowed to start the receiving workflow | Allow workflow chaining |
Schedule | The minimum interval passed and every schedule condition still matches | Configure a Schedule trigger |
When a run is waiting
Check whether the active step is a Delay. A queued delay makes the run In Progress until its minimum duration passes and processing resumes.
If the configured duration has passed:
Select Refresh.
Confirm that the contact and workflow links still open.
Check whether a later step is now Running, Queued, or Failed.
Record the workflow name, contact ID, run start time, and waiting step before contacting Support.
When a run failed
Start with the final Running or Failed step:
Failed action | Common checks |
|---|---|
Send Message | Channel connection, recipient identity, messaging window, and message content |
Send Voice Message | Audio size, saved recording, text-to-speech availability, and tested channel support |
Reply to Comment | Triggering comment context, selected channel, and whether the comment was already replied to |
Change Contact Owner | Teammate still exists and weighted percentages total 100% |
Change Autopilot Handling | Autopilot availability and the contact's current owner and handling state |
Trigger Webhook | HTTPS URL, receiver response time, authentication handled by the receiver, and duplicate-safe retries |
AI Pick | Valid candidate messages, saved configuration, and a supported result for the test context |
The interface may not display every backend error returned for a failed step. If the visible details are incomplete, please contact Winly Support with the workflow name, contact ID, run start time, and failed step name.
Understand run controls
Workflow Runs is currently a monitoring view.
Setting a workflow to Inactive prevents new runs but does not cancel an active run.
Deleting a workflow prevents new runs but does not reliably stop a run already in progress.
Taking over a conversation from Autopilot does not stop its active workflow run.