agent:write.
Add a check
1
Add check
Choose Add check, or Add the first check on an agent with none.
2
Name
What this check is called, for example Morning summary. Renaming it later
is safe: past runs stay attached to it.
3
What it should do
The task for this run, read by the agent when the check fires, for example
“One paragraph on yesterday: what moved, what did not, and what I should
look at.” The run keeps a copy, so editing this later never rewrites
history.
4
When
Pick a cadence. Times are in each store’s own time zone.
Custom takes a five-field cron expression, read in each store’s own time
zone, and shows it back in words so you can check it before saving. For example
0 */6 * * * runs every six hours. The fastest an agent may run is hourly:
the minute field must be a single number, so */15 * * * * is refused.
Run times are approximate. Each store’s runs are spread over a few minutes, so a
check set for 08:00 may start a little after.
Switch a check on or off
Each check has its own switch. Off keeps the check and its history, and shows Off on its row. Edit changes its name, what it does, or when it runs. A deployment’s Schedules tab shows when each check next fires on that store and how the last run there went.Event triggers
Some checks wake the agent when something happens rather than on a clock. Their row reads When … arrives, naming the event. The templates bring the event triggers they need:
In the dashboard you can rename an event check, change what it does, and switch
it on or off. Its trigger cannot be changed here yet, and a new check you add
here always runs on a cadence.
To add an event trigger to another agent, ask your
AI assistant or the agent itself in
chat, for example “Add a check that runs on each new
order”. Events arriving within the same minute share one run.
The Store monitor’s When an anomaly is detected check is also what makes its
finding your one alert for an incident. Switch it off and you are alerted about
the insight itself instead. See Insights and agents.