Jobs that run on time without a server cron
Declare a schedule in the app manifest, every 15 minutes or on a cron line, and the platform calls your app on time with a signed schedule.tick.
Schedules · Rider Sync
In short
An app declares up to five schedules in its manifest, each with a name and either an interval like 15m, 2h or 1d or a cron expression. The platform triggers each run as a signed schedule.tick webhook, and switches a schedule off after three dead lettered runs in a row.
The problem it solves
An app that syncs stock every hour needs its own always on server just to keep time. When that server sleeps, the sync quietly stops.
How it works
3 steps, start to finish
-
1
Declare it
Add a [[schedules]] entry with a name and either every or cron, with an optional timezone.
-
2
Ship the version
The schedule is registered with the app.
-
3
Receive the tick
Each run arrives as a signed schedule.tick webhook.
In detail
What schedules does for you
-
Intervals or cron
Forms like 15m, 2h and 1d, or a cron expression.
-
Timezones
Give a schedule its own timezone.
-
Sane limits
At least five minutes apart, at most 30 days, five schedules per app.
-
Stops when broken
Three dead lettered runs in a row switch the schedule off.
-
Every five minutes at most, and at least once every 30 days.
-
The platform sends a signed schedule.tick webhook, verified like any other webhook.
-
After three dead lettered runs in a row the schedule is switched off automatically.
Schedules · Free to start
Try schedules on your own business
Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.
- Live in 2 minutes
- Free to start
- No credit card
