Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Access errors on removing reaction #521

Open
kevinlul opened this issue Oct 4, 2024 · 0 comments
Open

Missing Access errors on removing reaction #521

kevinlul opened this issue Oct 4, 2024 · 0 comments
Labels
production Incidents from the running Bastion#1870 instance

Comments

@kevinlul
Copy link
Contributor

kevinlul commented Oct 4, 2024

"msg":"Could not remove reaction","error":{"requestBody":{},"rawError":{"message":"Missing Access","code":50001},"code":50001,"status":403,"method":"DELETE"

In principle, this should not be happening. Bastion only tries to remove its own reaction if it is present, which means Bastion had permission to add the reaction, and Bastion should always be allowed to remove its own reaction.

https://github.com/DawnbrandBots/bastion-bot/blob/master/src/events/message-search.ts

@kevinlul kevinlul added the production Incidents from the running Bastion#1870 instance label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
production Incidents from the running Bastion#1870 instance
Projects
None yet
Development

No branches or pull requests

1 participant