Skip to main content
PATCH
Update schedule

Authorizations

Authorization
string
header
required

Use a Runcrate API key with the rc_live_* prefix as the bearer token. Create one at https://www.runcrate.ai/dashboard/api-keys.

Path Parameters

id
string
required

Body

application/json

Send any of these. run_at turns the schedule into a one-off (clears cron); cron makes it repeating (clears run_at). spec replaces the whole spec, so send environment variable values again.

enabled
boolean

false pauses. true resumes and makes the schedule run as you from now on: a repeating schedule runs at its next occurrence from now; a one-off runs at its run_at, which must still be in the future.

run_at
string<date-time>
cron
string
timezone
string
overlap
enum<string>
Available options:
skip,
allow
name
string
Required string length: 1 - 63
spec
object

Response

Updated schedule.

data
object
required

Starts an instance or a job later: once at run_at, or on every occurrence of cron in timezone. Runcrate checks schedules every 2 minutes, so a run starts within about 2 minutes of its time, as run_as through run_as_credential, in the environment it was created in. When many schedules are due at once, each workspace gets its turn.