Forum Discussion
Copilot unusable since the latest UI updates were forced on users
Is anyone else having massive issues with Copilot since the latest UI rollout was forced on them with no option to switch back?
Problems I have been experiencing:
- Loss of chat history - initially, this appears to have been a sync/re-index issue as a result of the roll out but, whilst most of my chats & projects are now accessible, some (a few) have lost all the history & context that had been built up
- The UI does not focus on the latest messages output when a chat message is sent - it randomly scrolls to a part of the conversation and school to end is needed (TBH, this is the least disruptive issue - but still a massive pain, poor UI and a drain on productivity)
- Copilot cannot see files within a one drive folder - it can see the folder but, cannot access any of the files contained within the folder resource. Adding the files individually does work but, that causes admin overhead and risk of files not being referenced when new files are added
- There appears to be undocumented (& more importantly, unprompted) limits to conversations lengths in chats - have some chats that have been running for many days which then stop processing any further messages with a message: Sorry, I wasn't able to respond to that. Is there something else I can help with?
- No warning that chat length is nearing any limits
- No documentation on what the limit is
- Once hit, the chat becomes useless since the context cannot be referenced in a new chat
- No way to ask for a summary of the chat to maintain context into a new thread - the chat is useless save for scrolling back and cut/pasting relevant context into a new thread
- Conversations randomly truncating - often a conversation that has a significant history does not show the full conversation
These problems have degraded a product that was solid and, causing massive overhead in workload to 'work around', they limit the value of the product to me as a user and make me question whether to take the leap and switch to another (much better) AI tool set.
Has this actually been tested by Microsoft before forcing on CUSTOMERS or, are your users being treated as unpaid QA resources...
2 Replies
The symptoms point to more than one failure, so one broad reset is unlikely to help. I would preserve evidence from an affected chat before clearing browser data: copy its URL, conversation title, approximate message count, last date that loaded correctly, and the UTC time of each failure. If a thread opens even once, move the important facts into a Word or OneNote document immediately rather than relying on that thread as the only copy.
For the OneDrive-folder issue, test a new folder containing two small files with ordinary inherited permissions. Add that folder as a resource and ask Copilot to name both files. If individual files work but the clean folder does not, report it as folder enumeration rather than file access. Include whether the folder is personal OneDrive or SharePoint, whether shortcuts are involved, and whether the same account can open every file on the web.
Long conversations should be reported separately with the conversation URL and request/correlation ID from the failed load. Start a continuation chat with a manually reviewed summary while the original remains intact. Do not delete the original, repeatedly reinstall apps, or remove its project until Microsoft confirms whether history is missing or only failing to render.
No voice microphone since update. Have stopped using it , Tried enabling permissions again, wipe cache, uninstall reinstall, About to give up when I saw this post.
