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

# Scheduled tasks

> Run an automation on a repeating schedule.

A scheduled task runs your automation on a clock you set. Every morning at nine.
Every Monday. Every fifteen minutes.

## Ask for it

Say when you want it to run. Use normal words. The agent works out the rest.

> Run this every weekday morning at 8am Eastern.

> Check the site every 15 minutes and text me if it goes down.

> Send me the weekly summary on Friday afternoons.

Two things make a big difference here.

**Name your timezone.** "9am" means nothing on its own, and the agent defaults to
UTC when you leave it out. Say "9am Pacific" and you get 9am Pacific all year,
including after the clocks change.

**Say how often, not how it works.** You do not need to know any schedule syntax.
Describe the rhythm you want and let the agent translate it.

## What the agent sets up

The agent registers your schedule with the platform, not inside your workspace.
This matters, because your workspace sleeps when it is idle. A timer running
inside a sleeping machine would never fire.

When your schedule ticks, the platform wakes the workspace and runs the handler.
Then the agent adds the schedule to your automation's entry in the Automations
tab, with a label you can read, like "Every morning at 9".

## Test it before you trust it

Do not wait a whole day to find out whether your nightly job works.

Ask the agent to add a manual trigger too, then press the button and watch the
run. Both paths run the same code, so a passing manual run tells you the
scheduled run will work.

> Add a button so I can run this now instead of waiting until tomorrow.

## Worth knowing

* **Runs can land late.** The platform wakes your workspace first, so a 9:00 job
  might start at 9:00:30. Plan for a minute of slack.
* **Slow runs do not stack.** If your job is still going when the next tick
  arrives, the platform skips that tick instead of starting a second copy.
* **A broken job turns itself off.** After 10 failures in a row, the platform
  disables the schedule so it stops waking your machine for nothing. Tell the
  agent to fix it and turn it back on.
* **Delete what you stopped using.** Every tick wakes the machine and costs you
  compute. Ask the agent to remove schedules you no longer want.

## Change it later

Just say so in the chat. You do not edit anything by hand.

> Move the digest to 7am instead of 9am.

> Make this weekly instead of daily.

> Stop running the inventory sync.