-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
Some slash commands occasionally return the message, "The application did not respond." This issue likely occurs because the bot does not respond within three seconds. To address this, it is recommended to use ctx.defer or to reply immediately and then check if the subsequent actions have been completed before editing the message accordingly.
To reproduce
- Run the command
/kick,/tempbanor/warnwith appropriate permission on your account (role). - Occasionally, you'll notice the application returns "The application did not respond".
Expected behavior
The expected behaviour is that the bot handles the delay by responding promptly and updating the state (message).
Relevant log output
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working