Error codes: Power Virtual Agents

Select the version of Power Virtual Agents you're using here:

• Power Virtual Agents web app
• Power Virtual Agents app in Microsoft Teams

When a bot encounters a problem during a conversation, it will respond with an error message.

If you're a bot user, the error message will contain an error code for the specific problem that was encountered.

If you're a bot maker testing the bot in the Test bot pane, you'll see an additional message that gives more context about the problem.

Errors may also appear in the Topic Checker where you can easily locate and fix them.

Note

The following errors can occur in both the web app and Microsoft Teams. To view errors that are exclusive to Teams, please refer to the Teams version of this topic.

Prerequisites

• Learn more about what you can do with Power Virtual Agents.

Error List

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 bots. To configure a new environment, see Working with 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 Power Virtual Agents."	To use this bot, publish it in Power Virtual Agents.
2010	"We can’t retrieve your bot content."	Content couldn't be found because it was deleted. To configure a new bot, see Create and delete bots. To configure a new environment, see Working with 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 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 Add actions using Power Automate.
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 Power Virtual Agents.
2019	"We couldn’t find your environment. It may have been deleted."	Your environment was deleted. To configure a new environment, see Working with 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.
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-enabled 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.
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.