Understand error codes

Стаття
04/03/2024

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 Add user authentication with the Sign in system topic.
One or more connectors that are used in the copilot aren't in the same data group. See 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.

Error	Bot response	Resolution
2000	"The user is trapped in an infinite loop. Check to make sure `{Topic Name}` reaches a logical conclusion."	Make sure the topic ends properly, or links to other topics that end properly, such as the Escalate system topic.
2001	"The bot content is invalid."	Check the topic for errors.
2002	"We ran into an issue with CDS."	There was a problem accessing the Dataverse. Check your configuration for errors. Otherwise try again later as there may be a service issue.
2003	"There's a problem with `{Flow Name}` in `{Topic Name}`. Please check your content."	Check the flow for errors and look for failed runs in the flow run history.
2004	"There's a problem with `{Skill Name}` in `{Topic Name}`. Please check your content."	There was a problem with your skill. Check both the skill and topic for errors.
2005	"We ran into a problem. Please check your content."	There was a problem with your Power Automate Flow template. Check the flow for errors.
2006	"We couldn't find your bot."	Your bot couldn't be found because the bot, or its environment, was deleted. To configure a new bot, see Create and delete copilots. To configure a new environment, see Work with Power Platform environments.
2007	"The bot contains too much content to be able to work."	Reduce message lengths or number of topics, then try again. Read more about content limits.
2008	"We couldn't find the user's token."	Check your bot's authorization configuration for errors.
2009	"To use this bot, publish it in Microsoft Copilot Studio."	To use this bot, publish it in Microsoft Copilot Studio.
2010	"We can't retrieve your bot content."	Content couldn't be found because it was deleted. To configure a new copilot, see Create and delete copilots. To configure a new environment, see Work with Power Platform environments.
2011	"We couldn't find `{Skill Name}` in `{Topic Name}`. Please check your content."	Skill couldn't be found because it was deleted. To create a new skill, see Configure a Bot Framework skill.
2012	"We couldn't find `{Flow Name}` in `{Topic Name}`. Please check your content."	Your Power Automate Flow couldn't be found because it was deleted. To create a new flow, see Create a flow.
2014	"The translation service did not respond."	Try again later. If the issue persists, contact customer support.
2015	"You're not authorized to call `{Skill Name}`. Please check the skill and its usage for any issues."	Check your skill's configuration and ensure your bot is added to the skill's allowlist.
2016	"Sorry, we couldn't find your bot."	There was a problem with a Azure Bot Service channel. The channel may have been deleted or configured incorrectly.
2017	"Sorry, we couldn't access your bot."	The Azure Bot Service channel couldn't be accessed. Check the channel configuration for authentication issues.
2018	"The user is typing too fast."	You sent messages too quickly. Read more about quotas and limits within Microsoft Copilot Studio.
2019	"We couldn't find your environment. It may have been deleted."	Your environment was deleted. To configure a new environment, see Work with Power Platform environments.
2020	"Something happened, and `{Flow Name}` isn't working in `{Topic Name}`. Try again later. If the issue persists, check your flow's setup and run history."	Your Power Automate flow isn't working. Try again later. If the issue persists, check the flow for errors.
2021	"Number of dialogs executed in the current turn exceeded the maximum of `{Dialog Limit}`."	By default, the maximum number of topics is 50. Reduce the number of topics, then try again.
2022	"The bot sent more than `{Message Limit}` messages in this turn."	Limit messages per turn to under 30.
2023	"We ran into a problem executing your composer dialog."	Check the Composer dialog for errors.
2024	"This environment requires users to sign in before they can use the bot. Go to Manage > Security > Authentication and select the option to require users to sign in."	Your environment's data loss prevention (DLP) policies requires that user's sign in. To learn how to require users to sign in, see Configure user authentication.
2025	"There are one or more empty nodes in topic `{Topic Name}`, Please check your content."	Add content to empty nodes or remove them from the topic.
2025	"`{Topic Name}` is redirecting to a topic, which has been turned off. Return to `{Topic Name}` and check your content."	Your topic is redirecting to another topic that has been turned off. Re-enable the topic or remove the redirect node.
2025	"The topic you're trying to redirect to no longer exists. Return to `{Topic Name}` and check your content."	The topic you're trying to redirect to no longer exists. Create a new topic to redirect to or remove the redirect node.
2026	"There was a problem with the Power Automate Flow. Please check your content."	Check the flow for errors.
2030	"Check Power Automate flow run history and ensure that flow ran successfully."
2101	"The user's conversation with the bot was too long or the user's message was too long."	Try restarting the conversation with the bot or using a shorter message.
2102	"The user sent a message which is too large to process."	You sent a message that is too large to process. Shorten your message, then try again.
3000	"Unexpected error"	A system error occurred. Contact customer support for more details.
3001	"Power Automate isn't available for your flow `{Flow Name}` now. Try again later."	Power Automate isn't responding. Restart the conversation with your bot and try again. If the issue persists, contact customer support.
3002	"Something happened in Power Automate, and your request to your flow `{Flow Name}` wasn't accepted. Try again later."	An error occurred in Power Automate and the request to your flow wasn't accepted. Your flow might have taken more than 2 minutes to respond.
3003	"There's a network problem connecting to your flow `{Flow Name}`. Please try again later."	Try again later. If the issue persists, contact customer support.

Поділитися через