{"version":"2.1.124","anchor":"background-job-working-directory-error-is-now-actionable","canonical_anchor":"background-job-working-directory-error-is-now-actionable","heading":"Background-job working-directory error is now actionable","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124\/e\/background-job-working-directory-error-is-now-actionable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.124","markdown":"### Background-job working-directory error is now actionable\n\nWhen a background worker can't spawn because its `cwd` no longer exists, the job is marked permanently `crashed` instead of looping respawn attempts:\n\n`working directory no longer exists: <cwd> [<reason> \u2014 this job cannot be respawned]` The same path also fires the new `tengu_bg_spawn_cwd_gone` telemetry event.\n\n**Evidence**\n\nBackground spawn cwd-gone (search for `\"working directory no longer exists:\"` and `\"this job cannot be respawned\"`)."}