You click Verify. A little red line appears: “This interaction failed.” No role, no explanation, no dignity. Here is what that line actually means, because it is more specific than it sounds.
What Discord is telling you
Buttons, menus and slash commands are interactions. When you click, Discord sends the click to the bot and waits. Discord’s developer docs set a hard rule: the bot must send an initial response within 3 seconds. If it misses that window, the interaction token is invalidated and you get “This interaction failed”.
So the message is not about you, your account or your verification. It means the bot did not pick up the phone in 3 seconds.
Why a verify bot misses the 3 seconds
| Cause | How it looks | Who fixes it |
|---|---|---|
| Bot is offline or restarting | Every click fails, for everyone | Server staff or the bot’s host |
| Old button the bot no longer handles | Fails on an old verify message, a new one works | Staff: post a fresh verify message |
| Bot is slow under load | Fails for some people, works for others | The bot’s developer |
| Bot crashes on your click | Fails every time for you | The bot’s developer |
| Discord is having an incident | Lots of bots fail at once | Nobody. Check status.discord.com and wait |
Why it gets worse during a raid or a big announcement
Every click is its own interaction with its own 3-second clock. When a hundred people hit Verify in the same minute, a slow bot works through them one after another, and the ones at the back of the queue run out of time. Those people click again, which adds more work to the queue, which makes more clicks fail. That is why “it works for me but not for them” is so common right after a server gets shared somewhere big.
The same thing happens to slash commands, with different words. A command the bot does not answer in time shows “The application did not respond” instead. Same cause, same fixes.
If you are a member trying to verify
- Wait a minute and click once more. If the bot was restarting, it may be back.
- Still failing? Stop clicking. It will not queue up, and you are only spamming the bot.
- Tell the server staff, ideally with a screenshot of the error and the time it happened.
- Check status.discord.com in case it is Discord rather than the bot.
Watch out
If someone DMs you a “fixed” verification that needs you to scan a QR code or download a file, that is a scam. Discord’s QR scanner only logs devices into your account.
If you run the server
- Check the bot is online in your member list. Offline means its host is down or its token was reset.
- Post a fresh verification message. Buttons on very old messages may point at a handler the bot no longer has.
- Check the bot can still give the role: its role must sit above the verified role, and it needs Manage Roles.
- Try it yourself on an alt or a friend’s account, then delete the old verify message so nobody keeps clicking it.
If you wrote the bot
The fix is in the docs. Do not do slow work before you answer. Acknowledge first, then edit:
- For a button, reply with a deferred update (type 6) or a deferred message (type 5, the user sees a loading state).
- Then do the database call, the role change or the captcha link, and edit the original response.
- The interaction token stays valid for 15 minutes for follow-ups and edits, which is plenty.
A verify setup that does not fall over
- One verify message in one channel. Old copies in other channels are old buttons waiting to fail.
- A bot that stays online. Free hosts that sleep after a few minutes idle are the classic cause of a first click failing.
- The bot’s role near the top of the list, with Manage Roles, so the click that does get answered also gets the role.
- Logs. When someone says “verify is broken”, you want to see whether they clicked at all, failed a check or never got an answer.
- A test after every change: new bot, new role, new channel permissions. Thirty seconds on a second account saves an evening of DMs.
“Verification failed” is a different message
If the bot did answer and told you verification failed, the bot worked. You were stopped by a check, such as account age, a VPN or a blocklist. That is the server’s decision, and only the staff can let you in. The symptom table on the front page covers those.
Checked against Discord’s docs and help center. Updated .