Feel free to ask me, if you have questions about this idea.īeta Was this translation helpful? Give feedback.įunction myInteractionCallback ( ctx ) Since there's no other useful information an error message could have, we only need content. In autocomplete interactions, it would simply be under clyde, but I was not able to edit that xDĬontent - The content of the error message This will always be the message where the error will be shown, that the bot has responded to. Interactions are always designed to have an "This interaction has failed" error message. In modals we have an error message inside of the modal, which means, bots can have their error there (ignore german language): It can also be useful for buttons with a timeout or something. The bot responded to that button with "You are not allowed to use this button." This is an example for a button that only one user should be allowed to use. So why not adding the error response to ALL interactions? Yes, it is possible to do this with a message, but ephemeral messages need to get dismissed or there will be a public message which is not that useful. This can also be useful in other interactions, because bots can give more accurate information about the error. So I thought about making a response for that. Since modals popup and user may submit wrong information, people may want to know, what the error actually is, but don't want to close the modal and open it again. I got the idea today to make an interaction response for the error message.