Cron jobs

Cron jobs run shell commands on a schedule, in UTC, inside a service’s container image. Declare them in floo.app.toml; every deploy syncs them.

Declare in config

Add [cron.<name>] sections to floo.app.toml:

[app]
name = "my-app"

[cron.daily-report]
schedule = "0 9 * * *"                  # 9am UTC daily
command = "python scripts/daily_report.py"
service = "web"                          # which service's image to run in

[cron.cleanup]
schedule = "*/5 * * * *"                 # every 5 minutes
command = "node scripts/cleanup.js"
service = "worker"
timeout = 600                            # max seconds, 1 to 1500 (default 300)

[services.web]
type = "web"
path = "."
port = 3000
ingress = "public"

[services.worker]
type = "worker"
path = "./worker"
ingress = "internal"

Fields

Field	Required	Description
`schedule`	yes	Standard cron expression (e.g. `"0 9 * * "` for 9am daily, `"/5 * * * *"` for every 5 minutes). `floo preflight` rejects an invalid expression. A Git push saves it anyway, and the job never runs until you fix it; the deploy log says so.
`command`	yes	Shell command to execute inside the container
`service`	yes	Name of the service whose image to run the command in. Must match a `[services.*]` entry
`timeout`	no	Max execution time in seconds, `1` to `1500` (default: 300)

Deploy and verify

Push to GitHub or run floo redeploy. Each deploy creates new jobs, updates changed ones, and deletes removed ones. Dev and prod each have their own copy of every job, and both run on schedule with their own environment’s env vars and managed services. A push syncs the dev jobs; a prod release syncs the prod jobs. floo cron list, show, and run default to dev; pass --env prod for prod.

git push origin main && floo deploys watch --app my-app

Then verify:

floo cron list --app my-app

Manually trigger a job

floo cron run daily-report --app my-app             # dev
floo cron run daily-report --app my-app --env prod

Common schedule expressions

Expression	Meaning
`* * * * *`	Every minute
`/5 * * *`	Every 5 minutes
`0 * * * *`	Every hour
`0 9 * * *`	Daily at 9am UTC
`0 9 * * 1-5`	Weekdays at 9am UTC
`0 0 * * 0`	Weekly on Sunday at midnight UTC
`0 0 1 * *`	Monthly on the 1st at midnight UTC

How it works

You declare [cron.<name>] in floo.app.toml
A deploy reads the [cron.*] sections from floo.app.toml in the deployed commit
floo creates, updates, or deletes cron job records to match the declarations
Jobs run inside the specified service’s container image with the same environment variables

A job sees the same DATABASE_URL, REDIS_URL, and other env vars as the service it runs in.

Failure handling

Cron jobs do not retry. Each scheduled run executes once; if the command exits non-zero or exceeds its timeout, that run is marked failed. The next scheduled run is the only recovery; there is no backoff. Where a miss matters, make the command idempotent, handle retries inside it, and alert on failure: floo logs query --app my-app --cron <job> --env prod shows the cron output with [cron:<job>] attribution, and agent webhooks can route repeated failures to your agent or on-call.

JSON output

# List cron jobs (JSON for parsing)
floo cron list --app my-app --json 2>/dev/null | jq '.data.cron_jobs'

# Trigger a job manually
floo cron run daily-report --app my-app --json 2>/dev/null

CLI reference

See the exact floo cron list and floo cron run flags, JSON shape, and --preflight behavior.

Get started

Build with your stack

Deploy from your agent

Configure your app

Ship and release

Data

Domains and networking

App users and access

Operate

Team and billing

For agents

Declare in config

Fields

Deploy and verify

Manually trigger a job

Common schedule expressions

How it works

Failure handling

JSON output

CLI reference

​Declare in config

​Fields

​Deploy and verify

​Manually trigger a job

​Common schedule expressions

​How it works

​Failure handling

​JSON output

CLI reference

Declare in config

Fields

Deploy and verify

Manually trigger a job

Common schedule expressions

How it works

Failure handling

JSON output