{"version":"2.1.248","anchor":"sandbox-failures-now-report-a-specific-cause","canonical_anchor":"sandbox-failures-now-report-a-specific-cause","heading":"Sandbox failures now report a specific cause","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/sandbox-failures-now-report-a-specific-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Sandbox failures now report a specific cause\n\nSandbox failures now name the stage that broke instead of a generic error.\n\n**What**\n\nThe sandbox layer raises named errors instead of generic ones, so a failure says which stage broke: init, an unavailable bridge, no sandbox for this shell, a command too long, or a policy refusal carrying its own reason.\n\n**Details**\n\n- Ships with a schema for per-host network policy entries: an `action` of allow or deny plus optional HTTP `methods`.\n\n**Evidence**\n\n`SandboxPolicyRefusalError`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}