BizKitHub
PUBLIC_CRON_RUN_EXPIRED

Cron run expired and was closed as timed out.

HTTP 409Public API
No call arrived within the run expiration, so the run was closed as `timeout` and a critical log entry was written. Every log or heartbeat call extends the expiration.

How to resolve

  1. 1

    Send `/cron-run/{id}/heartbeat` during long silent steps.

  2. 2

    Start the run with a longer `expiration` (seconds).

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 expired and was closed as timed out.",
  "errorCode": "PUBLIC_CRON_RUN_EXPIRED",
  "hint": "No call arrived within the run expiration, so the run was closed as `timeout` and a critical log entry was written. Every log or heartbeat call extends the expiration.",
  "documentationUrl": "https://docs.bizkithub.com/errors/PUBLIC_CRON_RUN_EXPIRED"
}