{
  "id": 11976659,
  "title": "My Health Check Watched the Wrong File",
  "url": "https://urgent.news/2026/10/04/my-health-check-watched-the-wrong-file",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-04T18:05:19.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/kenielzep97/my-health-check-watched-the-wrong-file-p7h"
  },
  "original_language": "en",
  "account": "The health check tool mistakenly identified three Telegram poller jobs as dead when they were actually functioning correctly. The tool relied on a file that was only updated during startup and when an exception occurred, leading the reporter to believe the jobs had stopped. However, upon closer inspection, the reporter observed that the jobs were indeed running, as evidenced by the advancing state files. The reporter realized that the health check tool was not accurately detecting the jobs' status due to its reliance on outdated information and a misunderstanding of the jobs' behavior.",
  "summary": "I wrote a rule for my own agents: Liveness is not usefulness. Artifact age beats PID. A job that is loaded, looks healthy to the supervisor, and is producing nothing is the failure worth catching. Anyone can detect exit 127. Then I applied the rule to my own machine and got the wrong answer. What I saw Three listener jobs. launchctl lists them. pgrep -f sentinel_listen.py returns a PID. Their log…",
  "key_points": [
    "Health check tool misidentified Telegram poller jobs as dead",
    "Jobs were actually functioning correctly, not stopped",
    "Tool relied on outdated file, misunderstanding job behavior"
  ],
  "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."
}