Power Platform Community Forum Thread Details

On a Microsoft Teams agent, when clicking Quick Replies or Allow, an error message appears saying:
“Something went wrong. Please try again.”
This issue does not occur in Copilot Studio test mode, where the agent works as expected.

Steps to Reproduce

The agent displays Quick Replies using Send Message.
The user clicks one of the Quick Reply buttons.
The selected Quick Reply is not sent, and the error message “Something went wrong. Please try again.” is displayed.

Conditions / Observations

The issue occurs for all users (not user-specific).
The problem does not occur with other agents created in Copilot Studio.
When a new agent is created using the same instructions, knowledge sources, topics, and settings as the problematic agent, the issue does not occur.

Question

Has anyone experienced a similar issue with Quick Replies or Allow buttons on a published Microsoft Teams agent?
Any insights into possible causes or troubleshooting steps would be greatly appreciated.

Categories:

Autonomous agents

General topics

Publish & channel management

Hi @美木-30010535-0,

The pattern you're describing works in test, fails in published Teams, only for this specific agent, recreating with identical settings works fine points to the agent's Teams channel registration having gotten into a corrupt state. This isn't a configuration issue, it's a state issue with this specific agent instance's Teams deployment.

Quick Replies in Teams are sent as Adaptive Card Suggested Actions. When a user clicks one, Teams sends an Activity back to the bot. If the bot's registered endpoint or conversation state has become inconsistent, that Activity processing fails with "Something went wrong" even though test mode (which uses a different pipeline) works fine.

The confirmed fix for this specific scenario:

1. In Copilot Studio, go to Channels > Microsoft Teams
2. Remove the Teams channel from this agent entirely
3. Wait a couple of minutes
4. Re-add the Teams channel and republish
5. Uninstall and reinstall the Teams app for affected users (or re-push it via Teams Admin Center)

This resets the Teams channel registration for this specific agent and forces a fresh endpoint registration. Users will need to uninstall and reinstall because Teams caches the old channel endpoint.

If the issue persists after doing this, the next step is to check if there are any Power Automate flows connected to the Quick Reply topics that might be failing silently in Teams.

Test mode sometimes doesn't trigger flows identically to the published channel. Add a test step to those flows to confirm they complete successfully when triggered from Teams specifically.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube