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

# Scheduled Tasks

> Run any Gradial task automatically on a recurring schedule — set it once and Grady executes autonomously at every interval, with full lifecycle management and run history.

Scheduled Tasks let you put any existing Gradial task on a recurring cadence. Set the schedule once and Grady runs the task autonomously at each interval — no manual triggering required. Monitor every run from the Scheduled Tasks dashboard and stay in control with pause, resume, and run-now controls.

<Info>
  Scheduled Tasks must be enabled for your organization. Contact your Gradial team to get access. Requires Agent V3.
</Info>

***

## What Scheduled Tasks Enable

<CardGroup cols={2}>
  <Card title="Recurring execution on any task" icon="rotate">
    Schedule any existing task with a cron expression and timezone. Grady clones and runs it autonomously on each fire.
  </Card>

  <Card title="Scheduled Tasks dashboard" icon="table-columns">
    An org-level view of all active schedules with status badges (Active, Paused, Failed), next run time, last modified, and created by.
  </Card>

  <Card title="Run history and provenance" icon="clock-rotate-left">
    Every scheduled run links back to the parent schedule. A "Scheduled" badge on cloned task threads makes the origin clear at a glance.
  </Card>

  <Card title="Auto-pause on repeated failure" icon="circle-pause">
    After 5 consecutive failed runs, the schedule pauses automatically to prevent runaway execution. The failed state is visible in the dashboard.
  </Card>

  <Card title="Full lifecycle control" icon="sliders">
    Pause, resume, edit the task template or cadence, trigger an immediate run, and delete schedules with the option to keep or remove run history.
  </Card>

  <Card title="Flexible delete modes" icon="trash">
    "Delete Schedule" keeps completed run threads for reference. "Delete Schedule and Runs" also removes the associated cloned task threads.
  </Card>
</CardGroup>

***

## How It Works

<Steps>
  <Step title="Open the Scheduled Tasks page">
    Navigate to **Scheduled Tasks** in the left sidebar. This page lists all schedules your organization has set up, with their current status and next run time.
  </Step>

  <Step title="Create a new schedule">
    Select an existing task to use as the template. Set the cadence (daily, weekly, monthly, or a custom cron expression) and choose the timezone. Use **Run Now** to trigger an immediate run before the recurring schedule starts.
  </Step>

  <Step title="Grady executes each run autonomously">
    At each scheduled interval, Grady clones the template task and runs it end-to-end. The cloned thread appears in your task history with a "Scheduled" badge linking back to the parent schedule.
  </Step>

  <Step title="Monitor from the dashboard">
    The Scheduled Tasks page shows real-time status for every schedule. Open the run history drawer on any schedule to see each past run, its outcome (Success / Failed), and a link to the cloned task thread.
  </Step>

  <Step title="Manage the schedule lifecycle">
    Pause a schedule when you need to hold runs, resume it when ready, or edit the template and cadence at any time. If a schedule auto-pauses after 5 consecutive failures, investigate from the run history and resume once resolved.
  </Step>
</Steps>

***

## What makes a good scheduled task

Any existing task can be scheduled, but the cadence pays off most for work that is **recurring, predictable, and worth doing on a fixed rhythm** — where the value is in it happening reliably without someone remembering to trigger it. Good candidates tend to be:

* **Time-based by nature** — weekly refreshes, monthly audits, nightly batch jobs.
* **Repeatable with the same instructions** — the prompt doesn't need to change run to run.
* **Better caught early** — monitoring and compliance checks where a regular cadence surfaces drift before it becomes a problem.

Because each run starts from a task template, the prompt you schedule looks like any other Gradial prompt. See the [Prompt Library](/docs/gradial-prompt-library/prompt-library) for ready-to-use prompts that work well on a recurring schedule.

## Common Use Cases

**Weekly content refreshes.** Schedule a social media or blog refresh task to run every Monday morning. Grady executes autonomously and the team reviews results in the run history.

**Monthly audits.** Set a brand audit or compliance check to fire on the first of each month — no one needs to remember to kick it off.

**Nightly localization.** Run overnight localization tasks across markets while the team is offline. Scheduled runs execute and surface results in thread history for review the next morning.

***

## Permissions

| Action                         | Required permission                                          |
| ------------------------------ | ------------------------------------------------------------ |
| Create, edit, resume, run now  | `Org.MANAGE_SETTINGS`                                        |
| View schedules and run history | `Org.VIEW`                                                   |
| Pause, delete                  | Available without the feature flag (for wind-down scenarios) |

***

## Limitations

* **One schedule per task template** in this release — multiple cadences on the same template are not yet supported.
* **No attachment replacement on edit** — if a scheduled task template includes file attachments, editing the template message does not replace the attached files.
* **Human-in-the-loop tools stay active** in scheduled runs. A run that calls a HITL tool will stall its workflow.
* **No live next-fire-time preview** when editing the cron expression — the updated next-run estimate does not recalculate in real time after a cadence change.

***

## Getting Started

1. **Contact your Gradial team** to enable Scheduled Tasks for your organization.
2. **Navigate to Scheduled Tasks** in the left sidebar.
3. **Create a new schedule** — select an existing task template, set the cadence and timezone, and save.
4. **Monitor runs** from the Scheduled Tasks dashboard and run history drawer.