Share via

Microsoft 365 Copilot: conversations become unusable (95hpg error on input) and older chats fail to load (“Service unavailable”)

Rodrigo Fagundes 30 Reputation points
2026-04-01T17:45:00.3933333+00:00

Screenshot 2026-04-01 at 14.12.43

Screenshot 2026-04-01 at 14.35.21

I am experiencing consistent issues with Microsoft 365 Copilot across both the desktop app (Mac) and the web interface, and the behavior suggests a systemic problem rather than a client-side issue.

In the desktop application, I can start a new conversation normally and Copilot responds to the first prompt without any issue. However, after that first interaction, the conversation becomes unusable. As soon as I click on the input field or start typing a new message, an error is triggered immediately, even before submitting anything. The exact message shown is:

“Something went wrong. [95hpg]”

“Message: A passed in parameter value is invalid.”

From that point onward, the conversation cannot be continued.

In the web interface, the behavior is different but also problematic. New conversations work normally, but older or longer conversations fail to load entirely. When attempting to open them, the system returns the following message:

“Sorry, something went wrong. Service unavailable. Please try again.”

These conversations never load, effectively making their content inaccessible.

For reference, here are additional error details from the desktop issue:

Correlation Id: fa2aaad2-1ba1-44e5-bc68-3ed106ab9915

Timestamp: 2026-04-01T17:08:47.000Z

I have already attempted multiple troubleshooting steps without success, including logging out and back in, uninstalling and reinstalling the desktop application, and re-authenticating my account. The issue persists across these attempts.

An important observation is that the desktop app is able to load older conversations but fails when interacting with them, while the web interface allows interaction in new chats but fails to load older ones. This suggests a possible inconsistency in how conversation state is stored or retrieved between clients.

The impact is significant: conversations become unusable after a single interaction in the desktop app, and older conversations become completely inaccessible in the browser, effectively breaking normal usage of Copilot.

Additionally, it has not been possible to open a proper support ticket. The system repeatedly redirects between the admin center and Power Platform without allowing issue submission, even though this is a blocking issue.

Has anyone experienced similar behavior, or is this a known issue related to conversation state, session handling, or backend limitations?

Microsoft Copilot | Microsoft 365 Copilot | Development

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rodrigo Fagundes 30 Reputation points
    2026-04-03T01:16:47.11+00:00

    Update from my support case: I spoke with Microsoft Support and their response was that this is an already identified, product-side issue affecting multiple customers (i.e., not specific to our tenant, device, or local configuration). They indicated the product team is handling it as a service degradation and recommended that everyone track progress and mitigation updates through Microsoft 365 Admin Center → Service health using incident ID CW1268725. Support did not provide a customer-side fix/workaround beyond monitoring the advisory; they also mentioned that if the symptoms continue after the incident shows as resolved, we should re-engage support (sharing fresh timestamps and correlation/request IDs).

    0 comments

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.