SCH_STALEScheduler heartbeat stale
CriticalSCHAffects operatorsRetry: not retryable
The scheduler runner is reachable but has not reported a recent heartbeat. Jobs may be stuck; restart the runner if the condition persists.
Likely causes
- The background job runner is registered but has not reported a heartbeat recently.
- The runner process is hung or overloaded.
How to resolve
- 1
This is a platform-side condition. BizKitHub operations are alerted automatically.
- 2
Delayed background jobs continue once the runner recovers or is restarted.
- 3
Contact [email protected] if jobs remain stuck.
Where you will see it
The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:
Notification subject
[SCH_STALE] [sch] …