Skip to main content
By the end of this guide an agent runs in your repository every weekday at 9am, without you starting it, and you can see each firing and open the run it started. A schedule is a trigger. You can create one from the terminal, or declare it in a workflow’s YAML so anyone who uses the workflow can turn it on. This guide does both. Schedules lists every option.

Before you begin

1

Create a schedule trigger

Run this from the repository. --project defaults to the working directory. Always pass --workflow: builtin://agent is the stock agent.
terminal
This output came from a test trigger that fired a few minutes later. --overlap skip (the default) records a skipped firing instead of starting a second run on top of one still going. --catchup-window limits how late a firing missed during an outage may still run.
2

Or declare the schedule in a workflow

A triggers: block keeps the schedule beside the workflow it runs. Declaring it fires nothing.
.reliant/workflows/repo-summary.yaml
mode: plan gives the agent read-only tools. Check the file with reliant workflow validate and reliant workflow lint, then commit it. Lint warns [no-failure-path] until the workflow has an on_failure: step that tells someone. Then turn the schedule on, which is the app’s Enable dialog as a command:
terminal
The activation re-reads the triggers: block on every firing, so a cron edit you commit takes effect without activating again.
3

Verify it fires

trigger list shows the next and last firing. trigger events lists firings with the run each one started:
terminal
launched with a chat ID means the run started. DEFINITION records the exact commit of the workflow it ran. Follow the run with reliant workflow follow <chat-id>; it is also under Workflows → Runs in the app. To test without waiting for 9am, reliant trigger fire <name> runs it now.
4

Pause or remove it

terminal
Deleting keeps the firing history and the runs it started.

What this does not do

  • Nobody answers the agent. Scheduled runs are unattended, so the agent is told to decide and proceed. A run that waits for an approval, or one that fails, shows up in your Inbox.
  • In an organization with two or more members, runs spend only the organization’s AI accounts by default (Unattended funding: org_only), never your own subscriptions. If no organization account can run the model, the firing fails. An admin fixes that in Settings → Organization → AI accounts. The CLI can only tighten funding, never widen it.
  • A machine that is off cannot run it. A suspended cloud machine is woken for the run. A laptop or server you run yourself must be online. Firings missed for longer than the catch-up window are dropped, not replayed.
  • Turning a schedule on is yours to do. An agent can write the triggers: block. When an agent asks to enable an automation, you get an approval card by default (Automation approvals).

Troubleshooting

The firing launched, or tried to, but no organization account could run the model. reliant trigger get <name> shows Health: degraded with the same text. After two such failures in a row the trigger pauses itself (State: paused, Health: failing); run reliant trigger enable <name> once an account can run it. An admin can add an organization API key or turn on Reliant credits, or you can change the automation’s model. A paused run continues by itself once an organization account can run it. reliant workflow status shows only call_llm FAIL. reliant workflow follow <chat-id> prints the full error.
Check Workflow: in reliant trigger get <name>. A trigger created without --workflow shows Workflow: -. In reliant v1.21.3 its firings record nothing. Set a workflow with reliant trigger update <name> --workflow builtin://agent plus the trigger’s other flags: update replaces the whole definition.

Next steps

Schedules reference

Every schedule field, intervals, overlap and catch-up after an outage.

First multi-agent workflow

Write the workflow a schedule runs: planner, implementer and reviewer.

Daily Slack digest

Post a scheduled agent’s summary to a Slack channel.

No-machine runs

Schedule an agent that needs only the web and your integrations.