{
  "id": 10579996,
  "title": "Nodejs Cron Health Checks: 5 Heartbeat Controls for Missed Marketplace Jobs",
  "url": "https://urgent.news/2026/09/29/nodejs-cron-health-checks-5-heartbeat-controls-for-missed-marketplace",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-29T01:45:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/oskarholm4968/nodejs-cron-health-checks-5-heartbeat-controls-for-missed-marketplace-jobs-2pkm"
  },
  "original_language": "en",
  "account": null,
  "summary": "The article discusses the importance of implementing a Nodejs cron health check to detect missed jobs in a marketplace pipeline. The key points are that absence must be observed from outside the process, and an external heartbeat monitor is needed to detect missed jobs. The article outlines five controls for a Nodejs cron health check: expected-run control, attempt control, diagnostic control, attribution control, and notification control. Each control has specific requirements and failure boundaries, such as using a heartbeat service to own the cron schedule and grace period, recording start, failure, and success against one run_id, and attaching stable, low-cardinality dimensions such as pipeline_id and cost_center to metrics and logs. The article emphasizes the importance of separating concerns between the heartbeat service and the worker process, and the need for explicit notification delivery.",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}