​
What is the Runs Monitor?

The Runs Monitor is a dashboard that allows you to view, track, and analyze the execution of your Automations. It provides a comprehensive overview of all the runs (executions) of your Automations, including their statuses, durations, and other key metrics.

​
Key Features of the Runs Monitor

​
1. Run List

  • Displays a table of all Automation runs
  • Shows key information like Automation ID, version, run status, duration, and more
  • Allows sorting and filtering of runs

​
2. Date Range Selection

  • Enables you to view runs within a specific time frame
  • Includes a date picker for easy selection of start and end dates

​
3. Column Customization

  • Allows you to show/hide specific columns in the runs table
  • Customizable columns include Automation ID, Version, Name, Run ID, Inputs, Step Count, Started By, Start Time, Status, Steps Completed, and Run Duration

​
4. Filtering and Searching

  • Provides a search bar to quickly filter runs based on Automation ID
  • Supports keyboard shortcut (”/”) for quick access to the search function

​
5. Detailed Run View

  • Clicking on a run opens a sidebar with detailed information about that specific run
  • Shows all available data for the selected run

​
6. Real-time Updates

  • Includes a loading indicator to show when new data is being fetched
  • Displays the total number of runs currently visible

​
When to Use the Runs Monitor

​
Debugging during build

When you’re developing an automation, especially when you’re using triggers, the runs monitor is where you’ll go to see what happened after your trigger fired.

​
Troubleshooting

Sometimes an automation will start to fail or will fail occasionally. The runs monitor is where you’ll go to

  • Learn about failures (if you didn’t already know)
  • See the inputs that were used
  • See the result from each step, including success/failure of API calls or browser automations

​
Performance Analysis

If you’re trying to optimize an automation, the runs monitor is where you’ll go to see how long it took and how many steps it completed.

​
Auditing

If you need to audit what happened in a sequence of automations or in a sequence of steps, the runs monitor is where you’ll go to see the history.

  • See when each step started and finished
  • See who (or what, in the case of a trigger) started the automation
  • See who the automation communicated with and what data was sent and received

​
A note about logging

To get the most out of the monitor, you can take advantage of the logging function in your automations. This will make it easier to find the information you need in the runs monitor. To use the logging funtion, add to your prompt what you want to log specifically or just generally. For example:

Here’s a specific example:

/gmail loop through contacts list, send email to each contact using template "email-template"
log: 
 - complete email payload before sending 
 - log the result of each email send
    -- success or failure
    -- error message if it failed
    -- the email address that was used
    -- the id of the contact that was used (not part of the payload)

Here’s a more general example:

/gmail loop through contacts list, send email to each contact using template "email-template"
log: information that will be helpful in debugging and auditing
ConnectionsLibrary