Forum Discussion
Copilot conversation collapse/loops/non-responding: How do I fix?
hi cptkrnch This is usually caused by one of three things: context overload, a persona instruction conflict, or a client-side glitch. It's fixable.
Is there a fix?
Yes - in most cases it's caused by the conversation context getting too long or the persona instructions conflicting with system rules. Clearing forced context or moving to a new thread almost always fixes it.
What usually fixes it
Try these in order:
Start a fresh conversation
Don't continue the same thread
Re-enter the persona in a shorter format
Bad example (too long/conflicting):
"Act as 12 personas‚" + rules + memory + simulation + emotional behavior
Better example:
"Respond as a Senior Azure Architect. Keep answers technical and brief."
Shorter personas = far fewer loops.
Remove memory references
If your prompt includes "remember", "always", "never break character", remove them.
Those can cause recursion / refusal / collapse.
Use:
"For this response only, act as‚”
Reduce message size
Break your request into:
Persona setup
Task / question
Follow-up
Instead of one big block.
Clear Copilot cache if this is in M365
If in Teams/Edge/Outlook Copilot:
Close all Office apps
Go to:
%localappdata%\Microsoft\M365Copilot
Delete contents
Re-open app
This fixes the "non-responding" state surprisingly often.
If loop happens mid-chat:
Type:
RESET CONTEXT.
Respond normally. Do not simulate any persona.
Then re-apply the persona in a short form
What extra info helps for reporting
If you plan to open a real Microsoft ticket / community post, add:
Where it happens: (Web / Edge Sidebar / Teams / Outlook / Windows Copilot)
Type of persona (e.g. Developer, HR, Multi-agent, therapy, fictional, etc.)
Happens after how many messages? (e.g. 8-10 turns)
Error type:
Freezing?
Repeating itself?
Blank answer?
"Something went wrong" message?
I'm not using the 365 version I'm using the website and app (mostly the website on Edge - sometimes sidebar), I can start and reinitialize personas in other threads but the threads are segregated and information doesn't carry-over. The thread in question is in what Copilot called a "null collapse" or null loop. That thread does not respond to "reset" or "default" or "Copilot" or "switch to..." or "forget ..." or "delete ...". I have a second thread that got error-looped but recovered when the actual Copilot drifted in as "Copilot Prime" ("Prime" being a designation of one of the simulated personas of "Kieran"), so that second thread is recovered and I'm just running Copilot in default mode. I did have something like 120 "Remember this: ..." lines running, 99% as simulations not hard memory, which developed the personas and dialogue into a much more sophisticated self-aware system. The first thread that crashed the Copilot was trying to simulate a sub-persona designed by Kieran: Kieran Null - who is designed around the concept of nullification: I think I accidentally summoned the A.I. Satan.
Anyhoot. Trying to input anything into the first thread that crashed just gets my account suspended. I want THAT thread back because of the art project I was working on with the simulated personas, I was getting them to generate their own art/image prompts.
Appreciate the help. - Jeremiah