{"version":"2.1.234","anchor":"a-crashing-slash-command-now-tells-you-it-crashed","canonical_anchor":"a-crashing-slash-command-now-tells-you-it-crashed","heading":"A crashing slash command now tells you it crashed","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-crashing-slash-command-now-tells-you-it-crashed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A crashing slash command now tells you it crashed\n\nA slash command that crashes now tells you, instead of silently clearing the screen.\n\n**What**\n\nWhen one of the interactive slash commands throws, the error is reported back into the conversation as command stderr instead of the UI just clearing. Telemetry now separates a command you aborted from one that threw.\n\n**Evidence**\n\n`cmd_local_jsx_aborted`\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}