cron - floo

floo cron lists, shows, and manually triggers scheduled cron jobs. Cron jobs are declared in floo.app.toml under [cron.<name>] sections, not created with the CLI. Every deploy reconciles the declared set: new sections become jobs, removed sections are deleted, changed sections are updated.

To add a cron job, edit floo.app.toml. See Cron Jobs for the schema and end-to-end flow, or Config Spec → [cron.<name>] for the field reference.

list

Every cron job declared on an app, with its enabled state, last status, and last run time.

floo cron list --app my-app
floo cron list --app my-app --json

Flags

Flag	Description	Default
`--app APP`	App name or UUID	inferred from config

JSON output

{
  "success": true,
  "data": {
    "cron_jobs": [
      {
        "id": "c5a1c4d8-3a36-4d4f-9d4f-3c2a1f9bb2d7",
        "name": "daily-report",
        "schedule": "0 9 * * *",
        "command": "python -m reports.daily",
        "service_name": "api",
        "timeout": 300,
        "enabled": true,
        "last_run_at": "2026-04-30T09:00:14Z",
        "last_status": "success",
        "created_at": "2026-04-12T18:00:00Z"
      }
    ]
  }
}

last_run_at and last_status are null until the first run completes. last_status is success, failed, or interrupted. The API writes it only after the run reaches a terminal state, so there is no “running” value.

show

One cron job by name.

floo cron show daily-report --app my-app
floo cron show --name daily-report --app my-app

Arguments

Argument	Description
`<name>`	Cron job name; must match a `[cron.<name>]` section in `floo.app.toml`. Pass it positionally or as `--name`, not both

Flags

Flag	Description	Default
`--app APP`	App name or UUID	inferred from config
`--name NAME`	Cron job name, as an alternative to the positional argument	none

JSON output

{
  "success": true,
  "data": {
    "id": "c5a1c4d8-3a36-4d4f-9d4f-3c2a1f9bb2d7",
    "name": "daily-report",
    "schedule": "0 9 * * *",
    "command": "python -m reports.daily",
    "service_name": "api",
    "timeout": 300,
    "enabled": true,
    "last_run_at": "2026-04-30T09:00:14Z",
    "last_status": "success",
    "created_at": "2026-04-12T18:00:00Z"
  }
}

Errors

Code	Meaning
`CRON_JOB_NOT_FOUND`	No cron job with that name on this app. Run `floo cron list` to see available jobs.

run

Trigger a cron job now, for testing or a one-off catch-up run.

floo cron run daily-report --app my-app
floo cron run --name daily-report --app my-app
floo cron run daily-report --app my-app --preflight # preview, no API call

Arguments

Argument	Description
`<name>`	Cron job name; must match a `[cron.<name>]` section in `floo.app.toml`. Pass it positionally or as `--name`, not both

Flags

Flag	Description	Default
`--app APP`	App name or UUID	inferred from config
`--name NAME`	Cron job name, as an alternative to the positional argument	none
`--preflight`	Preview the trigger without calling the API	off

What it does

Resolves the app from --app or the nearest floo.app.toml.
Calls the platform’s “trigger cron job” endpoint once, which dispatches a one-off job execution against the service’s container image.
Prints the API’s response. The CLI makes one request and does not poll; the API holds that request open while the job runs, writes last_run_at and last_status when it reaches a terminal state, and then responds. A failed run returns an error. triggered: false means no new execution started, because the job was already running or that occurrence was superseded; message says which. Read the run’s output with floo logs query --cron <name>.

JSON output

{
  "success": true,
  "data": {
    "name": "daily-report",
    "triggered": true,
    "message": "Cron job completed."
  }
}

What the CLI does NOT do

Add jobs. Edit floo.app.toml. The next deploy creates the job.
Remove jobs. Delete the [cron.<name>] section from floo.app.toml. The next deploy deletes the job.
Edit schedules or commands. Change them in floo.app.toml. The next deploy updates the job.

Schedules are stateless reconcilable resources. Keeping them in config makes the repo the source of truth, and every change ships through the same review and deploy flow as code.

Cron Jobs guide: walkthrough with examples, schedule syntax, and the agent workflow
Config Spec → [cron.<name>]: full field reference
floo deploys watch: watch a deploy reconcile cron jobs in real time

​list

​Flags

​JSON output

​show

​Arguments

​Flags

​JSON output

​Errors

​run

​Arguments

​Flags

​What it does

​JSON output

​What the CLI does NOT do

​Related

list

Flags

JSON output

show

Arguments

Flags

JSON output

Errors

run

Arguments

Flags

What it does

JSON output

What the CLI does NOT do

Related