PUBLIC_CRON_RUN_RECORD_INVALIDRecorded cron run has invalid timestamps.
HTTP 400Public API
`startedAt` and `finishedAt` must be ISO-8601 times, `startedAt` must not be after `finishedAt`, neither may lie more than 5 minutes in the future and `startedAt` may be at most 7 days old.
How to resolve
- 1
Send times in UTC with a `Z` suffix, e.g. `2026-11-05T12:00:00.000Z`.
Example response
The API answers with HTTP 400 and a JSON body. Match on errorCode, not on message: messages may be reworded, codes are stable.
application/json
{
"state": "error",
"code": 400,
"message": "Recorded cron run has invalid timestamps.",
"errorCode": "PUBLIC_CRON_RUN_RECORD_INVALID",
"hint": "`startedAt` and `finishedAt` must be ISO-8601 times, `startedAt` must not be after `finishedAt`, neither may lie more than 5 minutes in the future and `startedAt` may be at most 7 days old.",
"documentationUrl": "https://docs.bizkithub.com/errors/PUBLIC_CRON_RUN_RECORD_INVALID"
}