discord.js - Imagine an app•10mo ago

interaction works on and off

Alright, I'm wondering if discord has some sort of rate limit when you testing commands, because it started to refuse so replies that usually work and it doesn't make no sense why it would stop receiving, so far the only successful wait has been to stop testing for like a few minutes and then try again and the command works... Here is the command:

    await interaction.showModal(modal);

      const modalResponse = await interaction.awaitModalSubmit({ time: 180000 });
      await modalResponse.deferReply({ ephemeral: true });

    await interaction.showModal(modal);

      const modalResponse = await interaction.awaitModalSubmit({ time: 180000 });
      await modalResponse.deferReply({ ephemeral: true });

` The defer reply shows throws unknow message error. Anyone seen anything like that? I just want to make sure it isn't any new change or option I need supply.

3 Replies

d.js toolkit•10mo ago

- What's your exact discord.js npm list discord.js and node node -v version? - Not a discord.js issue? Check out #other-js-ts. - Consider reading #how-to-get-help to improve your question! - Explain what exactly your issue is. - Post the full error stack trace, not just the top part! - Show your code! - Issue solved? Press the button!

duck•10mo ago

just to clarify, you may receive "Unknown interaction", but you shouldn't be receiving "Unknown message" from deferReply on the assumption you're receiving the former, this error just means that your bot didn't respond to the interaction within 3 seconds since you aren't doing anything between collecting it and responding, it's probably an issue with your host itself if you are receiving "Unknown message", please share the whole error since it's likely unrelated to the code shown

SharpOP•10mo ago

Yeah unknow message is the weirdest, after try all of that, what solved was closing and opening vs code... I guess something is wrong when starting and finishing many debug sessions i'm trying to purposely reproduce it now and see if closing and opening vs code will actually fix it again and will post it here for updates and/or future reference

Gaming

Programming

interaction works on and off