{"version":"2.1.286","anchor":"background-dispatch-failures-report-a-gate-cause","canonical_anchor":"background-dispatch-failures-report-a-gate-cause","heading":"Failed background task launches now report what blocked them","tier":"internal","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/background-dispatch-failures-report-a-gate-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Failed background task launches now report what blocked them\n\nWhen starting a background task fails, the report Claude Code records now includes what blocked it\n\n**Unclear.** The possible values of the new cause are not known.\n\n**What**\n\nWhen Claude Code fails to start a background task, it records the failure in its usage data. For launches from the fleet view and from the command line (`fleet_view_dispatch` and `cli_bg_dispatch`), that record used to hold only the reason, such as a failure to start. It now also includes the cause when a restriction blocked the launch.\n\n**Why**\n\nThis does not change what you see, but it makes blocked background launches easier to diagnose.\n\n- Area: Background Tasks\n- Names: `fleet_view_dispatch`, `cli_bg_dispatch`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}