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 or a WhatsApp message.
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 a warning 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 the Policy allows it.

Counts only, so they are shown whatever the privacy mode.


Active automations	Running on their schedule.
Paused	Paused by a user, a contributor, or the policy.
In error	Stopped automatically.
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.


Search	Name or instruction.
User	One creator. Defaults to all users.
Status	Active, Paused, Disabled, Error, Completed.
Trigger	Time or Event.
Action	Create conversation or Send WhatsApp.
Created From / Created To	Date range.
Sort By	Created At, Last Run or Next Run.
Order	Descending or ascending.


Automation	The name. Shows "Hidden — privacy mode" when the content is sealed.
User	The creator. Falls back to the user id when the name and email are hidden.
Trigger	Time or Event.
Schedule	A readable summary, for example "Every day at 08:00 (Asia/Jakarta)".
Action	One chip per action.
Status	A coloured chip: Active, Paused, Disabled, Error or Completed.
Last Run · Next Run · Created At	Date and time.
Row	Select a row to open the details drawer.
Pagination	10, 20, 50 or 100 per page.


Header	The name, status chip, and the reason for the status.
Privacy Notice	When content is sealed: "This automation's content is encrypted under the organization's privacy mode. Staff see only when and how it runs."
Original instruction	The user's own words.
Trigger	Kind and schedule summary, plus "until" an end date and "at most" a number of runs when set.
Condition	"None — the task runs every time", or the description, the all/any logic, and each rule.
Task	What the agent does each run.
Skills	The skills attached to the run, or None.
Action	One chip per action.
WhatsApp recipient	Shown only when Send WhatsApp is an action.
Created by · Created at	The creator and when.
Last run · Next run · Runs so far	Progress of the automation.

Shown in the drawer. Needs Can view execution history; otherwise a warning says who can grant it. Kept for the policy's History Retention.


Scheduled For	The time the run was due.
Kind	Scheduled, Run now, Retry (with attempt number) or Catch-up.
Status	Running, Succeeded, Condition not met, Failed, Skipped, Timed out or Abandoned — with the reason underneath when there is one.
Condition	No condition, Met, Not met, or Unknown (treated as met).
Actions	Each action's outcome: Sending, Sent, Failed or Skipped.
Duration	How long the run took.
Content	Never shown. The result itself lives in the user's conversation.

Buttons at the bottom of the drawer. Pause, Resume and Disable 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 Disabled automations. Checks the policy again.
Disable	For anything not already disabled or finished. Asks for confirmation. The user can no longer resume or edit it, but can still delete it.
Delete	Asks for confirmation. Removes it for the user too; cannot be undone. Run history remains until its retention ends.


Active	Running on its schedule.
Paused	Stopped for now, by a user, a contributor, the policy or an agent transfer.
Disabled	Switched off by a contributor.
Error	Stopped automatically after repeated failures, or because the policy or the user's access no longer allows it.
Completed	No future runs. Removed after 7 days.

For the reason texts and what to do about each, see Troubleshooting Runs.


Sealed Content	Name, instruction, condition, task, skills, WhatsApp number, and the creator's name and email are hidden as "Hidden — privacy mode".
Still Shown	Schedule, action, status, run times, summary counts and run history — operational metadata.
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.

See Monitor and Govern for the full explanation, and Managing Agent Access for the permission switches.