{"version":"2.1.280","anchor":"new-telemetry-which-plugin-the-hooks-worker-heartbeat-blame","canonical_anchor":"new-telemetry-which-plugin-the-hooks-worker-heartbeat-blame","heading":"New telemetry: which plugin the hooks-worker heartbeat blames when wedged","tier":"internal","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-telemetry-which-plugin-the-hooks-worker-heartbeat-blame","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New telemetry: which plugin the hooks-worker heartbeat blames when wedged\n\nHooks-worker heartbeat failures now log which plugin is likely responsible\n\n**What**\n\nWhen the background worker that runs hooks (small scripts triggered by events) misses its heartbeat past a timeout, Claude Code now logs which plugin is most likely to blame, along with the evidence for that conclusion, before declaring the worker wedged (stuck).\n\n**Why**\n\nThis makes it easier to diagnose which plugin caused the hooks worker to hang, instead of only knowing that something went wrong.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}