When an automation is triggered by an event from your connected app, e.g. Carerix, Salesforce, etc., a Run is created. This Run represents the full process that follows from the initial trigger to each step of your automation. In this article, we will walk through what runs are, how to find and read them, and how they can help you troubleshoot your automations.
What is a Run
What is a Run
A run is the result of an automation being triggered. It shows the exact sequence of actions that took place after an event was received, for example, a filter being checked, a delay being completed, or an email being sent/conversation ended. Each Run includes a full timeline of the steps taken, an Overview, Fields, and Related tabs.
Once a run is successfully completed, it will be reflected in the Task History page by adding a new task to the list.
How to filter Runs
How to filter Runs
Navigate to the Settings menu and open the Runs page to see a list of all runs:
Use the filters for a more organised view, for example, if you want to see the runs associated with one of your connected apps, or by narrowing them down by the state/stage they are currently in.
Filtering runs by an app:
Filtering runs by their state:
Filtering runs by their sub-state:
How to view Run details
How to view Run details
To explore an individual run, click the [Details] button next to the run for a short overview or open the dropdown menu and click [View Run].
This will open the run's detail view, which includes:
Overview – a summarised view of the data received from your app.
Fields – fields with the data in the event that triggered the automation and might have been used in the run.
Related – the automation this run followed and the event that triggered it.
This detailed view also allows you to see exactly how your automation played out and whether each step succeeded.
Troubleshooting Runs
Troubleshooting Runs
If something didn’t happen as expected:
Open the detailed view of the run to view logs and see if a step failed or was skipped.
Open the Fields tab to confirm whether the data used in the run met your conditions. You can also compare the run with the original event (found via the Related tab) to understand what triggered it and confirm if it used the correct data.
Still need help?
If you're unsure why a run was cancelled/completed or want help interpreting the run's steps, feel free to contact our team at [email protected]. If you do, please include:
A link or the ID of the run;
Any relevant data or context that might help us investigate further.