Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/jonwiggins/optio/llms.txt

Use this file to discover all available pages before exploring further.

Scheduled tasks let you run agent tasks automatically at set times — no manual intervention needed. Common uses include nightly test runs, weekly dependency updates, and daily code health checks. Schedules are managed at /schedules in the UI.

​
Creating a schedule

1

Open the Schedules page

Navigate to /schedules and click New schedule.
2

Fill in the task details

Configure what the agent will do each time the schedule fires:
  • Title — a short label for the task that will be created on each run.
  • Prompt — the full instruction sent to the agent.
  • Repository — the repository the agent will work in.
  • Branch (optional) — defaults to the repository’s default branch.
  • Agent type — claude-code or codex.
3

Set the cron expression

Enter a standard 5-field cron expression. The UI validates the expression and shows a human-readable description before you save.See common examples below.
4

Save and enable

Click Create schedule. The schedule is enabled by default. Optio will fire the first run at the next matching time.

​
Managing schedules

From the /schedules page you can:
  • Enable / disable a schedule with the toggle. Disabled schedules are not fired but are preserved with their configuration.
  • Edit the name, cron expression, prompt, or any other field at any time.
  • Manually trigger a schedule immediately using the Run now button — useful for testing.
  • Delete a schedule. This does not delete tasks that were already created by it.

​
Run history

Each schedule has a run history tab showing the last 50 runs. Each entry shows:
  • Triggered at — timestamp when the schedule fired.
  • Status — triggered, completed, or failed.
  • Task — a link to the task that was created, so you can open its logs and result.
  • Error — if the trigger failed before creating a task, the error message is shown here.

​
Common cron expressions

0 0 * * *
Fires at 00:00 UTC every day. Good for nightly test suites or cleanup tasks.
0 9 * * 1-5
Fires at 09:00 UTC Monday through Friday. Good for daily code health checks.
0 8 * * 1
Fires at 08:00 UTC every Monday. Good for weekly dependency updates.
0 * * * *
Fires at the top of every hour.
*/15 * * * *
Fires every 15 minutes. Use sparingly — each run creates a task and consumes agent credits.
0 9 1 * *
Fires at 09:00 UTC on the 1st of each month. Good for monthly dependency audits or reports.
All cron expressions are interpreted as UTC. The schedule worker checks for due schedules at regular intervals, so there may be a small delay (typically under a minute) between the scheduled time and when the task is actually created.
Scheduled tasks respect per-repository concurrency limits (maxConcurrentTasks). If the repository is already at capacity when a schedule fires, the new task will be queued and will start as soon as a slot is available — it is not dropped. For time-sensitive schedules, ensure your concurrency limits are set high enough or stagger your schedules to avoid queuing.

Build docs developers (and LLMs) love

Get started for freeTalk to us