Hi all,
I have been facing few issues with copilot studio agents and require some assistance.
Two recurring issues in a generative-orchestration agent (with connected agents). Grateful for any guidance.
=====================================================
ISSUE 1 — Action.Submit throws TopicNotFound
=====================================================
Setup: A custom topic (intent is empty, triggered by description) shows a single AdaptiveCardPrompt with Submit/Cancel buttons, then branches on the result.
Card action pattern (simplified):
"actions": [
{ "type": "Action.Submit", "title": "Submit", "data": { "action": "submit" } },
{ "type": "Action.Submit", "title": "Cancel", "associatedInputs": "none", "data": { "action": "cancel" } }
]
The submit value is bound to a Topic variable (Topic.action), then a ConditionGroup branches:
- condition: Topic.action = "submit" -> run submit steps
- condition: Topic.action = "cancel" -> run cancel steps
Problem: The card renders fine, but clicking Submit or Cancel returns:
"The Topic with Id cr665_<env>.topic.<MyTopic> was not found in the definition. Error code: TopicNotFound."
What I've verified:
- The topic exists and Topic checker is green (no errors).
- No duplicate topics in the solution; the topic has a unique, non-system name.
- The agent was published successfully.
- Other agents with multi-input / multi-card topics work fine.
- Single card vs two cards makes no difference — it is specifically the Action.Submit round-trip that cannot resolve the topic.
Questions:
1. Why would an Action.Submit callback fail with TopicNotFound when the topic clearly triggers and renders the card?
2. Is this a publish/runtime sync issue (draft vs published definition)?
3. Is there a known fix for adaptive-card button submits in generative-orchestration agents?
=====================================================
ISSUE 2 — Intermittent SystemError on brand-new chats
=====================================================
I also frequently get this, even on a fresh conversation with a short first message (not a long thread):
"Sorry, something went wrong. Error code: SystemError. Conversation ID: ... Time (UTC): ..."
Details:
- It happens intermittently — the same input often works on retry.
- It occurs on new/short chats, so it is not a context/token-limit issue (that would only appear in long conversations).
- No custom topic is involved — it can fail on a simple greeting or first query.
- The agent uses generative orchestration with connected agents.
Questions:
1. What causes an intermittent SystemError on the very first turn of a new conversation?
2. Could it be the selected model (orchestration/tool-calling capability), the connected-agent hops, or a transient backend issue?
3. How can I diagnose the underlying error beyond the generic SystemError, and what reduces its frequency?
Happy to share activity traces and more examples for both. Thanks!
