{"version":"2.1.280","anchor":"new-per-field-unavailability-message-used-for-run-in-backgr","canonical_anchor":"new-per-field-unavailability-message-used-for-run-in-backgr","heading":"New per-field unavailability message, used for run_in_background","tier":"notice","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-per-field-unavailability-message-used-for-run-in-backgr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New per-field unavailability message, used for run_in_background\n\nNew unavailability message explains why a background-running task field can't be used in some environments\n\n**What**\n\nAn internal helper that used to only show a \"Checking GitHub CLI installation...\" spinner has been turned into a general message generator producing lines like \"{field} is not available on {target}.\" It has a special case for `run_in_background`: when it's unavailable, the message explains that the calling session has no way to poll a background task there, and suggests running it in the foreground or in the session's own environment instead.\n\n**Why**\n\nThis gives a clearer explanation when a particular option, such as running a command in the background, can't be used in the current environment, instead of a generic error.\n\n- Area: Background Tasks\n- Names: `run_in_background`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}