{"version":"2.1.248","anchor":"internally-queued-commands-no-longer-inflate-enqueue-counts","canonical_anchor":"internally-queued-commands-no-longer-inflate-enqueue-counts","heading":"Internally queued commands no longer inflate enqueue counts","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/internally-queued-commands-no-longer-inflate-enqueue-counts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Internally queued commands no longer inflate enqueue counts\n\nInternally injected commands no longer count toward queue telemetry.\n\n**What**\n\nItems added to the message queue can now carry an `unlogged` marker, and both the \"next\" and \"later\" paths skip their telemetry call when it is set. The same change fixes the log call to report the item being queued rather than an unrelated captured value.\n\n**Evidence**\n\n`!wn.unlogged`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}