PUBLIC_CRON_RUN_RATE_LIMITEDCron monitor request quota of the API key is exhausted.
HTTP 429Public API
Requests to `/api/v1/cron-run/*` have their own fixed hourly quota per API key (separate from the quota of other endpoints). Every response carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` headers.
How to resolve
- 1
Send logs in batches (`entries`, up to 100) instead of one request per entry.
- 2
Report short runs with a single `POST /cron-run/record` instead of start + finish.
- 3
Wait until the time in `X-RateLimit-Reset` (Unix seconds) or the `Retry-After` header.
Example response
The API answers with HTTP 429 and a JSON body. Match on errorCode, not on message: messages may be reworded, codes are stable.
application/json
{
"state": "error",
"code": 429,
"message": "Cron monitor request quota of the API key is exhausted.",
"errorCode": "PUBLIC_CRON_RUN_RATE_LIMITED",
"hint": "Requests to `/api/v1/cron-run/*` have their own fixed hourly quota per API key (separate from the quota of other endpoints). Every response carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` headers.",
"documentationUrl": "https://docs.bizkithub.com/errors/PUBLIC_CRON_RUN_RATE_LIMITED"
}