Skip to content

Commit d62e20a

Browse files
Update error codes documentation with new entries
Added new error codes and their descriptions to the documentation.
1 parent 03bc52b commit d62e20a

1 file changed

Lines changed: 213 additions & 0 deletions

File tree

support/power-platform/copilot-studio/authoring/error-codes.md

Lines changed: 213 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,19 @@ As an agent maker, if a problem occurs when you use the test pane to [test your
2424
2525
| Error code | Description |
2626
| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
27+
| [AIModelActionBadRequest](#aimodelactionbadrequest] | There was a mimatch between the prompt action types. |
2728
| [AIModelActionRequestTimeout](#aimodelactionrequesttimeout) | There was a timeout error that's related to a call to an AI Builder model. |
2829
| [AsyncResponsePayloadTooLarge](#asyncresponsepayloadtoolarge) | There was an error that's related to the output of a connector. |
30+
| [AuthenticationNotConfigured](#authenticationnotconfigured) | Authentication is required but wasn't configured. |
31+
| [ConnectedAgentAuthMismatch](#connectedagentauthmismatch) | There's an authentication mismatch between the orchestrator and sub-agent. |
32+
| [ConnectedAgentBotNotFound](#connectedagentbotnotfound) | A sub-agent in a multi-agent orchestration configuration wasn't found. |
33+
| [ConnectedAgentBotNotPublished](#connectedagentbotnotpublished) | A sub-agent in a multi-agent orchestration configuration wasn't published. |
34+
| [ConnectedAgentChainingNotSupported](#connectedagentchainingnotsupported) | Multi-level agent chaining isn't supported. |
35+
| [ConnectedAgentGptComponentNotFound](#connectedagentgptcomponentnotfound) | A connected agent is missing descriptions or instructions. |
36+
| [ConnectorPowerFxError](#connectorpowerfxerror) | There was an error in the Power Fx expression evaluation in connector actions.|
2937
| [ContentError](#contenterror) | There was an error in the topic content. |
3038
| [ConsentNotProvidedByUser](#consentnotprovidedbyuser) | A user interacting with an agent rejected the agent's SSO request. |
39+
| [ConversationStateTooLarge](#conversationstatetoolarge) | The conversation state exceeds the size limits. |
3140
| [DataLossPreventionViolation](#datalosspreventionviolation) | There was a data policy violation. |
3241
| [EnforcementMessageC2](#enforcementmessagec2) | Not enough prepaid capacity was available. |
3342
| [FlowActionBadRequest](#flowactionbadrequest) | A request that was made to an [agent flow][1] was malformed. |
@@ -55,6 +64,30 @@ As an agent maker, if a problem occurs when you use the test pane to [test your
5564
[1]: /microsoft-copilot-studio/advanced-flow
5665
[2]: /microsoft-copilot-studio/authoring-topic-management#redirect-to-another-topic
5766

67+
#### AIModelActionBadRequest
68+
69+
**Error messages:**
70+
71+
- The output of the prompt evaluated to '{ActualType}' but expected '{ExpectedType}'.
72+
73+
- The input parameter '{ParameterName}' for prompt '{PromptName}' is missing.
74+
75+
- The input parameter '{ParameterName}' for prompt '{PromptName}' is blank but is required.
76+
77+
- Expected: {ExpectedType}. Actual: {ActualType}.
78+
79+
**Resolution:** This error occurs when a prompt action receives incorrect input or returns unexpected output types.
80+
81+
**Common causes and fixes:**
82+
83+
- **Type mismatch:** The prompt's output type doesn't match what's expected. Check your prompt configuration to ensure the output schema matches the expected variable type.
84+
85+
- **Missing required input:** A required input parameter wasn't provided. Verify that all required inputs are connected to variables with values.
86+
87+
- **Blank required value:** A required input was provided but its value is blank. Ensure the variable has a value before calling the prompt.
88+
89+
For more information, see [Create a prompt action](/microsoft-copilot-studio/advanced-create-prompt-action).
90+
5891
#### AIModelActionRequestTimeout
5992

6093
**Error message**: The prompt `prompt-name` execution timed out.
@@ -67,6 +100,162 @@ As an agent maker, if a problem occurs when you use the test pane to [test your
67100

68101
**Resolution**: One of the agent's real-time connectors is returning a payload that's larger than the agent can handle. For more information about the payload limit, see [Copilot Studio web app limits](/microsoft-copilot-studio/requirements-quotas#copilot-studio-web-app-limits).
69102

103+
#### AuthenticationNotConfigured
104+
105+
**Error messages:**
106+
107+
- Authentication is not configured for this bot.
108+
109+
- The bot requires sign in, but is not configured for authentication. Please update the authentication method for the bot.
110+
111+
- Integrated authentication is not supported in channel `{channel}`.
112+
113+
**Resolution:** This error occurs when your agent uses actions or features that require user authentication, but authentication hasn't been configured.
114+
115+
**To resolve:**
116+
117+
1. In your agent, go to **Settings > Security > Authentication**.
118+
119+
1. Select one of the appropriate authentication methods:
120+
121+
- **Authenticate with Microsoft** for Microsoft 365 users
122+
123+
- **Authenticate manually** for custom OAuth providers
124+
125+
1. If the error mentions a specific channel, verify that the channel supports the authentication method you're using. Some channels don't support integrated authentication.
126+
127+
For more information, see [Configure user authentication](/microsoft-copilot-studio/configuration-end-user-authentication).
128+
129+
#### ConnectedAgentAuthMismatch
130+
131+
**Error message:** Your connected agent with schema name `{AgentSchemaName}` has an authentication mismatch with the main agent.
132+
133+
**Resolution:** The orchestrator agent and connected sub-agent have different authentication configurations. For multi-agent orchestration to work, both agents must use compatible authentication settings.
134+
135+
**To resolve:**
136+
137+
1. Open both agents and go to **Settings > Security > Authentication**.
138+
139+
1. Ensure both agents use the same authentication method (for example, both use **Authenticate with Microsoft**).
140+
141+
1. If using manual authentication, ensure both agents are configured with the same OAuth provider and settings.
142+
143+
**Important:** The following authentication compatibility rules apply:
144+
145+
- If the connected agent has _no authentication_ configured, any orchestrator authentication is acceptable.
146+
147+
- If the connected agent _requires authentication_, the orchestrator must use the _same_ authentication method.
148+
149+
- **Manual authentication (Generic OAuth2)** on the orchestrator is _not compatible_ with connected agents that require authentication. Both agents must use the same manual authentication configuration or the connected agent must have no authentication requirement.
150+
151+
**Common scenarios that cause this error:**
152+
153+
- Orchestrator uses **Authenticate with Microsoft** but the connected agent uses manual OAuth
154+
155+
- Orchestrator uses manual OAuth but connected agent uses **Authenticate with Microsoft**
156+
157+
- Connected agent requires authentication but orchestrator has no authentication configured
158+
159+
For more information, see [Configure user authentication](/microsoft-copilot-studio/configuration-end-user-authentication) and [Use agents as actions in other agents (preview)](/microsoft-copilot-studio/advanced-use-dispatcher).
160+
161+
#### ConnectedAgentBotNotFound
162+
163+
**Error message:** Connected agent with schema name {AgentSchemaName} not found.
164+
165+
**Resolution:** This error occurs in multi-agent orchestration when the orchestrator agent can't find a connected sub-agent.
166+
167+
**To resolve:**
168+
169+
1. Verify the connected agent exists in the same environment as the orchestrator agent.
170+
171+
1. Ensure the connected agent's schema name is spelled correctly in the orchestrator configuration.
172+
173+
1. Check that you have access permissions to the connected agent.
174+
175+
1. If the connected agent was recently created, wait a few minutes and try again.
176+
177+
For more information, see [Use agents as actions in other agents (preview)](/microsoft-copilot-studio/advanced-use-dispatcher).
178+
179+
#### ConnectedAgentBotNotPublished
180+
181+
**Error message:** Connected agent with schema name {AgentSchemaName} needs to be published to be invoked.
182+
183+
**Resolution:** The connected sub-agent must be published before it can be invoked by the orchestrator agent.
184+
185+
**To resolve:**
186+
187+
1. Open the connected agent in Copilot Studio.
188+
189+
1. Publish the agent.
190+
191+
1. Return to the orchestrator agent and test again.
192+
193+
For more information, see [Use agents as actions in other agents (preview)](/microsoft-copilot-studio/advanced-use-dispatcher).
194+
195+
#### ConnectedAgentChainingNotSupported
196+
197+
**Error message:** Agent chaining detected. Your agent cannot be connected to agent with schema name `{AgentSchemaName}` as it already has a connected agent.
198+
199+
**Resolution:** Multi-level agent chaining isn't supported. An orchestrator agent can connect to sub-agents, but those sub-agents can't have their own connected agents.
200+
201+
**To resolve:**
202+
203+
1. Review your agent architecture and flatten the hierarchy.
204+
205+
1. Move the functionality from deeply nested agents into either the orchestrator or first-level connected agents.
206+
207+
1. Consider using topics or actions instead of additional connected agents.
208+
209+
For more information, see [Use agents as actions in other agents (preview)](/microsoft-copilot-studio/advanced-use-dispatcher).
210+
211+
#### ConnectedAgentGptComponentNotFound
212+
213+
**Error message:** No GPT component found for connected agent with schema name `{AgentSchemaName}`.
214+
215+
**Resolution:** The connected agent is missing required description or instructions that enable it to be invoked by an orchestrator agent.
216+
217+
**To resolve:**
218+
219+
1. Open the connected agent in Copilot Studio.
220+
221+
1. Go to the agent's **Overview** page.
222+
223+
1. Ensure the agent has a clear **Description** and **Instructions** configured.
224+
225+
1. Publish the connected agent after making changes.
226+
227+
1. Return to the orchestrator agent and test again.
228+
229+
For more information, see [Use agents as actions in other agents (preview)](/microsoft-copilot-studio/advanced-use-dispatcher).
230+
231+
#### ConnectorPowerFxError
232+
233+
**Error message:** Power Fx expression evaluation failed: {ErrorDetails}
234+
235+
**Resolution:** A Power Fx expression used in a connector action failed to evaluate correctly.
236+
237+
**Common causes and fixes:**
238+
239+
- **Syntax error:** Check your Power Fx expression for typos or incorrect syntax.
240+
241+
- **Type mismatch:** Ensure the data types in your expression are compatible (for example, don't compare text to numbers without conversion).
242+
243+
- **Null or blank values:** Add error handling for cases where variables might be blank. Use functions like `IsBlank()`, `Coalesce()`, or `IfError()`.
244+
245+
- **Invalid function usage:** Verify that functions are used with the correct number and type of arguments.
246+
247+
**To resolve:**
248+
249+
1. Open the topic containing the connector action.
250+
251+
1. Review the Power Fx expressions in the action's input parameters.
252+
253+
1. Test the expressions with sample data to identify the issue.
254+
255+
1. Use the formula bar's error indicators to locate specific problems.
256+
257+
For more information, see [Use Power Fx in Copilot Studio](/microsoft-copilot-studio/advanced-power-fx).
258+
70259
#### ContentError
71260

72261
**Error message**: This error produces dynamic messages based on the context of the error.
@@ -95,6 +284,30 @@ Common problems include:
95284
- One or more connectors that you use in the agent aren't in the same data group. See [Copilot Studio connectors](/microsoft-copilot-studio/admin-data-loss-prevention#copilot-studio-connectors-and-data-groups).
96285
- One or more connectors that you use in the agent were blocked by the tenant administrator.
97286

287+
#### ConversationStateTooLarge
288+
289+
**Error message:** Conversation state size exceeds the maximum allowed limit.
290+
291+
**Resolution:** The conversation has accumulated too much data in its state, exceeding the allowed size limits.
292+
293+
**To resolve:**
294+
295+
1. **Reduce variable data:** Review your topics and reduce the amount of data stored in variables during the conversation.
296+
297+
1. **Clear unused variables:** Set variables to blank when they're no longer needed.
298+
299+
1. **Simplify conversation flows:** Break complex conversations into smaller, more focused interactions.
300+
301+
1. **Avoid storing large objects:** Don't store large JSON objects, arrays, or text blocks in conversation variables.
302+
303+
**Prevention tips:**
304+
305+
- Use variables only for data that needs to persist across topics.
306+
307+
- Consider using Power Automate flows to store and retrieve large data from external sources instead of keeping it in conversation state.
308+
309+
For more information, see [Copilot Studio quotas and limits](https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-quotas).
310+
98311
#### EnforcementMessageC2
99312

100313
**Error message**: This agent is currently unavailable. It has reached its usage limit. Please try again later.

0 commit comments

Comments
 (0)