Step-by-Step Fix
-
Confirm the scope
- Try a different browser/device and a different network.
- If only one environment fails, the cause is usually local.
-
Refresh your session
- Sign out completely, then sign back in.
- Clear cache/cookies for the service domain.
- Try an incognito/private window with no extensions.
-
Check permissions and plan status
- Verify you’re using the correct account/workspace.
- Confirm your subscription/plan is active and assigned correctly.
-
Rule out network filtering
- Disable VPN/proxy temporarily.
- Pause ad blockers / privacy tools that may block requests.
- If you’re on a corporate network, test via hotspot.
-
Check service incidents
- Review the product status page or recent incident reports.
- If the service is degraded, wait and retry.
-
Collect evidence and escalate
- Save screenshots + exact error text + timestamps.
- Include environment details and repro steps in a support ticket.
Common Root Causes
- Expired/invalid session tokens
- Plan or permission mismatch
- Browser extensions interfering with requests
- Network blocks (VPN/proxy/firewall/DNS)
- Temporary outages
Prevention Tips
- Keep a clean browser profile for critical workflows
- Don’t stack multiple privacy extensions that rewrite requests
- Document workspace/team permissions and billing owners
- Export important settings regularly (when supported)
Why This Happens
The "Interaction failed" error in Discord occurs when the Midjourney bot receives a command from your client but fails to process it within Discord’s 3-second response window. This does not necessarily mean the bot is completely offline — it can happen when Midjourney’s servers are under heavy load and cannot acknowledge the interaction in time, when there is a brief outage on Midjourney’s infrastructure, or when Discord itself is experiencing API issues that delay message delivery. The error can also appear when the bot’s permissions in a specific server have been changed, preventing it from responding to slash commands even when the bot is otherwise operational.
Common Mistakes to Avoid
- Assuming "interaction failed" means your prompt was processed and the image will appear later — when this error appears, the job was not queued; you need to resubmit the command
- Spamming the same command after getting the error — during heavy load, rapid resubmission can worsen the queue congestion that caused the error in the first place; wait 1 to 2 minutes before retrying
- Not checking Discord’s status page in addition to Midjourney’s — "interaction failed" can be caused by Discord’s own API issues, which require Discord (not Midjourney) to fix; check discordstatus.com
- Using the bot in a server where its permissions have been restricted — if a server administrator recently changed bot permissions, the Midjourney bot may no longer have permission to respond to slash commands in that channel
- Not trying a DM to the bot — if the error is channel-specific rather than global, you can test by sending
/imaginedirectly in a DM to the Midjourney Bot to confirm whether the issue is server-specific
FAQ
Q: Does "interaction failed" mean I was charged for the job?
No. "Interaction failed" means the bot did not process your request — no GPU time was consumed and no Fast hours were deducted. The interaction failed before the job entered the queue, so you can safely resubmit the same prompt without worrying about being charged twice.
Q: How do I know if the Midjourney bot is down or just slow?
Check status.midjourney.com for any active incidents. If no incident is listed but the bot is consistently returning "interaction failed" across multiple attempts, check discordstatus.com for Discord API issues. If both status pages show all systems operational but the bot is still failing, it may be a brief localized issue — wait 5 minutes and try again. The Midjourney bot typically recovers from brief failures within minutes.
Q: Can I use Midjourney’s web interface when the bot is not responding?
Yes. Midjourney’s web interface at midjourney.com operates independently of the Discord bot. If the Discord bot is returning "interaction failed," try submitting your prompt through the Midjourney web interface at midjourney.com. The two interfaces share the same account and subscription but use different infrastructure, so a Discord bot issue does not necessarily affect the web interface.
Q: Why does the Midjourney bot work in some Discord servers but show "interaction failed" in others?
Bot failures that are server-specific usually indicate a permissions problem in that particular server. The Midjourney bot requires specific permissions to respond to slash commands: "Use Application Commands" must be enabled for the role or channel where you are trying to use it. If a server admin recently changed bot permissions or channel settings, this can cause "interaction failed" in that server while the bot works normally elsewhere. Ask the server admin to check bot permissions in that channel.
Q: The Midjourney bot responded to my command but then showed "interaction failed" when I clicked a button (like Upscale or Variation) — why?
Button interaction failures (on Upscale, Variation, or other action buttons below generated images) occur when the original interaction token expires. Discord interaction tokens are valid for 15 minutes after the original command. If you wait more than 15 minutes to click an Upscale or Variation button, the token expires and the button returns "interaction failed." The fix is to resubmit the original /imagine command and act on the buttons within 15 minutes of generation.
Related Issues
- Midjourney Job Failed Image Not Generating
- Midjourney Stuck Queued Long Time
- Midjourney Account Not Recognized in Discord
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Q: Why do hard refresh and regular refresh fix different problems? A regular refresh (F5) reloads the page using cached resources — it does not clear JavaScript bundles, service worker state, or session cookies. A hard refresh (Ctrl+Shift+R or Cmd+Shift+R) bypasses the cache and fetches all resources fresh from the server. Regular refresh fixes transient network hiccups; hard refresh fixes stale cached code. Neither clears cookies or session tokens — for that, you need to clear site data explicitly from browser settings.
Q: When should I contact support versus waiting it out? Contact support immediately if: you were charged but did not receive access, your account was suspended without explanation, or the problem affects billing or data. Wait and retry after 30–60 minutes if: a status page shows an ongoing incident, the error message says 'try again later', or the problem started very recently. For account-specific errors with no platform-wide incident, opening a support ticket is always the right move — document what you tried and include timestamps.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.