What changed
"Missing Permissions" on its own never told anyone what to do. Now every error is tied to the block that failed, and says why in plain words and how to fix it. Every Discord error has its own words, and the common ones name the real cause: a channel override that turns off a permission, a role above your bot's, a member who owns the server, an emoji Discord can't read, or a reply that came after Discord's 3 seconds.
The Errors page
Each error shows the block, why it failed, the steps to fix it, and who ran it, where and when. Open one to see what each setting came out as, and What changed before it failed: every variable the run changed before the block broke. Show in builder takes you straight to the block.
- Mute errors you expect, like a member with DMs off. They stay listed but nobody is told.
- Dismiss clears one error, and Dismiss all clears everything listed. An error that happens again comes back.
In the builder
Blocks that failed in Discord get a red ring and a Failed tag. The Errors button next to Problems counts the errors you haven't opened yet. If your own run fails while the builder is open, a pop up shows the fix straight away, with Replay and Copy to run again. Fix the block, run it again, and That fixed it marks the error fixed.
In Discord
When you or a collaborator run a command that fails, your bot sends you a private fix tip with what went wrong, the steps, and a link to the error. Members never get one. Switch it off in a command's When it fails settings.
Good to know
- Errors are kept for 7 days, or 30 days with Premium. Premium also keeps the last 3 runs of each error.
- Your older error logs are still there, under Older logs.
- A red Failing chip on the Commands and Events lists shows anything that failed in the last day.
Full list of changes
- NewThe Errors page is rebuilt: every error shows which block failed, why in plain words, how to fix it, and who ran it, where and when (7 days free, 30 days with Premium)
- NewEvery Discord error in plain words: errors now name the real cause, such as an emoji Discord can't read, a member whose role is above your bot's, or a reply that came after 3 seconds, with the steps to fix it
- NewWhat changed before it failed on the Errors page, with a Show what changed before it failed choice in When it fails
- NewMute for errors you expect, and Dismiss and Dismiss all to clear errors and the older logs
- NewFix tips: when you or a collaborator run a command that fails, your bot privately tells you what went wrong and how to fix it, with a link to the error
- NewShow Errors on Blocks: blocks that failed in Discord get a red ring and a Failed tag
- NewA Last run card in block settings, and an Errors button next to Problems that counts only errors you haven't opened yet, with Mark all seen
- NewAn instant pop up when your run fails while the builder is open, with Show me the fix, Replay, Copy to run again and Mute
- NewThat fixed it: after you fix a block, the next run that gets past it says so and marks the error fixed
- NewA red Failing chip on the Commands and Events lists, and a Failing in Discord line on opened commands and events with See the errors
- ImprovedOther people's failed runs only pop up the first time each error shows up, with Pop Up Every Time for Others' Runs in Builder Settings
