Copilot aparentemente não recuperando contexto ou "lembrando" informações da mesma maneira que antes.

Coelho, Laura (ext) 20 Reputation points
2026-09-21T12:48:40.4766667+00:00

Since last Friday, I noticed that Copilot repeatedly struggled to access or correctly use information that had already been shared within the same conversation. I was using prompts and workflows that I use regularly and that usually work very well.

In several different chats, Copilot appeared unable to retrieve messages that had been sent only a few moments earlier. Tasks that normally require linking the most recent prompt to information provided immediately before it were not working as expected.

What was unusual is that this did not seem to be limited to long-term conversation history. Instead, Copilot appeared to have difficulty accessing even the very recent context from the same chat thread. Normally, it can connect information from different points in the conversation with no difficulty, including details shared much earlier in the same discussion.

Because this behavior occurred multiple times across different conversations, I wondered whether there may have been a temporary issue affecting conversation memory, context retrieval, or chat history access.

Have there been any known issues, incidents, or changes that might explain this behavior?

I wanted to provide this feedback because maintaining continuity across messages is one of the features I rely on most heavily in my daily work.

Thank you for your support and for looking into it.

Microsoft Copilot | Windows Copilot | App
0 comments No comments

Answer accepted by question author
Clary-N 16,565 Reputation points Microsoft External Staff Moderator
2026-09-22T01:02:32.7266667+00:00

Hi Coelho, Laura (ext),

Thank you for providing such a clear and detailed report. I understand how disruptive this must be when your regular workflows depend on Copilot maintaining continuity between messages.

I haven’t found confirmation of a publicly documented incident that specifically matches the recent-context behavior you described. To help determine whether this may be platform-specific or account-related, could you confirm:

  • Whether you’re using a personal Microsoft account or a work or school account
  • Where you experienced the issue, such as the web version, Windows app, mobile app or Microsoft 365 Copilot
  • Whether the same behavior occurs across multiple devices or browsers
  • The approximate date, time and time zone of one or two recent examples

If it happens again, please select Send feedback > Report a problem from the menu in the upper-right corner of Copilot. Include when it occurred, your device and operating system and a screenshot if possible, with any personal or confidential information removed. These details can help with investigating the affected session.

If you’re using a work or school account, I also recommend asking your Microsoft 365 administrator to check Health > Service health for any advisories affecting your organization. For a continuing or business-critical issue, the administrator can use Help & Support in the Microsoft 365 admin center to contact support or open a service request.

In the meantime, starting a new chat may temporarily restore normal behavior, although I understand that this is only a workaround and does not address the underlying loss of continuity. Since this is a user-to-user support forum, contributors don’t have access to account details, service logs or back-end systems and can’t make changes directly to Copilot. However, I can share troubleshooting guidance and point you toward the appropriate support channel if the issue needs further investigation.

If the issue continues, the additional details submitted through feedback or a support request should help the appropriate team investigate it further.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.