{"version":"2.1.242","anchor":"proxy-denial-details-no-longer-reach-the-model","canonical_anchor":"proxy-denial-details-no-longer-reach-the-model","heading":"Proxy denial details no longer reach the model","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/proxy-denial-details-no-longer-reach-the-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Proxy denial details no longer reach the model\n\nWhen a proxy blocks a fetch, only the connect status reaches the model; details go to debug logs.\n\n**What**\n\nWhen a network egress proxy blocks an artifact content or asset fetch, the proxy's marker and status detail now go to the debug log, and the message returned to the model keeps only the connect status.\n\n**Details**\n\n- Both artifact fetch paths also gained a branch reporting that the relay is unavailable.\n\n**Evidence**\n\n`[artifact] asset fetch: egress proxy denied`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}