Understand error codes
When a copilot encounters a problem during a conversation, it responds with a message that includes an error code for the specific problem that was encountered. Users of the copilot should give this error code to their administrator.
As a copilot maker, if a problem occurs when you are using the test pane to test your copilot, you can see a message with more context about the problem, in addition to the error code. Alternatively, you can use the Topic checker panel to validate your copilot.
Error list
Note
The term dialog used in some error messages refers to a topic.
Error code | Description |
---|---|
ContentError | There's an error in the topic content. |
DataLossPreventionViolation | There was a data loss prevention violation. |
FlowActionException | An error occurred while executing a cloud flow. |
FlowActionBadRequest | A request made to a cloud flow was malformed. |
FlowActionTimedOut | A cloud flow took more than 100 seconds to run and timed out. |
InvalidContent | Invalid content was added to the code editor. |
InfiniteLoopInBotContent | A node was executed too many times. |
LatestPublishedVersionNotFound | Unable to retrieve the published version of the copilot. |
RedirectToDisabledDialog | A topic is redirecting to a disabled topic. |
RedirectToNonExistentDialog | A topic is redirecting to another topic that no longer exists. |
SystemError | A system error occurred in Microsoft Copilot Studio. |
ContentError
Error message: This error produces dynamic messages based on the context of the error.
Resolution: This is a catch-all error for problems related to your copilot's content. Refer to the error message for more details.
Common problems include:
- A node is missing required properties.
- Invalid YAML was added with the code editor.
- A Power Fx formula contains an error.
DataLossPreventionViolation
Error message: "This environment requires users to sign in before they can use the copilot. Go to Manage > Security > Authentication and select the option to require users to sign in."
Resolution:
- Your environment's data loss prevention (DLP) policies require that users sign in. See Configure user authentication.
- One or more connectors that are used in the copilot aren't in the same data group. See Microsoft Copilot Studio connectors.
- One or more connectors that are used in the copilot are blocked by the tenant administrator.
FlowActionException
Error messages:
- "No output was received from flow {FlowName} ({FlowId}), even though output was expected as per the copilot definition."
- "The output parameter with name {ItemKey} on flow {FlowName} ({FlowId}) is missing from the response data. Refresh the flow, or ensure the flow returns this value."
- "The output parameter with name {ItemKey} on flow {FlowName} ({FlowId}) is missing from the output schema. Please refresh the flow."
Resolution: Check the flow for errors.
FlowActionBadRequest
Error messages:
- "The parameter with name {KeyName} on flow {FlowName} ({FlowId}) is declared to be of type {ItemTypeKind}. This type is not supported when invoking Power Automate. Currently, only Text, Boolean and Numbers are supported."
- "The parameter with name {ItemKey} on flow {FlowName} ({FlowId}) is missing in the 'Call Flow' action."
- "The parameter with name {KeyName} on flow {FlowName} ({FlowId}) evaluated to type {ResolveType}, expected type {ExpectedType}."
- "The flow {FlowName} ({FlowId}) failed to run with response code {ResponseCode}, error code: {FlowErrorCode}."
Resolution: Check that the base type of any variables you pass to the flow match the parameter's type.
FlowActionTimedOut
Error message: "The flow with id {FlowId} has timed out. Error Code: {FlowErrorCode}"
Resolution: Check the flow for errors to understand why the cloud flow took more than 100 seconds to run before it returned to your copilot. Try to optimize the query and the data you return from backend system. If some of the cloud flow logic can continue to run after a result is sent to the copilot, place these actions after the 'Return value(s) to Microsoft Copilot Studio' step in your cloud flow.
InvalidContent
Error message: "A total of {TotalComponents} component(s) exist in the copilot, but none are valid."
Resolution: Open the code editor to review issues with the content.
InfiniteLoopInBotContent
Error message: "Action {DialogId}.{TriggerId}.{ActionId} was executed more than {MaxTurnCount} times in a row. This indicates a cycle in execution of the dialog and hence dialog execution will be terminated."
Resolution: Make sure the topic ends properly and links to other topics that end properly, such as the Escalate system topic.
LatestPublishedVersionNotFound
Error message: "Unable to retrieve the latest published version of the copilot."
Resolution: Publish the copilot.
RedirectToDisabledDialog
Error message: "The Dialog with Id {DialogId} is disabled in the definition. Please enable the Dialog before using it."
Resolution: Re-enable the topic or remove the redirect node.
RedirectToNonExistentDialog
Error message: "The Dialog with Id {DialogId} was not found in the definition. Please check that the Dialog is present and that the Id is correct."
Resolution: Create a new topic to redirect to, or remove the redirect node.
SystemError
Error message: This error doesn't produce an error message.
Resolution: Contact customer support.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for