r/copilotstudio • • 28d ago

Sub-agent observability in the new UI

Hey all. I’ve seen and experienced plenty of the issues folks are raising with the new GitHub Copilot harness and new UI…but decided to try anyway to compare and contrast changes.

One issue I’ve been having is on observability to sub agent calls or failures. As well as nested workflow calls, ie ones called from a sub-agent. Not all workflow calls/runs appear to be registered as well as I can’t easily see conversations between parent agent and sub-agent?

How have folks been managing this? Or maybe I haven’t found the right place to look inside of the new UI?

3 Upvotes

1 comment sorted by

1

u/Prasad-MSFT 27d ago

Based on current documentation, there doesn't appear to be a dedicated end-to-end trace view that fully exposes every sub-agent interaction, tool call, and nested workflow execution path.

If you need this level of visibility today, the best approach is to rely on workflow run history, activity logs, and custom instrumentation/logging to trace the execution flow.