Policy
Open in CMSPurpose and Access
| Automation Policy | Decides whether the users of this agent may set up automations — tasks the agent runs on a schedule for them — and within which limits. |
| Page Access | Agent Owners and Contributors. |
| Applies | At once when saved, without publishing the agent. |
| Checked | When an automation is created or changed, and again at every run — so a tighter policy binds automations made under a looser one. |
| Default | Off. Until someone switches it on, the agent offers no automations. |
Master Switch
| Let users create automations on this agent | Off by default. While off, the agent offers no automations and existing ones are skipped when due — nothing is deleted. On lets users ask the agent to run a task on a schedule and deliver the result as a new conversation or a WhatsApp message. |
What Users May Automate
| Allowed Triggers | Multi-select. Only Time (schedules) is available; event triggers are not available yet. At least one is required. |
| Minimum Interval (minutes) | The shortest gap allowed between two runs of one automation. 5–10080, default 15. Automations that run more often are stopped. |
| Allowed Actions | Multi-select: Create conversation, Send WhatsApp message. At least one is required. WhatsApp goes to the number the user gives, from the platform's shared numbers. |
| Maximum WhatsApp Messages per Day | For all of this agent's users together. 1–5000, default 100. Applies only while WhatsApp is an allowed action. |
Limits per User
| Maximum Active Automations | Running at the same time. 1–100, default 10. Lowering it pauses the newest ones above the limit. |
| Maximum Total Automations | Active and paused together. Up to 200, default 20. Cannot be lower than the active limit. Finished ones do not count. |
| Maximum Runs per User per Day | All of one user's automations on this agent together. 1–1000, default 100. Every run spends credit. |
| Maximum Runs per Automation | 0 means no limit, up to 100000. An automation that reaches it is finished. |
Running
| Run Timeout (seconds) | How long one run may take. 60–900, default 300. |
| History Retention (days) | How long run history is kept. 1–365, default 30. |
| Maximum Retries | Retries after a temporary failure. 0–5, default 2. A WhatsApp message is never sent twice. |
| Retry Interval (minutes) | The wait before a retry. 1–1440, default 5. |
What Users May Do
Six switches, all on by default, for users' own automations.
| Create automations | Off stops new automations; existing ones keep running. |
| Edit automations | Change the schedule, task, condition, actions or recipient. |
| Delete automations | Off leaves users only able to pause. Owners and Admins can still delete from the Monitor. |
| Pause and resume | Stop an automation for a while and start it again. |
| Run now | Run an automation immediately instead of waiting for its schedule. |
| View history | See when each automation ran and how it ended. |
| Contributors | Not limited by these switches — they govern every automation from the Monitor. |
Save and Sync
| Last Changed | Shows when the policy was last saved. |
| Save | Validates every field with the same rules the server uses, and shows the problem beside the field. |
| Conversation Service Status | Up to date: the chat service has the latest policy. Has not received the latest policy: a warning with a Resend action. Could not check: an informational note. |
See Set Up the Automation Policy for guidance on choosing values.