Automation Runs

Open The Runs Dialog

1. On the Automations page, select the three dots in the required automation row.

2. Select Runs in the menu.

3. Wait for the Runs dialog to open over the list. You do not need to navigate to a separate page.

In the open dialog:

1. The left side contains the selected automation's runs, grouped by day.
2. Each run shows the dialog and its channel, start time, status, and short run number. If the run has no dialog, Without dialog appears instead of a name. Test runs have a Test label.
3. The add filter button helps find the required run.

The first run is selected automatically. Select another row to review a different run. If the automation has not run yet, the list is replaced by the No runs yet message. New runs and status changes appear automatically while the dialog is open.

Filter The List

The filter block can combine several conditions:

• status: active, paused, completed, failed, or cancelled;
• run type: production or test;
• start period;
• a lead: use search and select the required row;
• a dialog: use search and select the required row;
• a full run ID. Paste all 24 characters into the ID field: the run loads directly even if it is not among the latest runs.

The cross next to a filter removes only that condition. Reset clears all conditions.

Review A Run And Its Steps

If the automation editor is already open, select More actions, then select Runs. This opens the same dialog.

The selected run header shows its short number and current status. The summary may also contain the full ID with a copy button, start and finish times, duration, current and original workflow versions, migration count, run type, links to the lead and dialog, and the source event ID. Only data available for that run is shown.

The variable icon opens this run's current variables, showing each {{run.name}} template and its stored value. Internal execution data is not included in this list.

The timeline below groups completed and current steps by day. Each step shows its name, execution time, status, and the attempt number out of the maximum allowed. Even if a step is later deleted from the automation, its name normally remains in the history. If the name is unavailable, the step's internal number appears instead.

The same timeline shows Button click and Branch transition events. They list the next steps or the absence of a configured connection, the event ID, and the result: Started, No connection, Duplicate, or Rejected. This distinguishes a successful continuation from a repeated event or a branch without a next step.

While a run is active or paused, new steps appear at the bottom of the list. If you scroll up, the list stays at the selected position and does not interrupt your reading. After the run finishes, the most recent events appear first.

When a step fails, its error message appears directly below it. For diagnosis, find the first step with the Failed status and read that message.

The latest failed attempt for a step has a Retry step button. It creates a new attempt for that step in the same run; completed actions are not rolled back or run again. The button is absent while an automatic retry is already scheduled and when a newer attempt exists after the failure. Manual retry requires permission to manage automations.

You can pause an active run. Its current step finishes, then continuation stops. Select Resume to execute the following steps again.

Cancel run stops it permanently. After confirmation, this run cannot be resumed. Use pause when the stop should be temporary.

Understand The Statuses

Run Statuses

• Active means the run is still executing steps;
• Paused means continuation is stopped until the automation resumes;
• Completed means all run steps finished;
• Failed means a step could not be completed;
• Cancelled means the run was stopped.

Step Statuses

• Queued means the step has not started yet;
• Running means the step is executing now;
• Waiting means the step will continue at its scheduled time;
• Paused means the step was stopped together with the automation;
• Retrying or Step failed, retrying means the current attempt failed but another attempt is already scheduled;
• Completed, Failed, and Cancelled are final step outcomes.

Permissions

The permission to view automations is sufficient to open the dialog and review runs. Pausing, resuming, cancelling, and manually retrying a step require permission to manage automations.