Copilot Studio publishing and channel errors

Copilot Studio agents fail in two very different places: authoring/publishing (the agent won't build or won't take a new version live) and channel delivery (a published agent behaves correctly in the test pane but not on the channel end users actually reach). Diagnosing which half you're in narrows the fix considerably.

The agent publishes without error, but end users still see old behaviour

Symptom. A topic or knowledge-source change is saved and the agent is republished, but users on a live channel keep experiencing the previous behaviour.

Cause. Each channel connection (Teams, a custom website widget, a Dynamics 365-embedded agent) caches or independently activates the published agent version; a successful publish in the maker portal does not always propagate instantly to every connected channel.

Fix. Reconnect or refresh the specific channel (in Teams, this can mean the app needs to be reinstalled or the conversation restarted; for a website widget, a hard refresh of the embed script) rather than assuming a second publish in the maker portal will push it through.

Prevention. Treat "publish, then verify on the actual channel, not just the test pane" as the standard release step, since the test pane always reflects the latest authored version regardless of what channels have picked up.

A topic that should trigger on an obvious phrase never fires

Symptom. A topic with what looks like an appropriate trigger phrase is never selected, and the conversation either falls through to generative answers or to a fallback topic instead.

Cause. Trigger matching is a best-match process across every topic's phrases at once — a broader or more generic phrase on a different topic (or the generative-answers layer, when enabled, intercepting before topic matching completes) can consistently out-compete a narrower phrase that looks like it should have matched.

Fix. Test the exact phrase in isolation in the test pane with tracking enabled, which shows which topic (or the generative layer) actually claimed the message and why — broadening or adding more specific trigger phrases, or explicitly excluding the phrase from a competing generic topic, resolves most cases.

Prevention. Design trigger phrases from specific to general and review overlap across topics as new ones are added, rather than only reviewing a topic's own phrase list in isolation.

Knowledge-source answers stop reflecting a recently updated source document

Symptom. A knowledge source (a SharePoint site, an uploaded file, a public website) is updated, but the agent's generative answers keep citing the old content.

Cause. Knowledge sources are indexed on a schedule rather than read live on every conversation turn — a recent edit to the underlying document or site does not appear in agent answers until the next indexing pass completes.

Fix. Allow time for re-indexing (or trigger a manual re-sync where the knowledge source type supports one) before concluding the agent is ignoring the update, and confirm the exact document version the agent is citing via its response citations.

Prevention. Build in an expected delay between "content team updates a source document" and "agent answers reflect it" into any process that depends on this pipeline, rather than assuming near-real-time freshness.

A published agent doesn't appear (or appears with the wrong identity) in a Teams channel

Symptom. After publishing to Teams, the agent either doesn't show up for the intended users, or appears using an unexpected name, icon, or permission scope.

Cause. Teams channel publishing has its own approval and distribution step (through the Teams admin centre, for org-wide availability) separate from Copilot Studio's own publish action — a Copilot Studio publish makes the agent available to push to Teams, it does not by itself complete the Teams-side app approval and rollout.

Fix. Check the Teams admin centre's app management for the agent's approval and availability status, not just the Copilot Studio publish history, and confirm the intended audience (specific users, a team, or the whole org) was actually targeted in that step.

Prevention. Document the Teams-side rollout step as part of the release checklist for any agent that ships through Teams, since it is easy for a maker who only has Copilot Studio access to assume a publish there is the whole story.

Where to go next

Building the agent itself is covered in building agents with Copilot Studio; the boundary between Copilot Studio and the built-in app Copilots is in Copilot agents vs Copilot Studio; connecting an agent to outside systems is in integrating Copilot Studio agents with external APIs.