← All chapters

Schedules

Work that starts without anybody pressing anything.

The routes

GET/trons/:id/schedulesWrapped: { schedules }.
POST/trons/:id/schedulesCreates one.
PATCH/schedules/:idEdits one. Note the path is not under the tron.
DELETE/schedules/:idRemoves it.
POST/schedules/:id/runFires it now.
GET/automazioniEverything that starts by itself, in one answer: schedules (agent crons included), the bridges, and the API keys.

One scheduling engine

This table is the only scheduler. An agent’s cron in the Lab is a row here, and an agent that still carries a cron trigger in its definition gets one made at deploy. When a row is due the scheduler queues a job; the work queue runs it on the agent when the agent is free, waking the tron if it sleeps — no tron is kept on just to keep a clock running. «Every N days» counts days from the day the schedule was made, and if the platform was down at the time of a run, at most the last missed run is made up.