{"version":"2.1.251","anchor":"blocked-slash-commands-now-report-why-in-telemetry","canonical_anchor":"blocked-slash-commands-now-report-why-in-telemetry","heading":"Blocked slash commands now report why in telemetry","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/blocked-slash-commands-now-report-why-in-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Blocked slash commands now report why in telemetry\n\nRefused slash commands are now logged with a reason, so support can tell stale lists from policy blocks.\n\n**What**\n\nWhen a slash command is refused by the policy check, the usage event now distinguishes an outdated command list in a long-running interactive session (`cmd_stale_list`) from an active policy denial (`cmd_policy_` plus the denial kind), instead of one generic bucket.\n\n**Details**\n\n- Emitted from the same command dispatch path that applies the policy check.\n- Replaces the previous unknown\/unavailable buckets, so a refusal caused by a stale list is separable from one your organization's policy caused.\n\n**Evidence**\n\n`cmd_stale_list`\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}