Pattern
Publish ritual
Changes that seem not to arrive in a published channel because publishing propagates asynchronously and channels cache old agent versions.
Last reviewed 8 July 2026
The pattern
After every publish, run a fixed ritual before you judge whether a change arrived. Republish, start a new session, clear the client cache, re-add the app, and wait. Publishing propagates asynchronously across regions, and each channel caches its own copy of your agent. Never conclude "the fix didn't work" until you have ruled out propagation.
When to use it
- After every publish, before you retest in a channel.
- Whenever behavior differs between the test pane and a published channel.
- Before you revert a change or open a support case for "publish is broken".
Steps
- Publish the agent again in Copilot Studio ("Publish").
- Start a completely new chat session in the channel.
- Type "start over" to reset the conversation state.
- Sign out of the client, for example Teams.
- Sign back in.
- Remove the agent app from the client.
- Re-add the agent from the app catalog, not from a pinned entry.
- Wait; propagation can exceed the documented 30 minutes.
- Retest with a question whose answer changed in the new version.