Under the hood
Useful1 Signal2
Refused slash commands are now logged with a reason, so support can tell stale lists from policy blocks.
What's wrong with this entry?
Anonymous. No account, no email.
What
When 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.
Details
- Emitted from the same command dispatch path that applies the policy check.
- Replaces the previous unknown/unavailable buckets, so a refusal caused by a stale list is separable from one your organization's policy caused.
Evidence
cmd_stale_list
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command