{"version":"2.1.281","anchor":"slash-command-results-now-record-a-failure-outcome","canonical_anchor":"slash-command-results-now-record-a-failure-outcome","heading":"Slash command results now record a failure outcome","tier":"internal","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/slash-command-results-now-record-a-failure-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Slash command results now record a failure outcome\n\nSlash commands now record whether they failed, with the skill usage command and \/recap marking their errors as failed\n\n**Unclear.** The finding does not say where `commandOutcome` is shown or reported, or what the internal condition is.\n\n**What**\n\nSlash commands are the commands you type starting with `\/`. Their results can now carry an outcome, and the record of each command run stores it as `commandOutcome`. Under one internal condition the outcome is always recorded as failed. Two commands now mark errors as failed:\n\n- The skill usage command, when it shows \"Couldn't compute skill usage.\"\n\n- `\/recap`, when the request to the model returns an error.\n\nThe build also has \"unavailable_headless\" and \"unknown\" outcome kinds.\n\n**Why**\n\nA command that hits an error is now recorded as failed rather than as having run normally.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}