Skip to main content
New An organization’s automations, what each one does, and every time one has run. Start here when a customer reports that an automation stopped working.

​
Prerequisites

  • You need Platform Admin access

​
Open the automations list

  1. In the Platform Admin App, open Accounts and select the account.
  2. Select the organization.
  3. Select Automations.
Automations appear newest first, 25 to a page. Paused, disabled and expired automations are listed alongside active ones — a switched-off automation is the most common answer to the question you are investigating.

​
What each row shows

Search matches the name, description, trigger and automation ID. Status narrows the list to one lifecycle state. Sort by Last run to bring the automations that have gone quiet to the bottom of the list. Filters live in the page address, so you can share or bookmark a filtered view.

​
Read an automation’s definition

Select an automation to see:
  • The trigger that starts it, when it next runs, and when it expires.
  • Its lifecycle: whether it is enabled and active, when it was switched off and why, and how many runs it has used against its cap.
  • The agent it runs as and the tools it is allowed to call.
  • Its last error, when it has one.
  • The instructions the customer wrote.
  • The generated code it runs, under Show. Customers never see this; it is the fastest way to tell what the automation actually does.
Below the definition is that automation’s own run history. A deleted automation still opens from its address, and is marked as deleted, so a link in an old ticket keeps working.

​
Review every run in the organization

Select All runs on the automations list for the whole organization’s run history, newest first — the fastest way to tell whether anything is running at all. Filter by status, and bound the range with From and To. Both are UTC, and both include the minute you select.

​
Read a run

Select a run’s start time to open it. The run detail shows when it started and finished, how long it took, which attempt it was, and the event that triggered it. When the run failed, it also shows the error, whether the failure was retryable, and an automated diagnosis when one exists. Steps lists each tool the automation called, in order, with how long the call took and what it returned. A step that failed opens expanded, with its error. Select any other step to see the arguments it was called with. Not every run carries a step log. When one wasn’t recorded, the page says so rather than showing an empty list. Very large arguments, results and code blocks are shortened, and the page marks where it cut them.
These pages are read-only. Retrying or cancelling a run is a separate capability. Viewing an automation or a run is not recorded in the audit log.
Last modified on September 6, 2026