search

Dougley / MegaBot

Discord bot that interacts with Zendesk Community
GNU Affero General Public License v3.0
1 stars 0 forks source link

MegaBot complains that it is unable to DM you, even though it did. #18

Closed Kitty-Therapist closed 5 years ago

Kitty-Therapist commented 5 years ago

Describe the bug When using the command, MegaBot proceeds to direct-message you - only to send a message saying that it has failed DMing you even though that it did. To Reproduce Steps to reproduce the behavior: 1.) Use the command !stats 2.) Observe as MegaBot sends you a direct message. 3.) Come back to Custodian Central to observe.

Expected behavior MegaBot should have deleted your !stats message, and have DM'd you the information.

Actual Behavior MegaBot sends you a direct-message, then sends a message in Custodian Central, complaining that it couldn't DM you.

Screenshots https://cdn.discordapp.com/attachments/284796966641205249/521117963042947102/unknown.png

Additional context No additional information, as far that I am concerned.

Dougley commented 5 years ago

Can't reproduce in dev, need more info

MoonlightCapital commented 5 years ago

That happened to me as well while I was testing a local copy of the bot. I think that's related to the promise catch, which is catching something else that is not necessarily the bot being unable to DM the user (read: the old unexpected error we GVs loved)

https://github.com/Dougley/MBv2/blob/master/src/commands/stats.js#L16

Dougley commented 5 years ago

Narrowed this down to it being a permission issue in production, closing since this issue is unrelated to code.