Muse Is Disconnected: Why It Happens and How to Fix It

What does the disconnected message mean?

The message reads, in full, as documented in user reports: Muse is disconnected. We disconnected Muse to protect your information. Submit a feedback ticket to reconnect. It is a server side protective lock on your account, not a connection error. Your internet is fine, the app is not broken, and no amount of signal checking will change the screen.

What happened is that Meta's systems deliberately severed the Muse connection after something tripped a security check on the linked Meta account. The Meta account itself usually keeps working fine: Facebook, Instagram, and Threads stay up, and only the Muse connection is cut. The notice gives no reason code, no specific trigger, and no timeline. That silence is part of what makes the message so frustrating, and it is consistent across the reports we have seen.

Keep this state separate from two neighboring ones. A locked account greets you at sign in: you were out, and now you cannot get in. A suspended account announces itself with the word suspended and points you at a support ticket. A disconnection interrupts you mid session or greets you on opening the app, with the protective wording above. Our guide to locked, suspended, and disconnected accounts separates the three states in full, including the October 14, 2026 evening when several users were disconnected at roughly the same time. This guide stays focused on the disconnected banner and the fix for it.

Why does Muse disconnect accounts?

Meta has published no criteria for disconnections and no list of behaviors that triggers them, so every cause below is a reported association, not a confirmed rule. The honest position is that in many cases the user never learns the trigger. The patterns below come from user reports and community discussions, and they are worth knowing because they shape what you should check first.

The most reported trigger is a security event on the linked Meta or Facebook account. Reports describe disconnections after a password change, after account recovery, and in one case confirmed in Meta community forum reports, after changing an Instagram username. The logic appears to be that when the underlying Meta account goes through a security check, the Muse connection is severed as a precaution. The account itself recovers, but the Muse link does not restore itself.

A second pattern involves automated activity flags. One user reported that after asking Muse to analyze a Facebook flag on their posting, Facebook, Threads, and Instagram under the whole Meta account started having issues, and Muse disconnected immediately. Their reading was that Meta's risk systems mistook Muse's own activity for bot activity. That reading is the user's own, not Meta's, but the sequence, a flag on one Meta service followed by a Muse disconnection, appears in more than one report.

A third pattern is credential churn. Users in community discussions report disconnections after changing a password and email address and adding two factor authentication in quick succession, with the disconnect appearing days later when they returned to the app. Again, the link is reported, not proven, and plenty of users change credentials without any problem. But rapid changes to the linked account are worth noting when you describe your case to support.

Finally, some disconnections are Meta's side, not yours. On the evening of October 14, 2026, multiple users reported being disconnected at roughly the same time while doing nothing unusual, a pattern that points at a platform problem rather than individual behavior. Waves like that are a reason not to assume you did something wrong, and a reason to check whether others are reporting the same thing before you rebuild your setup.

What does not fix it?

Because the lock lives on Meta's servers, device level fixes do not work. Users who hit the notice have tried all of the following, and none of them restored access: reinstalling the app, toggling WiFi, switching from WiFi to mobile data, reloading the browser, switching devices, and signing out and back in. If the banner is the protective disconnect message, these steps waste your time.

Resetting your password does not fix it either, on its own. Community reports include cases where the disconnection persisted even after password resets. Completing a security verification on your Meta account is still worth doing if Meta asks for it, because an unresolved security check can block the reconnection, but a password reset by itself is not the fix.

Changing your IP address does not fix it. A VPN, a proxy, or a different network cannot restore an unlinked or disconnected account, because the lock is attached to the account, not to the connection. Repeated country IP changes are not a recovery procedure, and they may add new security flags to the account you are trying to recover.

Filing duplicate tickets does not help either. Multiple identical reports do not move a case faster, and they can split the conversation across threads. File once, through the route that actually goes through, save the reference number, and wait for the email reply. The next section covers that route.

How do I get a disconnected account back?

There is no instant fix, and anyone promising one is selling something. The only real path is getting Meta's support team to reconnect your account, and the route you use to reach them matters, because the form the banner points to often fails. Work through these steps in order.

