Using Workflow Launch History
Track the number and status of workflow launches and check for errors in workflow blocks.
- Go to Automation ā Workflows.
- Click the Launches icon for the required workflow.
- In the Show launches dropdown menu, select one of the following:
- In progress ā launches that are still running;
- Completed ā launches completed without errors;
- With errors ā launches during which an error occurred;
- Last 7 days ā launches whose start date falls within the last seven days;
- Launch statuses per segment ā launches for a segment of contacts. This option is available only for regular workflows for a segment.

NoteYou can also open the workflow launch history directly in the editor. The Show launches dropdown contains the same filters and uses the same counting rules in both entry points.

When you select Launch statuses per segment, a side panel opens with the following information:
- Group ID
- Workflow launch date and time
- Number of contacts in the segment
- Launch status

To view the contacts included in the segment, click the preview icon.
Launch History
Launch history contains the following data:
- Launches ā individual instances of the same workflow. Each launch runs independently and may have a different result.
- Blocks activated during each launch.
- Block and context parameters.

For condition blocks, the check result ā true/false, yes/no, or the branch percentage for Split ā is displayed directly in the block's row in the list, so you don't need to open the block to see the outcome.

NoteThe number of triggering events and the number of launches don't always match. If the workflow uses a uniqueness condition, duplicate events that share the same uniqueness key collapse into a single launch ā so a lower launch count than event count doesn't necessarily mean events were lost.
The Show launches menu displays the following status filters:
- In progress
- Completed
- With errors
The number next to each filter shows how many matching launches were counted. Click the ? icon next to Show launches to view the counting rules.
The counters use different date references:
- In progress includes every launch that hasn't finished yet, with no filter by start date.
- Last 7 days is counted by launch start date.
- Completed is counted by launch completion date. A completed launch is kept for seven days after it finishes, no matter when it started.
- With errors can include both finished and running launches. For a finished launch, the completion date applies and the same seven-day period is used.
Because different dates are used, the Last 7 days total may not equal the sum of the status counters. For example, a launch may have started more than seven days ago but completed within the last seven days. In this case, it is included in Completed but not in Last 7 days.
NoteA gap between the number of incoming events and the number of messages actually sent is generally explained by workflow condition filtering and by re-trigger restrictions on events that repeat with the same required parameters ā not every matching event necessarily results in a new send.
Contacts without a media channel are another reason. Messages aren't sent to them and they don't get into the campaign report, but the workflow launch for such contacts is still recorded in the launch history. Because of this, the number of launches can exceed the total of sent and unavailable contacts shown in the report.

Workflow Launch Viewing
- Hover over the required launch and click the view icon.

- The Workflow's launch view window opens. The execution path for that launch is highlighted in blue.

- Select a block to view its settings in the right pane. The settings are view-only ā you cannot change them in this window.

Click the three-dot icon to view the campaign report.

NoteThe report opens for the channel used for the first send. For example, if the first send was an email, the corresponding email campaign report opens. More details about campaign reports ā
The Refresh button allows you to manually update data for launches and blocks with the In progress and Completed statuses.

Launch Errors
Workflows and blocks containing errors are marked with a warning icon.
Select a workflow launch with an error, and then select the block where the error occurred.
The right pane displays the block and context parameters, along with the error description highlighted in red.

No contact history found using the current algorithm ā this error appears for recommendation-based triggers, such as Abandoned Category or Price Drop, when the algorithm cannot find the required web-tracking events for the contact within the configured lookback window. For example, the required page-view events may be missing.
Common causes:
- The contact is not being tracked ā verify that web tracking is installed and events are recorded for this contact.
- The lookback period configured for the algorithm is too short for the contact's browsing behavior.
Per hour emails limit reached: N ā this error appears on email message blocks when the account's hourly limit on single email sends is exceeded; N is the current limit value (100 emails per hour by default). To increase the limit, contact support. For details, see Rate Limits.
Search and Filter Launches
To load more launches, scroll down the list and click Show more launches.

You can also use the search bar to find a launch by block or context parameters.

The Period tab offers ranges from the last three hours up to Last 7 days, which is selected by default. Custom ranges and periods longer than seven days are not available.

Stopping a Workflow Launch
You may need to stop a workflow launch if it contains errors, is no longer relevant, or the workflow must be changed before execution continues.
- Open the In progress launches, hover over the required launch, and click the Stop icon.

- Confirm the action.
To stop all active launches, click Stop all.

The aggregated figures on this page can't be pulled through the API ā export them from the interface. To feed a BI tool with the underlying data instead, use webhooks, the Get contacts activity resource, or the export to BigQuery.
Updated 11 days ago