{"version":"2.1.246","anchor":"background-dispatch-failures-distinguish-daemon-startup-erro","canonical_anchor":"background-dispatch-failures-distinguish-daemon-startup-erro","heading":"Background dispatch failures distinguish daemon startup errors","tier":"internal","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/background-dispatch-failures-distinguish-daemon-startup-erro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Background dispatch failures distinguish daemon startup errors\n\nBackground dispatch failures now distinguish a daemon that started but couldn't launch Claude Code.\n\n**What**\n\nThe `tengu_bg_dispatch_fallback` telemetry now classifies failures where the daemon started but Claude Code did not under a daemon-stderr reason, with a parsed exit code or signal appended when one is present, before falling back to the previous path-bearing and truncated-message forms.\n\n**Evidence**\n\n`tengu_bg_dispatch_fallback`\n\n- Area: Background Tasks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}