Monitor and Recover Workflow Runs

A workflow run is one record’s journey through a live workflow. Open the Workflows tab of Automations, then open a workflow and use its activity list to review the runs it has created. The list can be searched and filtered, and opening a row shows that run’s timeline, the steps it reached, and the run events recorded for it.

Read run status before taking action

The status label describes the record’s current journey:

• Finished means the run completed.
• In progress means it is continuing through its steps.
• Waiting to start or Waiting to send means it is queued. A run waiting for a sending slot resumes on its own; it does not need to be restarted.
• Paused means the run is intentionally stopped. Its detail view can show the reason and whether resuming will retry the affected step.
• Needs attention means the run stopped at a condition that may require review.
• Stopped means the run is no longer progressing.

Open a run rather than relying on its table label alone. The detail view shows the run’s timeline and related records, and a queued-send message explains when Goliath will make another sending attempt when that information is available.

Pause or resume one run

In the activity list, hover over a run to reveal Pause run or Resume run, when that control applies. You can also open the run and use the control in its detail view. Pausing is available for runs that are in progress or waiting; resuming is available for paused runs.

When a paused run has a recoverable reason, the detail view tells you what to correct. For example, it can identify a blocked text, a failed send, an unavailable sender, or a step error. Correct the underlying problem before selecting Resume and retry step. That action retries the step where the run paused.

Do not resume a run merely because a message is waiting for capacity. The run detail explains that queued sending continues automatically. A message that is too old to send is different: the run detail advises stopping that run and starting a fresh sequence for the record instead.

Control multiple runs

Select runs from the activity list to reveal a selection bar with Pause and Resume. These controls operate only on runs that can transition: terminal runs are left unchanged. Use the search and filter controls first so the selection matches the exact records you intend to change.

Pause or resume workflows for selected contacts

To pause the workflow runs a group of contacts is going through, start from Contacts instead of a single workflow. This pauses workflow runs only, and only for the contacts you select. To hold every automated message to your contacts at once, from workflows and AI employees alike, see Pause all automated sending.

1. Open Contacts and select contacts in the table, or select every contact that matches the current filter.
2. In the bulk action bar, open More and select Pause workflows.
3. Choose Pause or Resume, then keep All workflows or pick specific workflows.
4. Select the button to submit. When the background task finishes, the notification reports how many runs changed and how many were skipped.

Pause stops each in-progress or waiting run where it is. Resume only restarts runs that were paused by hand, from here or from a workflow’s activity list. It does not restart runs held because their workflow was paused or replaced by a newer version; resume those from the workflow itself. Runs held because Goliath suspended their workflow cannot be resumed by hand, here or from the workflow’s activity list: see Publish, pause, and resume workflows for what to do. Runs that cannot change are skipped, never errors.

Some workflows are system-managed and read-only. Their banner names what maintains them. You can review their runs there, but you cannot pause or resume individual runs.

For publishing decisions that affect new enrollment and in-flight work, see Publish, pause, and resume workflows. For deliberately enrolling selected records, see Manually trigger workflows.