Track Executions

A running scenario leaves a trace. The Executions page of the Automation hub gathers them all, from the most recent to the oldest, to answer the two recurring questions: “why did nothing happen?” and “why did it do that?”.

One Line per Trigger

Each time an active scenario is triggered — form submitted, appointment made, comment received, scheduled time reached — an execution is created. The line indicates:

• the scenario concerned;
• the result: successful, failed, or in progress;
• the trigger that launched it;
• the start date and duration;
• the number of steps taken and any error (columns to be displayed via Customize Columns).

A scenario that has reached its daily execution threshold also appears: the execution is marked as failed, with the reason.

Execution Details

Click on a line. The record shows the progress: each node in the order the engine traversed it, with its verdict.

• A trigger recognized or not concerned by the event.
• A rule and the branch taken (“Yes”, “No”, a case of the switch).
• A scheduled delay with the resumption time.
• An action executed, or failed with the error message.

At the bottom, the received event can be expanded: these are the exact data that fed the scenario, useful for verifying that a variable indeed existed.

Resumptions After a Delay

When a scenario contains a delay, the continuation executes later, sometimes several days after. This resumption appears as a separate execution, with the trigger “Resumption after …” followed by the name of the delay node. If the scenario was paused in the meantime, the resumption does not occur.

Filter and Search

The Filter button offers the result and the scenario. From a workflow's record, the View Executions button opens the page already filtered on this scenario. The search covers the scenario name, the trigger, and the error message.