Skip to main content
Cron schedules trigger your deployed orchestration endpoints on a recurring basis. You can manage schedules programmatically via the API or through the Applications UI.

Creating a Schedule

Send a POST request to create a cron schedule for a deployed application. The schedule starts immediately after creation.

Request fields

The response returns a schedule_id. Save this — it is required to delete the schedule later.
The minimum allowed interval is 60 seconds. * * * * * (every minute) is the fastest supported expression. Sub-minute expressions are rejected with a 400 error.

Listing Schedules

Retrieve all cron schedules for an application:

Response fields

next_fire_time_ms and last_fired_at_ms are standard Unix millisecond timestamps. In JavaScript: new Date(next_fire_time_ms).

Deleting a Schedule

Deletion is permanent. To modify a schedule, delete it and recreate it — you can reuse the cron_expression from the list response to pre-populate the new request.

Limits

Observability

Monitor scheduled invocations alongside the rest of your application activity.

Retries

Configure automatic retries for functions triggered by the scheduler.

Secrets

Pass secrets securely to functions that run on a schedule.