PUBLIC_CRON_RUN_CLOSEDCron run is already finished.
HTTP 409Public API
The run was already finished, so it accepts no more log entries, heartbeats or finish calls.
How to resolve
- 1
Start a new run with `/cron-run/start` for the next execution.
Example response
The API answers with HTTP 409 and a JSON body. Match on errorCode, not on message: messages may be reworded, codes are stable.
application/json
{
"state": "error",
"code": 409,
"message": "Cron run is already finished.",
"errorCode": "PUBLIC_CRON_RUN_CLOSED",
"hint": "The run was already finished, so it accepts no more log entries, heartbeats or finish calls.",
"documentationUrl": "https://docs.bizkithub.com/errors/PUBLIC_CRON_RUN_CLOSED"
}