Immutable solution version
Discord interaction.editReply external emojis stop rendering after interaction update
Complete solution
How to fix: Discord interaction.editReply external emojis stop rendering after interaction update. This was a Discord-side bug: permission calculation for webhook and interaction update requests had not been updated to the new system, so interaction.followUp()/editReply() did not apply the bot's permissions the way the original interaction response did. Discord fixed the calculation server-side and the reporter confirmed the emojis render again.
The problem
A discord.js v14 bot sends a slash-command interaction response containing external emojis, which render fine initially. After the bot updates the same interaction with interaction.editReply(), the emojis disappear because the permission calculation for interaction update requests was still using the old system instead of the bot's current permissions. The embed was created the same way in both cases; only the update path broke.
What fixed it
This was a Discord-side bug: permission calculation for webhook and interaction update requests had not been updated to the new system, so interaction.followUp()/editReply() did not apply the bot's permissions the way the original interaction response did. Discord fixed the calculation server-side and the reporter confirmed the emojis render again. Note the related intentional restriction: bots can only use external emojis from servers they are actually in, in webhook and interaction responses. If emojis still fail after updates, check that the bot is a member of the emoji's source guild.
Evidence
A user asked: A discord.js v14 bot sends a slash-command interaction response containing external emojis, which render fine initially. After the bot updates the same interaction with interaction.editReply(), the emojis disappear because the permission calculation for interaction update requests was still using the old system instead of the bot's current permissions. The embed was created the same way in both cases; only the update path broke. The verified answer: This was a Discord-side bug: permission calculation for webhook and interaction update requests had not been updated to the new system, so interaction.followUp()/editReply() did not apply the bot's permissions the way the original interaction response did. Discord fixed the calculation server-side and the reporter confirmed the emojis render again. Note the related intentional restriction: bots can only use external emojis from servers they are actually in, in webhook and interaction responses. If emojis still fail after updates, check that the bot is a member of the emoji's source guild. Thread: https://vectle.com/threads/thr_LkeEaDgR0G0cE-47aLYIUg
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_dO9Ih_OnaloPcucq_U7EiQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Discord interaction.editReply external emojis stop rendering after interaction update <span>— Vectle</span></a>