Closed CapricaBSG closed 1 year ago
Do you have some heavy load on your node-red or network problems? Because this error comes when you don't reply the interaction in seconds
There is some heavy network usage. Is there any way to call deferUpdate() outside of this?
An idea is to separate discord flow on a node-red instance and another instance with the heavy network usage.
Sometimes when the bot is responding to a command it will throw 'DiscordAPIError: Unknown interaction', it comes from discordInteraction.js. I have tested this with a 'test' command that does nothing except respond to a command. Sometimes it works sometimes it fails and when it does it throws the aforementioned error
Looking at discordInteraction.js
` registerCallback("interactionCreate", async interaction => { try { if (!matchInteractionType(interaction)) return;
I believe throw is at await interaction.reply({ content: commandResponse, ephemeral: ephemeral }).
it is a very annoying much, as a quicker fix I suggest sending the interaction obnject along with the node-red status so I am atleast able to respond to the command another way