-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Error happens when trying to edit a followup message: [Could not find the channel where this message came from in the cache!] #10441
Comments
Is this on User App? In which case it is understandable as channels might not be cached. Use .editReply(...) |
Is there a way to edit a follow-up message without overriding the previous one? I’m creating a quiz bot that asks 5 random questions. Each time a user selects an option, I want to record their choice without replacing the previous question message. However, editReply() overwrites the last message, and followup() creates a new message. I want all the questions and their answers to be displayed together |
|
But when I was trying to use |
What's confusing? We're telling you to use Do not use |
Got it, thanks for answering my question, this issue could be closed |
followup message should be edit like this: const msg = await interaction.followUp("followup")
await interaction.editReply({ message:msg, content:"new msg" }) // now followup message change to "new msg" |
Yes, again, you should refer to docs. It has all the answers |
Which package is this bug report for?
discord.js
Issue description
when I was trying to edit a message which was "followupped" by an interaction, it crashed and tolds an error:
the code below can reproduce on my environment
It seem the
edit()
function is unable to use on a followup message?Code sample
Versions
Issue priority
Low (slightly annoying)
Which partials do you have configured?
No Partials
Which gateway intents are you subscribing to?
Guilds
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: