Docs contents

Scheduling

AgentOS can run your hosted agents on a schedule, with no cron infrastructure of your own.

Setting up a schedule

  1. Open an agent in the dashboard
  2. Go to the Schedule tab and turn on Enable scheduling
  3. Choose Hourly, Daily, Weekly and a day of the week, Monthly and a day of the month (1 to 28), or On chosen dates and a list of dates
  4. For daily, weekly and monthly, pick the time and the time zone it should run in. An hourly schedule runs on the hour
  5. Save. AgentOS invokes the agent at each scheduled time

The schedule dispatcher runs hourly, so a run starts within the hour of its scheduled time. An hourly schedule runs 24 times a day: for an agent, that is 24 runs of model spend. Scheduled runs appear in the runs list with the trigger Scheduled.

Every schedule is listed on the Schedules page with its cadence, the time until the next run, when it last ran and whether that run succeeded. Pause a schedule there with its switch; the agent itself stays active.

On chosen dates

A schedule can run on dates you choose instead of a recurring cadence: add each date with its hour, and pick the time zone they are read in. An agent or a script has one schedule, recurring or on chosen dates, not both.

  • It runs once at each date, on the hour. A list holds up to 366 dates, no two alike.
  • A date already past does nothing, and saving the list never runs one. The preview shows the dates still to come.
  • After the last date the schedule stays on with no next run, and reads Finished. Add a later date to bring it back.
  • Dates missed while a run could not start are not replayed one by one. Several missed in a row start one late run, and a date skipped because the previous run was still going, or the agent was paused, is passed over. An agent or script on chosen dates should therefore do everything due up to now on each run, not only the date it was started for.
  • On the night the clocks go forward, an hour that does not exist runs at the next hour that does. On the night they go back, an hour that comes twice runs the first time.

Over the API it is frequency: "calendar" with run_dates:

{
  "frequency": "calendar",
  "timezone": "Europe/Lisbon",
  "run_dates": [
    { "date": "2026-11-03", "hour": 9 },
    { "date": "2026-11-17", "hour": 14 }
  ]
}

Run instructions

Set optional Run instructions on the Schedule tab: a JSON object passed as the run input on every scheduled run. Use it for runtime parameters.

{
  "report_type": "daily_summary",
  "notify_slack": true
}

Triggering a run manually

You can trigger any agent run from the dashboard (the agent's Run button) or via the API:

curl -X POST https://agentos-ai.dev/api/v1/agents/<agentId>/invoke \
  -H "Authorization: Bearer aos_agent_..." \
  -H "Content-Type: application/json" \
  -d '{ "input": { "report_type": "on_demand" } }'

Monitoring scheduled runs

Runs → Live streams events from all running agents, and the Overview shows run counts and success rates by agent.

To hear about problems, add alert rules: Any run fails for a failed scheduled run, and Agent has no activity for a scheduled agent that should have run by now and did not.