Symptom
Cron jobs whose delivery takes more than about a minute are recorded as failed with 'Interrupted by shutdown before terminal completion', though the work finished.
Evidence what you'll see
- Nothing actually shut down
- The job's work (for example a backup) completed
- Also reported as 'Fire claim ownership lost'
Cause
The claim heartbeat tried to renew through the same lock the job's own run thread was holding, timed out, and the timeout was read as losing ownership.
Fix steps
0 of 1 done
Your check marks stay in this browser only.
Verify the fix worked
- Run a cron job that takes longer than 60 seconds and confirm it's recorded as succeeded.
Sources and credit
Summarized in our own words from these public reports. Credit goes to their authors.
Provided as is, without warranty. Try changes in a non-production environment and back up first. Security-related steps: verify against the official docs. Terms · Request removal or attribution change
Hit an error we don't cover? Submit it