Skip to main content
A scheduled command runs an existing site command on a cron. Use it for a direct, repeatable task such as validation or a repository script. Give an agent a routine instead when the work needs tools or judgment.

​
Create a schedule

Cron uses standard five-field syntax. Fimo runs the command from the site root in the selected Branch. The current checkout selects the Branch by default, or you can pass --branch <name>. The schedule policy shown by list and show is the source of truth for the current cadence and availability.

​
Select site secrets

Schedules receive no site secrets unless you select them. Repeat --secret for the keys the command needs:

​
Manage schedules

Pausing stops future cron runs and keeps the schedule history. Fimo suspends a schedule after three consecutive failed runs on the same Branch, regardless of the error. This includes failures while preparing the run, missing secrets, command errors, and timeouts. A successful run resets the streak. Skipped ticks do not count either way. A suspended schedule keeps its active-schedule slot but does not start more runs. Review the latest failure, fix the cause, then use Resume in Studio or fimo schedules resume <name>. Resume gives the schedule a fresh retry streak. Editing an unsuspended schedule also starts a fresh streak. A new deployment does not resume a suspended schedule.

​
Run and inspect

run waits for completion by default. Add --no-wait to return after Fimo queues it. Only one run for a schedule can be active at a time. Each run can last up to the Max run time shown in the schedule policy. If the command is still running at that limit, Fimo stops it, keeps the output it produced so far, and marks the run failed with the error code deadline_exceeded.
A scheduled command may run more than once. Make commands with external side effects safe to retry.

​
What’s next

Automate your site

Choose the right automation tool.

Agents

Give work that needs judgment to an agent.

Branches

Keep scheduled work isolated.