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

# Scheduling

> Run an agent automatically on a cadence — daily, weekly, monthly, or a custom schedule.

An agent can run on its own on a schedule. Set a cadence and the scheduler triggers background runs for you — no one has to be at the dashboard. Each scheduled run is recorded just like any other run, with its own output chat.

## Schedule modes

<ParamField path="manual" type="default">
  No schedule. The agent runs only when you start it interactively or through the API. This is the default.
</ParamField>

<ParamField path="daily" type="cadence">
  Runs once a day at a time you choose.
</ParamField>

<ParamField path="weekly" type="cadence">
  Runs once a week on the day and time you choose.
</ParamField>

<ParamField path="monthly" type="cadence">
  Runs on a monthly cadence — including **every N months** — at the time you choose.
</ParamField>

<ParamField path="custom" type="cron expression">
  Any standard cron expression, for full control over the cadence.
</ParamField>

You can **enable or disable** a schedule at any time without redeploying the agent, so pausing and resuming automated runs is instant.

<Tip>
  For a repeat like "every N days" or "every N weeks" (any interval other than every 1), use a **custom cron expression** that spells out the exact days you want. Cron gives you precise, predictable cadences for these patterns.
</Tip>

## Schedules run in UTC

All schedules run in **UTC**. Set your run time with UTC in mind.

<Warning>
  If your local time observes daylight saving, your agent's local run time will shift by an hour when the clocks change, because the schedule itself stays anchored to UTC. Choose a time that's acceptable year-round, or adjust the schedule seasonally when the clocks change.
</Warning>

## What a scheduled run needs

A couple of things need to be in place for scheduled runs to fire successfully. The dashboard shows whether scheduled runs are supported for your agent, so you can confirm at a glance.

<AccordionGroup>
  <Accordion title="Available credits" icon="coins">
    Scheduled runs consume credits like any other run. If the tenant is out of credits, the run is skipped and marked accordingly rather than failing silently — so your credit balance is always the single thing to top up.
  </Accordion>

  <Accordion title="A bound identity for connected apps" icon="user-check">
    If the agent uses [connected apps](/agents/configuring), it needs a bound identity so those apps can act on someone's behalf during an unattended run. Agents driven by an API key need a **bound subject** for this. Without one, scheduled runs can't use connected apps — the dashboard indicates whether scheduled runs are supported so you know before you rely on them.
  </Accordion>
</AccordionGroup>

## How scheduled runs are recorded

Each scheduled run is recorded as a **run** with its own output chat, so your automated work has the same history and reviewability as interactive runs. See [Running & run history](/agents/running).

<Note>
  Retries never double-run the same scheduled occurrence — a given occurrence produces exactly one run, so automated work stays clean and idempotent.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Review scheduled runs" icon="list-check" href="/agents/running">
    Open the chats your scheduled runs produce.
  </Card>

  <Card title="Configure connected apps" icon="plug" href="/agents/configuring">
    Set up the integrations a scheduled agent will use.
  </Card>
</CardGroup>