1. Save the details first. Note the exact message on screen, the date and time, your device, the app version, and the last thing you did before the disconnect. Screenshots help, with personal information hidden. Support will ask for this, and your memory of it will fade.
2. Check your Meta account. Open Facebook or Instagram and confirm the underlying account works. If Meta shows a security check, a verification step, or a lock there, complete it first. The Muse reconnection depends on the linked account being in good standing.
3. Use Report an issue, not the ticket form. On the web at muse.ai, click the gear icon for Settings, then Help and support, then Report an issue. Choose the Accounts/activation category. This route completes and returns a Bug ID, while the feedback ticket form the banner points to often fails with a Something went wrong error while you are disconnected. If the app offers a Report a problem option in its help menu, that is the same route on mobile, and on some clients shaking the device opens it.
4. Write a report support can act on. Include the exact notice text, the date and time it appeared, what you were doing just before, and any recent security events on the linked account, such as a password change or a recovery. Ask explicitly to reconnect your existing account and restore your data, not to create a new account. A new account loses your history, your workflows, and your codes.
5. Use a reply email you control. Enter an inbox you can receive replies at, including spam folder checks. Do not enter an old inbox you can no longer open. Support replies by email, and a dead reply address means a dead case.
6. Save the Bug ID and wait. The Report an issue submission returns a Bug ID. Keep it. There is no guaranteed recovery window: reports describe waits from days to no reply at all, and no official documentation promises a timeframe. If support asks for verification, such as confirming you are a real person, complete it promptly and through official channels only.

One warning that applies to every step: never share passwords or verification codes with third parties offering account recovery. No legitimate recovery process needs your password, and anyone asking for it is running a scam. Muse's official support process handles account access reviews, and store support handles purchases only.

What if the ticket form returns a 403 error?

A 403 error means the request was refused. It does not by itself prove the account is banned, and it does not mean your case was received. If the feedback ticket form returns 403, or a Something went wrong message with no confirmation, treat the submission as failed, not as filed.

This failure is common while disconnected. The form the banner points to appears to depend on the same session the lock just severed, so it fails for the people who need it most. Users have reported the 403 consistently, and the workaround is the Report an issue route described above, which goes through and returns a Bug ID.

If you hit the 403, report the broken form itself in your Report an issue submission: note that ticket submission returns 403, with the time and a screenshot. Keep any report number, Bug ID, or ticket number you receive. An in app bug report can document a broken form, but it does not by itself prove an account appeal was accepted, so be explicit in the report text that you are requesting reconnection of the existing account.

Do not keep hammering the failed form. Repeated failed submissions do not create a case, and they do not speed up the review. One successful Report an issue submission with a Bug ID is worth more than ten failed ticket attempts.

Is unlinked the same as disconnected?

They belong to the same family, but the wording differs and the distinction is worth making. The disconnected banner says Meta disconnected Muse to protect your information. The unlinked message says Muse has been unlinked from the account, and it usually carries a support ticket option on the same screen. Both are account access states that need a support review, and both use the same recovery route.

An unlinked message does not necessarily mean your login email was removed or changed. Changing a login email is a separate action, and the unlinked message alone does not establish that contact details changed. Check the complete message and whether your account contact details actually changed before concluding anything about the login itself.

Similarly, a single unlinked message does not establish a ban, and it does not establish a service wide incident. It establishes that your account needs a review. The steps are the same as for a disconnection: save the details, use the support ticket option on the screen if it works, fall back to Report an issue if it returns 403, choose the Account access and sign in topic if offered, and wait for the email reply.

If the unlinked screen offers a topic choice, choose Account access and sign in, or the closest account access or login category available. Describe the account, the timing, and the actions just before the message appeared. Recovery, verification requirements, and timing all depend on the support response, and no fixed window applies.

What if I bought the account?

Bought accounts show up in disconnection reports more than any other single pattern, and the honest advice is blunt: an account you bought is far more likely to be disconnected, and far harder to recover. Reports from community discussions describe bought accounts lasting about a day before disconnection, and sellers' accounts demanding repeated proof that the holder is a real person.

One discussion from November 2026 includes a user who had two accounts banned, one obtained for free and one bought for 30 cents, with both lasting a day. Another user in the same discussion reported that a bought account required verification that they were a real person, then a fresh login, a CAPTCHA, a second email verification, and finally a photo upload to prove identity. Another reported creating dozens of accounts and seeing nearly half banned, with appeals approved in minutes but the lock screen still showing on opening the account.

The pattern makes sense from Meta's side. An account that changes hands, changes credentials, changes devices, and changes locations in quick succession looks exactly like a compromised account, which is what the protective disconnect is built to catch. Whether the account was bought, shared, or simply handed over, the signals are the same, and the lock treats them the same way.

If your bought account is disconnected, the support route is the same, but set expectations honestly. Support may ask for identity verification you cannot pass, because the account was not created with your identity. Appeals may be approved on paper while the lock persists in the app. And a reconnection, if it comes, may not last, because the underlying signals have not changed. The safe route is an account you created yourself, with your own email, your own recovery details, and your own history. Invite codes, which are free from the community pool, add tokens to your own account without any of the risks of a bought one.

