Notifications
Every agent and every report has a Notify list: the workspace members and channels that hear about it when something needs a person. People on the list get an email; channels on the list get a short message. Each carries a short reason and a link into Discontinue.
The Notify list
- On an agent: under Who gets alerts about this agent in the Agent tab. Edit opens the Alerts panel, where you add or remove entries and pick what each one hears; every change saves at once.
- On a report: under Who gets alerts about this report at the top of the Schedules tab (changed the same way, in the Alerts panel), apart from each schedule's destinations (the rows under the schedule, added with Add destination). The destinations are where the report itself goes; the Notify list hears when something goes wrong.
A new agent or report starts with its creator on the list. Anyone in the workspace can add or remove members and channels. The list is not part of an agent's versions: a change applies at once and needs no approval.
Each entry chooses what it hears, on its row: on an agent Approvals, Failures and Every run; on a report Failed runs and Failed deliveries. A new entry hears everything except Every run, and every entry hears at least one event.
Only the list is notified. There is no fallback to admins: if nobody on the list hears an event, nobody is told; an empty list shows Nobody gets notified. A member who leaves the workspace and a deleted channel leave every list.
Any channel type can be on a list except FTP/SFTP, which receives files, not messages.
What is notified
| Event | Who hears | What it says |
|---|---|---|
| Approval needed | The agent's list | Which agent is waiting, what it asks for, and when the request expires (it is treated as denied if nobody decides by then) |
| Agent run failed | The agent's list | The agent, when, and what went wrong. A run that failed, ran out of its step or time budget, or was stopped or refused by a spend limit, the subscription, or an app not yet authorized for the agent counts, and so does a run that ended with the agent saying it could not do what was asked (its own words are the message); a run you stopped does not. Runs started from chat are not notified |
| Email not answered | Entries of the agent's list that hear Failures | The agent, who wrote, the email's subject, when, and why the answer could not be sent (for example the monthly delivery limit is used up, or the address was rejected). Once per run, even when failures are muted, and in addition to that run's failure or finished message |
| Agent run finished | Entries of the agent's list that chose Every run | The agent, how the run ended (completed, with warnings, failed, or cancelled), its summary, what started it, and when. Every run counts, including one you stopped; runs started from chat do not |
| Scheduled report failed | The report's list | The report and schedule, when, and the first line of the error. Runs you start by hand, runs an agent starts, and runs held back by the monthly report limit or the subscription are not notified |
| Report delivery failed | The report's list | The report, the destination it did not reach, when, and the error, including a delivery refused because the monthly delivery limit is used up. A muted destination is not a failure |
Approvals are decided in Discontinue only; the messages carry a link, never buttons. See Agents for who may decide what.
Problems with a connection itself, such as an expired login that needs reconnecting, are reported to admins under Connectors, not to Notify lists.
No repeats
A failure notifies the first time it happens after a success. If the same thing keeps failing, the list is not told again until it has worked once in between. Each destination of a report counts on its own, so one broken destination never mutes another. An approval request and a finished run are always notified. Each entry gets one message about how a run ended: an entry that hears both Failures and Every run gets the failure message for a failed run, and the finished message only when no failure message reached it.
To stop notifications, remove the entries or the events they hear.
Email and channel messages
- Email to people comes from Discontinue in your workspace's branding, with a button to the request, run, or report.
- Channels get the short message their type supports: a Slack or Telegram message, an email to the channel's addresses, a Teams card, or the JSON message with
kindset tonotificationfor a webhook. See Channels.