cron
Covers 1 API operations in the cron category.
| Method | Path | Description |
|---|---|---|
| GET | /v1/orgs/{orgSlug}/projects/{projectName}/cron | Scheduled runs: what is declared, when it fires next, what happened |
GET /v1/orgs/{orgSlug}/projects/{projectName}/cron
One call, because the three answers are only useful together (docs/cron.md §8).
schedules comes from the live deployment, not the newest one: a rollback
restores the schedules that version declared, so the newest deployment's list can
name expressions nothing is firing.
nextRunAt is computed server-side with the one cron parser there is
(internal/cronexpr). A second implementation in the client would be a second
answer to "when does this fire", and the two would disagree on exactly the
expressions a person opens this screen to check.
History is kept for keepDays and then pruned — an empty runs is not proof that
nothing ever ran.
operationId getProjectCron
| Parameter | Location | Required | Type | Description |
|---|---|---|---|---|
limit | query | No | integer | How many history rows. Default 50, capped at 200. |
| Status code | Description | Response body |
|---|---|---|
| 200 | Schedules, their next fire time, and the recent history | CronOverview |
| 403 | — | — |
| 404 | — | — |