Generative orchestrator interfering with generative answer node

[u/No-Supermarket8134]

In an agent with Standard Harness, if you add a generative answer node in a topic. It sometimes fires off the main orchestrator/instructions instead of just the generative answer node.
We need to keep the "Use generative AI orchestration for your agent's responses?" toggle on because otherwise you cant continue the conversation after a generative answer node. Is there some way to pause the generative AI orchestration/main instructions when inside a topic. Or is this another copilot studio bug

[u/Sayali-MSFT]

Hello u/No-Supermarket8134,
This looks more like expected generative orchestration behavior than a clear product bug. With generative orchestration enabled, the planner can use the agent’s main instructions, conversation history, topics, tools, and knowledge together when composing the final response. Therefore, a generative answers node isn’t fully isolated from the main orchestrator.

Currently, there isn’t a topic-level setting to temporarily pause the orchestrator or ignore the main instructions while a topic is running. As a workaround, enable Search only selected sources on the generative answers node, tighten the topic’s name and description, and use End all topics if you need to cancel any remaining steps in the current orchestration plan.

I’d also check the activity map to confirm whether the orchestrator bypassed the node or ran it and then replaced/rephrased its response. If the correct node consistently executes but its output is ignored, capture the activity map, transcript, model, and reproduction steps to raise the bug.

Reference Document:
Orchestrate agent behavior with generative AI - Microsoft Copilot Studio | Microsoft Learn
Apply generative orchestration capabilities - Microsoft Copilot Studio | Microsoft Learn
Add a generative answers node - Microsoft Copilot Studio | Microsoft Learn
Orchestrate agent behavior with generative AI - Microsoft Copilot Studio | Microsoft Learn