Copilot Studio Agent Publishes but Old Version Still Responds: Fix

You updated your agent in Copilot Studio, clicked Publish, and the confirmation appeared. But when you test the agent in Teams, Microsoft 365 Copilot, or a custom channel, it still uses the old version. The new topics, changed responses, or updated knowledge sources do not appear. This problem occurs because the published version is not immediately applied to all runtime environments. This article explains why the old version persists and provides the exact steps to force the new version to respond.

Why Copilot Studio Continues to Serve an Older Agent Version

When you publish an agent in Copilot Studio, the system creates a new version entry in the Microsoft Dataverse environment. However, the runtime endpoints that serve the agent to users do not automatically reload this version in all scenarios. The runtime caches the agent configuration for performance reasons. This cache can persist for several minutes or even longer if the channel uses aggressive caching. Additionally, certain channels such as Microsoft Teams and custom websites may cache the agent metadata at the client level. The result is that users see the old behavior even though the Copilot Studio interface shows the new version as Published. The root cause is a combination of server-side versioning delay and client-side caching.

Steps to Force the Latest Published Agent to Respond

Use the following steps in order. After each step, test the agent in the channel where the old version appears. Move to the next step only if the old version still responds.

1. Verify the published version number in Copilot Studio
   Open Copilot Studio. Go to Agents and select the agent that is not updating. In the top toolbar, click Settings then General. Look for Version. Note the version number displayed. Now go back to the agent overview page. The Publish button should show the current version and the date of the last publish. If the version shown is not the latest one you expected, click Publish again. Wait 30 seconds and refresh the page. Confirm that the version number matches your latest change.
2. Publish the agent a second time
   Even if the first publish appeared successful, a second publish can force the runtime to acknowledge the update. Click the Publish button in the top toolbar. In the Publish dialog, review the changes listed. Click Publish again. Wait 2 minutes. This double-publish technique often resolves cases where the initial publish did not fully propagate.
3. Clear the agent cache in Microsoft Teams
   If the agent is deployed to Microsoft Teams, the Teams client caches agent responses. Sign out of Teams completely. Close the Teams application. Clear the Teams cache by deleting the contents of the folder %appdata%\Microsoft\Teams on Windows. Do not delete the folder itself. Restart Teams and sign in again. Open a chat with the agent and send a test message. The agent should now respond with the latest version.
4. Use the Test agent pane in Copilot Studio to confirm the latest version
   In Copilot Studio, open the agent and click the Test button in the top-right corner. The test pane uses the latest published version directly from the Dataverse environment, bypassing most caches. Send a test message that triggers the changed topic or response. If the test pane shows the new behavior but the channel still shows the old one, the problem is definitely channel caching. If the test pane also shows old behavior, the publish did not apply correctly. In that case, go back to the agent, check for validation errors, and publish again.
5. Disable and re-enable the agent in the target channel
   For channels like Microsoft 365 Copilot or a custom website, remove the agent from the channel and add it again. In Copilot Studio, go to Channels. Select the channel where the old version appears. Click Remove or Disable. Confirm the removal. Wait 1 minute. Click Add channel and select the same channel again. Configure the channel settings as needed. This action forces the channel to fetch a fresh copy of the agent configuration.
6. Wait 15 minutes and test again
   Microsoft 365 Copilot and some custom channels have a server-side cache that expires after 10 to 15 minutes. If none of the above steps work, wait 15 minutes and test the agent again. During this time, the runtime should automatically pick up the latest published version. If the old version still responds after 15 minutes, contact Microsoft Support with the agent version numbers and the channel where the issue occurs.

If the Agent Still Uses the Old Version After All Steps

Copilot Studio shows a validation error after publish

If you see a red banner in Copilot Studio after publishing, the publish did not succeed. Common validation errors include missing trigger phrases in a topic, a broken Power Automate flow connection, or an unsupported connector. Open the agent and go to Topics. Look for any topic marked with a warning icon. Fix the validation issue by adding the required trigger phrases or reconnecting the flow. Publish again. The validation error must be resolved before the new version becomes active.

User sees old version in one channel but new version in another

This indicates that the channel with the old version has a persistent cache. For Microsoft Teams, clear the Teams cache as described in step 3. For a custom website, ask the user to clear their browser cache and cookies. For a mobile app, force close the app and reopen it. If the problem persists, the channel configuration may point to an older agent endpoint. Remove and re-add the channel as described in step 5.

Agent responds differently to different users

This can happen when the agent uses authentication and the user context changes the behavior. If you updated a topic that depends on user authentication, test the agent while signed in as a user who has the correct permissions. Also check if the agent has multiple versions deployed to different audiences. In Copilot Studio, go to Settings > Security > Authentication. Ensure that the authentication settings match the users who are seeing the old version.

Copilot Studio Publish vs Manual Version Refresh: Key Differences

Item	Publish Button	Manual Cache Refresh
Description	Creates a new version in Dataverse and marks it as active for the runtime	Clears client-side and channel caches to force the runtime to fetch the active version
When to use	After every change to topics, knowledge, or settings	When the published version does not appear in a specific channel
Effect on all channels	Makes the version available to all channels but does not immediately flush caches	Only affects the channel where the cache is cleared
Time to take effect	Up to 15 minutes for full propagation	Immediate after cache clear
Requires admin rights	Yes, the user must be an owner or contributor of the agent	No, any user can clear their local browser or app cache

You can now force your Copilot Studio agent to use the latest published version by combining a double-publish with channel-specific cache clearing. Start with the Test agent pane to confirm the version is correct at the server level. Then clear the cache in the channel where users are seeing the old version. If you frequently encounter this delay, consider adding a note to your change management process to wait 15 minutes after publishing before announcing the update to users.