While deploying through Copilot Studio, the cache is still being stored in Teams, which is unexpected.

Question

While deploying through Copilot Studio, the cache is still being stored in Teams, which is unexpected.

Deepak Kumar Rath 0

I am building a bot from Copilot Studio and i have deployed in Teams channel .. Everytime when i ask a question its not taking the results from Power Automate it takes from the Cache memory of teams and gives me the response. I tried many ways to remove the cache but still its not going
Steps i tried are:

1 Uninstall and reinstall the app in my teams channel

2 I have used Clear variables and there i have used Conversation history for the current session
3 I have also used /debug clearstate

Nothing is working.. Am i missing anything can you suggest me alternate ways to remove cache from Teams

Nivedipa-MSFT 4,246 Reputation points Microsoft External Staff Moderator

2026-03-27T10:30:30.5066667+00:00

Hello Deepak Kumar Rath,
This isn't related to a Teams cache issue — Copilot Studio's generative answers are being sent before your Power Automate flow is triggered.

Solution: Set up a dedicated topic with a clear "Call an action" node that links to your flow, rather than depending on generative orchestration. Make sure this topic is prioritized above the generative fallback.

To check: Review the Power Automate Run History. If the flow isn't running, the topic may not be firing. You can also use Activity Trace in the test pane for confirmation.

1 answer

Your answer

Nivedipa-MSFT 4,246 Reputation points Microsoft External Staff Moderator

2026-03-27T10:30:30.5066667+00:00

Hello Deepak Kumar Rath,
This isn't related to a Teams cache issue — Copilot Studio's generative answers are being sent before your Power Automate flow is triggered.

Solution: Set up a dedicated topic with a clear "Call an action" node that links to your flow, rather than depending on generative orchestration. Make sure this topic is prioritized above the generative fallback.

To check: Review the Power Automate Run History. If the flow isn't running, the topic may not be firing. You can also use Activity Trace in the test pane for confirmation.

Answer 1

Hi @Deepak Kumar Rath

Thank you for posting your question in the Microsoft Q&A forum.

This behavior is expected when a Copilot Studio agent runs in Microsoft Teams. The confusion usually comes from calling it Teams cache, when in reality it’s persistent conversation state and version caching.

Could you please confirm whether you’ve followed the steps outlined in Best Practices for Deploying Copilot Studio Agents in Microsoft Teams | The Custom Engine?

The /debug clearstate command resets only the runtime state and is mainly intended for test chat scenarios. In Microsoft Teams, conversations remain persistent. Reinstalling the app or using debug commands does not reset the conversation or trigger ConversationStart. The article explains this behavior and recommends implementing explicit session lifecycle management.

I also found a similar discussion where users confirmed that following these steps worked for their scenario, please refer to Solved: Agent Not Reflecting Updates In MS Teams.

I hope this helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Teddie-D 16,130 Reputation points Microsoft External Staff Moderator

2026-03-25T23:52:47.9833333+00:00

Hi @Deepak Kumar Rath
May I know if you have got any chance to check my answer? If you need further assistance, please feel free to let me know. Thank you!

Share via

While deploying through Copilot Studio, the cache is still being stored in Teams, which is unexpected.

1 answer

Your answer