What if only a connected app says disconnected?

That is a different problem with a much easier fix, and it is important not to confuse the two. A disconnected account locks you out of Muse entirely. A disconnected connector means one linked service, such as Gmail or Google Calendar, lost its sign in, while Muse itself keeps working. The fix for a connector is local and usually takes a minute.

The fix that usually works is revoke and reconnect. Remove the connection in Muse settings, then connect it again, watching for blocked OAuth popups, which are the most common cause of a half finished connection. If one surface says connected while another says it is not, complete the connection once on muse.ai in a desktop browser and let it sync to the app. That clears most half finished states. Work or school accounts may need admin approval before they connect at all.

Two design limits are worth knowing. First, disconnecting a service stops new data, not old memories: anything Muse already used can remain in memories and chat history. To clear that, ask Muse to forget those interactions, or use Settings, then Data Controls, then Reset Muse, and revoke access on the provider side too, such as Google's third party connections page. Second, Muse filters out verification codes and login links by design, so a hijacked agent cannot take over your other accounts. Do sign ups and logins yourself, then hand Muse the finished account.

Our connector list covers every service Muse connects to, and our permissions guide explains what each access level lets Muse do. If a connector keeps dropping after a clean reconnect, the provider side is the next place to look, not the Muse app.

How do I lower the chance it happens again?

No habit guarantees you will never be disconnected. Platform waves hit users doing nothing unusual, and Meta publishes no criteria. But the reported patterns suggest a few precautions that cost nothing and remove the most common triggers.

• Use one account you created yourself. Do not buy accounts, do not share accounts, and do not create stacks of spare accounts. Every one of those patterns appears in disconnection reports.
• Space out credential changes. If you need to change a password, an email address, and add two factor authentication, do them on different days rather than all at once, and complete any security verification Meta shows you before returning to Muse.
• Keep a recovery email you control. Support replies by email. An inbox you cannot open turns a recoverable case into a lost one.
• Protect your codes and workflows before anything goes wrong. Keep copies of workflow prompts and important Muse outputs outside the app, and redeem invite codes promptly, since the token reward window is 48 hours from joining. Our account safety guide covers the habits that protect your codes and workflows in more detail.
• Complete security checks promptly. If Facebook, Instagram, or Meta shows a verification step, do it right away rather than letting it sit. An unresolved check on the linked account is the most reported precursor to a Muse disconnect.

If it happens despite all of that, remember the core of this guide: save the details, use Report an issue, ask for reconnection of the existing account, save the Bug ID, and wait for the email reply. The lock is on Meta's servers, and patience plus the right route beats every device trick.

Get started

Once your account is back, start with one small task to confirm everything works, then reconnect any services that dropped during the lock. If you are new to Muse and setting up a fresh account of your own, redeem a free invite code within 48 hours of joining and both you and the person who shared it get 1 billion Muse tokens.

Get a free code from the community pool.

Frequently asked questions

What does Muse is disconnected mean?

It means Meta's systems severed the Muse connection to protect your information, after a security check on the linked Meta account. It is a server side protective lock, not a WiFi or app problem. Your Meta account itself usually keeps working, and only the Muse connection is cut.

Will reinstalling the app fix a disconnected Muse?

No. The lock lives on Meta's servers, not on your device, so reinstalling the app, toggling WiFi, switching devices, and reloading the browser do not restore access. Only Meta's support team can lift the lock, through the Report an issue route.

How do I contact Muse support about a disconnection?

On the web at muse.ai, open Settings, then Help and support, then Report an issue, and choose the Accounts/activation category. Describe the exact message, the timing, and recent security events, and ask to reconnect your existing account and restore your data. Save the Bug ID it returns, and watch your email for the reply.

What does a 403 error mean on the ticket form?

A 403 error means the request was refused, and it does not by itself prove the account is banned. The feedback ticket form often fails with 403 while you are disconnected. Treat the submission as failed, and file through Report an issue instead, noting the 403 with the time and a screenshot.

Can a bought Muse account be reconnected?

Possibly, but reports show bought accounts face repeated identity verification and frequent disconnection, with some lasting about a day. Support may ask for proof you cannot pass if the account was not created with your identity. The same support route applies, but there is no guarantee, and an account you created yourself is far safer.

Is a disconnected connector the same as a disconnected account?

No. A disconnected connector means one linked service lost its sign in while Muse keeps working, and the fix is to revoke and reconnect it, ideally once on muse.ai in a desktop browser. A disconnected account locks you out of Muse entirely and needs Meta support to lift the lock.

Built with Muse is an independent community project. Not affiliated with or endorsed by Meta.