Encountered response failures after updating or republishing Copilot agents?

Greggory Rodgers 0 Reputation points
2026-05-14T18:27:07.95+00:00

A few of us within my organization are seeing the same issue with Copilot agents, but it appears to only affect agents that were recently updated. The error message we’re receiving is: “Sorry, I wasn’t able to respond to that. Is there something else I can help with?” Based on what we’re seeing, this does not appear to be an individual user issue, since multiple people are experiencing the same behavior. It also does not seem to affect all agents, mainly agents that were recently changed or republished. Has anyone else experience this issue or have any further details?

My specific agent is not connected to our SharePoint. It relies only on the information provided by the user as its source of truth. It works as expected when tested in the configuration panel, but when I test it within Copilot, it responds to that specific message instead.

Microsoft Copilot | Microsoft 365 Copilot | Development
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-05-14T18:27:17.38+00:00

    The behavior matches a known post-publish issue where Teams or Microsoft 365 Copilot continues to use an older agent configuration after an update or republish, which can cause generic runtime failures such as “Sorry, I wasn’t able to respond to that. Is there something else I can help with?” on recently changed agents.

    To address this, refresh the agent configuration in the channel where it runs (Teams / Microsoft 365 Copilot) and then republish:

    1. In the Microsoft Teams admin center, locate the agent app, disable it, wait a few seconds, and then re-enable it.
    2. In Copilot Studio, open the agent and turn off the Teams (or Microsoft 365 Copilot) channel, save the change, and then turn the channel back on.
    3. Republish the agent so the latest configuration is available to the channel.
    4. Test again from Copilot (not only in the configuration panel) to confirm that the new version is being used.

    If the problem persists across multiple users after these steps, collect the Conversation ID, Agent ID, and the time of the error from a failing conversation and open a support case with Microsoft Support so they can investigate backend issues affecting updated agents.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer 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.