{"version":"2.1.239","anchor":"data-loss-prevention-blocks-are-marked-separately-from-fetch","canonical_anchor":"data-loss-prevention-blocks-are-marked-separately-from-fetch","heading":"Data-loss-prevention blocks are marked separately from fetch failures","tier":"internal","area":"Web Fetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/data-loss-prevention-blocks-are-marked-separately-from-fetch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Data-loss-prevention blocks are marked separately from fetch failures\n\nA fetch blocked by data-loss-prevention policy is now distinguishable from an ordinary network failure.\n\n**What**\n\nA failed content fetch can now be tagged `isDlpDenied` alongside the existing detail, status and timeout fields, so a block by data-loss-prevention policy is distinguishable from an ordinary network failure. The name is new in this build.\n\n**Evidence**\n\n`isDlpDenied`\n\n- Area: Web Fetch\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}