---
title: "Schedules"
description: "Configure recurring Cloud Agent runs on a cron schedule."
diataxis: how-to
applies_to:
  product: "nirmata-ai-agents"
audience: ["platform-engineer"]
last_updated: 2026-04-16
url: https://docs.nirmata.io/docs/control-hub/agent-hub/cloud-agents/schedules/
---


Schedules let you run any Cloud Agent automatically on a recurring basis. Navigate to **Agent Hub → Cloud Agents → Schedules** to manage them.

## Creating a Schedule

1. Click **New Schedule** (or click **Schedule** on an agent from the [Agent Catalog](../agent-catalog/)).
2. Configure the schedule:
   - **Agent** — select the agent to run.
   - **Target cluster** — the cluster to run the agent against.
   - **Inputs** — the same agent-specific parameters as a [manual launch](../agent-launch/).
   - **Interval** — choose from: Hourly, Every 12 hours, Daily, Weekly, or enter a **custom cron expression**.
   - **Timezone** — the timezone used to interpret the schedule interval.
   - **Enabled** — toggle on to activate immediately, or leave off to save it inactive.
3. Optionally configure **Notifications** (see below).
4. Click **Save**.

## Managing Schedules

From the Schedules list you can:

- **Filter** schedules by agent name, target cluster, or status (active / inactive).
- **Enable or disable** a schedule without deleting it.
- **Edit** an existing schedule to change its interval, inputs, or notification settings.
- **Delete** a schedule you no longer need.
- **View run history** — see all past runs triggered by a specific schedule, with their status and reports.

## Notifications

For each schedule you can configure notifications sent when a scheduled run completes:

| Channel | Setup |
|---------|-------|
| **Email** | Enter one or more recipient addresses. A summary is sent on run completion. |
| **Slack** | Select a Slack channel. Requires a Slack workspace integration configured under **Settings → Integrations**. |

Notifications are sent regardless of whether the run succeeded or failed.

## Cron Expression Reference

For custom intervals, use standard cron syntax (5 fields: minute, hour, day-of-month, month, day-of-week):

```bash