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
Running a user app slash command in a thread, then locking the thread before the command can respond (for example via deferred message or followup) will result in an unavoidable error.
If the bot is in the server the
{"message": "Thread is archived", "code": 50083}
error will be returned by the API. If the bot is not in the server, the error will be
{"message": "Missing Access", "code": 50001}
Steps to Reproduce
Run a slash command in a thread.
Have the command respond with a deferred ack.
Lock the thread as a moderator.
Have the bot respond to the deferred command.
Observe
Expected Behavior
The response message is forced ephemeral for the user who ran the command, as happens with context menu commands inside of locked threads.
Current Behavior
The API will return an error that cannot be predicted/avoided.
Screenshots/Videos
Command gets stuck in an infinite loading state, the bot developer will see an annoying error in their logs
Client and System Information
The text was updated successfully, but these errors were encountered:
Description
Running a user app slash command in a thread, then locking the thread before the command can respond (for example via deferred message or followup) will result in an unavoidable error.
If the bot is in the server the
error will be returned by the API. If the bot is not in the server, the error will be
Steps to Reproduce
Expected Behavior
The response message is forced ephemeral for the user who ran the command, as happens with context menu commands inside of locked threads.
Current Behavior
The API will return an error that cannot be predicted/avoided.
Screenshots/Videos
Client and System Information
The text was updated successfully, but these errors were encountered: