{"version":"2.1.229","anchor":"a-failed-sandbox-startup-no-longer-sticks","canonical_anchor":"a-failed-sandbox-startup-no-longer-sticks","heading":"A failed sandbox startup no longer sticks","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/a-failed-sandbox-startup-no-longer-sticks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### A failed sandbox startup no longer sticks\n\nIf the sandbox fails to start, a later attempt can now succeed instead of failing forever.\n\n**What**\n\nWhen sandbox initialization fails, it now clears its recorded state and returns instead of caching a rejected promise, so a later attempt can succeed. A successful init clears the previous failure reason.\n\n**Details**\n\n- The reset covers both whether the sandbox was started with TLS termination and a new flag recording whether the installed network filter actually enforces the allowlist.\n- The settings-change subscription now also re-subscribes to the stream of denied plugin producer directories.\n- A new helper answers whether the sandbox is currently usable without re-running the dependency probe.\n\n**Evidence**\n\n`Sandbox configuration updated from settings change`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}