If you set up a Ticket panel, a Reaction Role or an Embed with MEE6 and then switch to a custom bot created through the Discord Developer Portal, those interactive elements will stop functioning and become uneditable on the MEE6 Dashboard.
This is caused by how Discord controls which bot "owns" certain interactive panels, embeds and buttons.
Understanding "This interaction failed" Error
When a ticket panel is created, it's tied to the exact bot that created it, based on the unique bot ID.
If that panel was originally made by the MEE6 bot or a different custom bot, Discord won't let your new custom bot control it.
As a result, the buttons no longer respond after you switch bots, because they still "belong" to the old bot.
Same thing happens with your Embeds and Reaction Role panels.
How to Fix It
Step 1. Duplicate the Panel.
Go to the Ticketing plugin page, find the panel that isn't working, click on the three-dot menu, and select Duplicate.
This creates a new panel that your current custom bot can “own” and manage.
Once this new panel is published and used, it will respond correctly, because it's now authorized for your custom bot.
Step 2. Repeat this for all other Ticketing panels, Embeds and Reaction Roles.
This Discord security measure is applicable only to these 3 plugins inside MEE6.
Other plugins will start working properly as soon as your custom bot is installed, no duplication is needed.
Step 3. Custom Bot Application settings.
If the new copy of the panel still isn't working, there might be an issue with the custom bot itself.
To fix this, visit https://discord.com/developers/applications, select your custom bot application and open its "Bot" tab.
Ensure that Privileged Gateway Intents are enabled (all three of them) and that "Requires Oauth2 code grant" is disabled.
Summary
If your Ticket panel, Reaction Role panel, or embed stops working after switching to your custom bot (or reverting back to the standard MEE6 bot, or after changing custom bot applications), simply duplicate the panel to recreate it under your current bot's ownership.
If that doesn’t resolve the issue, check your custom bot's application settings in the Discord Developer Portal and then try reinstalling it.
This ensures your custom bot is fully authorized to manage these interactive elements.
If you have any questions about this, do not hesitate to join our Support Server✌️