The Automations Monitor shows the automations users set up on this agent and their runs, and lets you pause, resume, turn off or delete them. Found in the agent sidebar under Automations → Monitor.
Purpose and access
| |
|---|
| Automations Monitor | Governance over the automations users created on this agent: scheduled tasks that run on their own and deliver the result as a new conversation, a WhatsApp message or an email. |
| Page access | Agent Owners and Contributors. |
| Permission | Organization Owners and Admins always have it. A Contributor needs the Can view automations switch on their card; without it the page shows Automations are not available to you and requests nothing else. |
| Read-only content | The Monitor never edits an automation. Users create and change theirs by talking to the agent. |
| Empty list | Users create automations by asking the agent in a conversation, once your organization's rules in the Policy allow it. |
Summary cards
Counts only, so they are shown whatever the privacy mode.
| |
|---|
| Active automations | Running on their schedule. The line under the number reads Running, or None running. |
| Paused | Paused by a user, a contributor, or your organization's rules. Not running, or None paused. |
| Stopped | Stopped automatically. Needs attention, or All clear. |
| Users with automations | People with at least one automation on this agent. |
| Runs today | Runs that started today. |
| Failed runs today | Runs that failed today. The line reads, for example, "1 of 4 runs", or No failures. |
Search and filters
| |
|---|
| Search automations | Name or instruction. |
| Filters | Opens the panel with the sort order and the filters below. Clear all resets them. |
| Status | Active, Paused, Turned off, Stopped, Finished. |
| Starts | On a schedule, or When something happens. |
| What it does | Create conversation, Send WhatsApp or Send email. |
| User | One creator. Defaults to all users. |
| Created from / Created to | Date range. |
| Sort by | Created date, Last run or Next run, ascending or descending. |
Automations table
| |
|---|
| Automation | The name. Shows "Hidden (private)" when the content is private. |
| User | The creator. Falls back to the user id when the name and email are hidden. |
| Starts | On a schedule, or When something happens. |
| Repeats | A readable summary, for example "Every day at 08:00 (Asia/Jakarta)". |
| What it does | One chip per action. |
| Status | A coloured chip: Active, Paused, Turned off, Stopped or Finished. |
| Last run · Next run · Created | Date and time. |
| Row | Select a row to open the details drawer. |
| Pagination | 10, 20, 50 or 100 per page. |
Details drawer
| |
|---|
| Header | The name and the status chip. |
| Private notice | When content is private: "This automation's content is private under your organization's rules. Staff see only when and how it runs." |
| Original instruction | The user's own words. |
| Starts | On a schedule, or When something happens. |
| Repeats | The schedule summary, plus "until" an end date and "at most" a number of runs when set. |
| Runs only if | "Nothing. It runs every time.", or the description, "Any of these is true" or "All of these are true", and each rule. |
| What it does | What the agent does each run, with the action beneath it. |
| Skills | The skills attached to the run, or None. |
| WhatsApp recipient | Shown only when Send WhatsApp is an action. |
| Email recipient | Shown only when Send email is an action. The address the email goes to: the one the user gave, or their own account's address. |
| Created by · Created at | The creator and when. |
| Last run · Next run · Runs so far | Progress of the automation. |
| Status note | The reason, when the automation is not active. |
Run history
Shown in the drawer. Needs Can view execution history; otherwise Run history is not available to you says who can grant it. Kept for the number of days your organization's rules set.
| |
|---|
| Scheduled for | The time the run was due. |
| How it started | On schedule, Run now, Tried again (with attempt number), Late start or By an event. |
| Status | Running, Done, Not needed, Failed, Skipped, Took too long or Gave up, with the reason underneath when there is one. |
| Condition met | Runs every time, Yes, No, or Unknown (ran anyway). |
| What it did | Each action's outcome: Sending, Sent, Failed or Skipped, with the reason when it failed (for example "Daily email limit reached"). |
| Duration | How long the run took. |
| Content | Never shown. The result itself lives in the user's conversation. |
Governance actions
Buttons at the bottom of the drawer. Pause, Resume and Turn off need Can pause, resume and disable; Delete is for Organization Owners and Admins.
| |
|---|
| Pause | For Active and Stopped automations. Stops it; the user can resume. |
| Resume | For Paused, Stopped and Turned off automations. Checks the policy again. |
| Turn off | For anything not already turned off or finished. Asks for confirmation. The user can no longer turn it back on or edit it, but can still delete it. |
| Delete | Asks for confirmation. Removes it for the user too; cannot be undone. Run history is kept for the number of days your organization's rules set. |
Statuses
| |
|---|
| Active | Running on its schedule. |
| Paused | Stopped for now, by a user, a contributor, your organization's rules or an agent transfer. |
| Turned off | Switched off by a contributor. |
| Stopped | Stopped automatically after repeated failures, or because your organization's rules or the user's access no longer allow it. |
| Finished | No future runs. Removed after 7 days. |
For the reason texts and what to do about each, see Troubleshooting Runs.
Privacy Mode
| |
|---|
| Private content | Name, instruction, condition, task, skills, WhatsApp number, email recipient, and the creator's name and email are hidden as "Hidden (private)". |
| Still shown | Schedule, action, status, run times, summary counts and run history: operational metadata. |
| Delivered results | A WhatsApp message or email still carries the full result, because that is what the user asked for. |
| Priority | Privacy Mode overrides contributor permission. |
| Transcripts | The hidden task message and automation tool arguments are redacted on CMS conversation pages unless the reader may view automations. |
For the permission switches, see Managing Agent Access.
Related guide: Monitor and Govern