runcrate schedule starts an instance or a job for you later: once with --at, or repeating with --cron. Runs start within about 2 minutes of their time. See Schedules for how runs, skips and notifications work.
Create a schedule
-- makes it a job schedule, joined and quoted the same way as runcrate run. Without a command it is an instance schedule, and --name is required.
The command is visible to everyone in the workspace, so pass tokens with --env (or keep them in your environment’s secrets), never inside the command.
create prints the schedule id and its next run.
When it runs
Use exactly one of
--at and --cron. A time skipped by a daylight saving change moves forward by the gap (02:30 runs at 03:30); a time that happens twice runs once, the first time.
What it starts
List schedules
--json works on every schedule command.
Inspect a schedule
Pause, resume and run now
run-now does not move the next run. A one-off resumes only if its time is still in the future.