Manage Your Automations
This page describes what your users see once they have automations: the Automations page in the chat app, the notification bell, and the controls on each automation. Knowing it helps you support them. It also shows what your policy switches actually change.
Everything here is in QA-Web, the public chat of your agent. It is only for signed-in people and is not shown in the CMS preview.
The running example is the automation that Rina Wijaya, Kirana's operations lead, created by chatting with Atlas: KG-2041 delay / on-hold check. Every weekday at 07:30 Atlas checks project KG-2041 and sends her a short summary, but only if the project is delayed or on hold.
Before you start
- At least one automation exists, created as described in Create an Automation. To follow along, create the KG-2041 check from that page.
- You are signed in to the agent's public chat (for Atlas,
https://app.qlar.ai/atlas-ops) with the account that created the automation.
Finding the Automations page
In the chat, open the sidebar with the ☰ button and click Automations. A signed-in user sees this entry while the agent's policy is on. It also stays visible when the person still has automations from before the policy was turned off, so they can always pause or delete them.
The page header says "Tasks (the agent's name) does for you on a schedule" and shows how many are active out of the maximum. For Rina it reads Tasks Atlas does for you on a schedule. 1 of 10 active. Below it, a hint explains that new automations are added by asking the agent in a conversation, with an example request.
If the policy is off, a warning says the automations will not run until it is turned back on. Pausing and deleting still work.
The list
The Automations tab shows each automation as a card:
| Field | Shows |
|---|---|
| Name and status | Active, Paused, Turned off, Stopped or Finished, with the reason underneath when there is one. |
| Schedule | For example "Every weekday (Monday to Friday) at 07:30 (Asia/Jakarta)". |
| Condition | When there is one. |
| Task | What the agent does. |
| Action | New conversation, WhatsApp message and/or Email, with the number or address it goes to. |
| Next run / Last run | When it runs next, and how the last run ended. |
Rina's card is Active. Its condition is the plain-language version of the two rules Atlas showed in the automation preview, and Last run says Not yet because the first scheduled run is Monday, 5 Oct 2026 at 07:30.
New automations are not created here. The page tells the user to ask the agent in a conversation instead.
Recent runs
If View history is allowed on the policy, a second tab, Recent runs, lists the latest runs of all the user's automations. Each entry shows the automation's name, when it ran and how (for example Run now), the status, whether the condition was met, and what each action did. A run that created a conversation has a View result link to it.
View result opens the conversation the run created. For Rina, KG-2041 was delayed, so the condition was met and Atlas wrote the summary:
Controls on each automation
Seven buttons, each available or greyed out depending on the automation's status and your policy switches. A greyed-out button explains why when hovered. On Rina's active automation, Resume is greyed out because there is nothing to resume.
| Button | What it does | Available when |
|---|---|---|
| View | Shows the full definition. | Always. |
| Edit | Opens the edit form. | Editing is allowed; the automation is not turned off by a contributor or finished; automations are on. |
| Pause | Stops it until resumed. | Pausing is allowed; the automation is active. |
| Resume | Starts it again. | Pausing is allowed; it is paused or stopped, not turned off by a contributor. Policy and access are checked again. |
| Run now | Runs it once, immediately. | Run now is allowed; the automation is active or paused. |
| History | Lists its runs. | View history is allowed. |
| Delete | Removes it, after a confirmation. | Deleting is allowed. Otherwise the user can only pause it. |
Run now uses the same queue as scheduled runs, so during a busy moment it can wait behind others.
Editing an automation
The edit form covers everything except adding a brand-new kind of check:
| Section | What can be changed |
|---|---|
| Name, Task | Free text (80 and 4000 characters at most). |
| Repeats | Once, every few minutes or hours, daily, weekly or monthly, with the date and time, interval, days of the week, day of the month or times of day, and the time zone. |
| Condition | Reword, change the value, comparison and meaning of each rule, or remove the condition. To check something new, ask the agent. |
| What to do with the result | Choose the actions, the WhatsApp number and the Email address. Actions the policy does not allow cannot be newly added. |
| If a run is missed | The missed-run policy. |
For example, Rina could move the check to 07:00, or remove the condition so the summary comes every weekday whatever the status. To check something different, such as open safety incidents at the Surabaya site, she asks Atlas for a new automation instead.
Saving re-checks the policy, for example the minimum interval or the limit of 10 emails an hour to one address, and shows the reason if the change is refused.
Notifications
The bell in the top bar of the chat tells the user what automations have produced. It shows a badge with the number of unread items and, when opened, the latest 20. After Rina's Run now, the bell showed a badge for the new result.
| Kind | When |
|---|---|
| Result | An automation created a new conversation. |
| Alert | An automation was stopped or paused: after repeated failures, because the policy changed, or because the agent moved to another organization. |
| Warning | An automation could not check its condition three times in a row. |
Opening a notification marks it read and takes the user to the conversation, or to the Automations page when there is no conversation. Mark all read clears the badge. The badge refreshes about once a minute and whenever the browser tab comes back into focus. Notifications are kept for 30 days.
Results and alerts are gathered per agent, so the bell only counts the current agent's automations.
What users cannot do
| They cannot | Because |
|---|---|
| Resume or edit an automation a contributor turned off | It is under governance. They can still delete it. |
| See other people's automations | Each automation belongs to the person who created it. Governance is done in the CMS, by you. |
| Get around the policy | The policy is checked at creation, at every edit, and at every run. |
Check the result
- Signed in to the agent's public chat, open ☰ → Automations. The KG-2041 card shows Active, the weekday 07:30 schedule, and the next run.
- Click Run now. Open Recent runs: a new entry shows Succeeded, and either Condition met with New conversation: sent, or Condition not met if the project is on track. Both are correct results.
- If the condition was met, click View result. The new conversation holds Atlas's summary of KG-2041, and the bell shows a badge for it.
- Click History on the card to see the same runs for this automation only.
Next steps
- Next in the journey: Monitor and Govern, your own view of every automation on this agent in the CMS.
- Troubleshooting Runs: help a user who asks why something did not run.