{"version":"2.1.248","anchor":"emptied-messages-are-explicitly-not-treated-as-subscriptions","canonical_anchor":"emptied-messages-are-explicitly-not-treated-as-subscriptions","heading":"Emptied messages are explicitly not treated as subscriptions","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/emptied-messages-are-explicitly-not-treated-as-subscriptions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Emptied messages are explicitly not treated as subscriptions\n\nA tool result now spells out that a blanked message means nothing was sent and nothing subscribed.\n\n**What**\n\nA fixed tool result now states that when a permission handler blanks out a message, nothing was sent and no idle subscription was created, closing off an ambiguous reading of that case.\n\n**Evidence**\n\n`a blanked delivery is never reinterpreted as a pure subscription`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}