{"version":"2.1.280","anchor":"background-command-failed-status-no-longer-distinguishes-n","canonical_anchor":"background-command-failed-status-no-longer-distinguishes-n","heading":"Background command 'failed' status no longer distinguishes non-zero exit code","tier":"notice","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/background-command-failed-status-no-longer-distinguishes-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Background command 'failed' status no longer distinguishes non-zero exit code\n\nBackground command status now marks 'failed' based only on presence of a result, not on a non-zero exit code\n\n**Unclear.** The finding does not say what visible effect this has, such as whether commands that previously showed as failed now show as succeeded or vice versa.\n\n**What**\n\nThe logic that marks a background command or task entry as `failed` has changed. Previously it checked whether the command produced a result and whether that result's exit code was non-zero. Now it only checks whether a result exists at all, without looking at the exit code.\n\n**Why**\n\nThis changes when background commands are reported as failed versus succeeded, since a non-zero exit code alone no longer determines the failed state.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}