> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glood.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedules and triggers

> When an agent wakes, on a clock or when something happens, and what it does then

A schedule, which the dashboard calls a **check**, is one standing job: when the
agent wakes, and what it should do when it does. An agent with no checks only
works when you ask it, in [chat](https://docs.glood.ai/platform/agents/chat.md) or with
[Run now](https://docs.glood.ai/platform/agents/deploy.md#deployment-actions).

Checks belong to the agent, so every deployment of it runs the same checks, each
in its own store's time zone. Switching a check off stops it on every store; to
stop an agent on one store only, [pause that deployment](https://docs.glood.ai/platform/agents/deploy.md#deployment-actions).

Open the agent, then **Configuration → Schedules**. The section header counts
the checks that are on and off. Changing them needs `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.

| Cadence | When it runs |
| - | - |
| **Every hour** | On the hour, every hour |
| **Every 4 hours** | Six times a day |
| **Daily at 08:00** | Once each morning. The default |
| **Weekly on Monday** | Once a week, Monday morning |
| **Custom** | A cron expression you write |

**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:

| Template | Check | Wakes when |
| - | - | - |
| **Store monitor** | When an anomaly is detected | One of the hourly checks opens an insight on the store. The agent traces the insights named in its first message |
| **Fraud agent** | Each new COD order | A new order arrives unpaid or partly paid, which is how a cash-on-delivery order looks at checkout |
| **Fraud agent** | Each new prepaid order | A new order arrives paid or authorized |
| **Fraud agent** | Each return request | A return is requested |
| **Fraud agent** | Daily store-level fraud checks | Not an event: every day at 07:00, store time, it reviews discount codes and couriers |

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](https://docs.glood.ai/platform/using.md) or the agent itself in
[chat](https://docs.glood.ai/platform/agents/chat.md), for example *"Add a check that runs on each new
order"*. Events arriving within the same minute share one run.

> [!NOTE]
>
> 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](https://docs.glood.ai/platform/dashboard/insights.md#insights-and-agents).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.