sincecutoff.com
← all changes

railway cron list and run commands

Introduced 2026-10-12 · score 0.96

HOW TO USE IT

If the linked Railway service has a cron schedule, use `railway cron list` to view recent runs or `railway cron run --yes` to enqueue an off-schedule run.

railway cron list
railway cron list --service <SERVICE> --environment <ENV> --limit 50
railway cron run --service <SERVICE> --yes

WHY THIS HELPS

List or run cron jobs while working with a Railway project.

REQUIREMENTS AND LIMITATIONS

  • Version: v5.65.0
  • list: Subcommand to list recent runs, newest first; targets the linked service by default.
  • run: Subcommand to trigger an off-schedule run now; targets the linked service by default.
  • -s, --service <SERVICE>: Service name or ID; defaults to the linked service.
  • -e, --environment <ENV>: Environment; defaults to the linked environment.
  • -p, --project <PROJECT>: Project ID or name; defaults to the linked project.
  • --limit <N>: For `list`, maximum runs to show; default 20, maximum 1000.
  • --json: Output in JSON format.
  • -y, --yes: For `run`, skip confirmation; required when stdout is not a terminal.
  • Prerequisite: Authenticate with a Railway account before using the CLI; the CLI docs specify `railway login` or a token for CI/CD.
  • Prerequisite: The target service must have a cron schedule configured in service settings or in a config file's `deploy` section; otherwise the command errors.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card