A dashboard for failed Interactions #3707
Replies: 2 comments 1 reply
-
|
I really like the idea. Sometimes interactions fail but I don't know why because I can't reproduce it and no error is logged |
Beta Was this translation helpful? Give feedback.
-
|
or idk, maybe the API response can be a bit more, eh, descriptive? for now the api response after the interaction has failed just contains your payload and the interaction id (cannot use it to trace down the error or for that matter, where the slash command was ran) and the interaction token (same goes for this, cannot use it in debugging), so i guess it would be a bit more, eh, good? if they kind of, maybe add the guild id or the command id in the API response. I also don't really see how a dashboard for the failed interactions would be any useful but something like this would be amazing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This applies more to services that completely run using outgoing webhooks, but I'd love to see a dashboard where I can see how many Interactions failed and more importantly, why.
Right now, if an Interaction fails for some reason, it's blind debugging: there is no way to check why it failed (this is especially the case when you have to respond to an interaction, since you're the one responding and not Discord)
Beta Was this translation helpful? Give feedback.
All reactions