You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started receiving odd Missing Permission errors in my bots logs in the past months despite checking for all required channel permissions, finally being able to track them down to the fact that timeouts seem to suddenly affect bots now.
I'm certain this used to not be the case, with bots being exempt from timeouts. More perplexing, this behavior seems to be inconsistent now between regular messages and slash commands.
Steps to Reproduce
Time out a bot in a server
Attempt to send a message via the bot
Attempt to run a (server) slash command via the bot
Attempt to run a (user) slash command via the bot
Observe
Expected Behavior
(Previous expected behavior) All of them work
(Potentially expected by a moderator) None of them work (or respond publicly in the case of user commands)
Current Behavior
The message fails, the slash commands "work" and create a new public message.
Screenshots/Videos
No response
Client and System Information
N/A
The text was updated successfully, but these errors were encountered:
Description
I've started receiving odd Missing Permission errors in my bots logs in the past months despite checking for all required channel permissions, finally being able to track them down to the fact that timeouts seem to suddenly affect bots now.
I'm certain this used to not be the case, with bots being exempt from timeouts. More perplexing, this behavior seems to be inconsistent now between regular messages and slash commands.
Steps to Reproduce
Expected Behavior
(Previous expected behavior) All of them work
(Potentially expected by a moderator) None of them work (or respond publicly in the case of user commands)
Current Behavior
The message fails, the slash commands "work" and create a new public message.
Screenshots/Videos
No response
Client and System Information
N/A
The text was updated successfully, but these errors were encountered: