Skip to content

Commit c6e4f8f

Browse files
Merge pull request #10086 from MicrosoftDocs/main
Auto Publish – main to live - 2025-10-30 18:00 UTC
2 parents 4d31f55 + cfc65c9 commit c6e4f8f

File tree

9 files changed

+150
-71
lines changed

9 files changed

+150
-71
lines changed

.openpublishing.redirection.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13909,6 +13909,10 @@
1390913909
{
1391013910
"source_path": "support/sql/database-engine/install/windows/update-or-slipstream-installation.md",
1391113911
"redirect_url": "/sql/database-engine/install-windows/install-sql-server-using-slipstream"
13912+
},
13913+
{
13914+
"source_path": "support/dynamics-365/commerce/payments/adyen-support.md",
13915+
"redirect_url": "/dynamics365/commerce/dev-itpro/payments-retail#what-is-the-service-level-agreement-sla-for-out-of-box-payment-connectors-like-adyen"
1391213916
}
1391313917
]
1391413918
}

support/azure/azure-kubernetes/error-codes/aks-error-code-page.md

Lines changed: 111 additions & 0 deletions
Large diffs are not rendered by default.

support/azure/azure-kubernetes/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -261,8 +261,10 @@ items:
261261
href: extensions/changes-in-kubernetes-event-driven-autoscaling-add-on-214-215.md
262262
- name: Troubleshoot KEDA add-on
263263
href: extensions/troubleshoot-kubernetes-event-driven-autoscaling-add-on.md
264-
- name: Troubleshoot error codes
264+
- name: Troubleshoot by error codes
265265
items:
266+
- name: Common error codes
267+
href: error-codes/aks-error-code-page.md
266268
- name: 429 Too Many Requests errors
267269
href: create-upgrade-delete/429-too-many-requests-errors.md
268270
- name: A-K

support/azure/azure-kubernetes/welcome-azure-kubernetes.yml

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -182,11 +182,10 @@ landingContent:
182182
url: ./identify-memory-saturation-aks.md
183183

184184
# Card
185-
- title: Troubleshoot common issues
185+
- title: Troubleshoot AKS error codes
186186
linkLists:
187187
- linkListType: how-to-guide
188188
links:
189-
- text: Troubleshoot common issues with Azure Linux container hosts on AKS
190-
url: ./troubleshoot-common-azure-linux-aks.md
191-
- text: Troubleshoot DNS resolution problems on AKS clusters
192-
url: connectivity/dns/basic-troubleshooting-dns-resolution-problems.md
189+
- text: AKS error codes
190+
url: ./error-codes/aks-error-code-page.md
191+

support/dynamics-365/commerce/payments/adyen-support.md

Lines changed: 0 additions & 39 deletions
This file was deleted.

support/dynamics-365/commerce/payments/refund-declined.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ The payment authorization details include the following error message:
2525
2626
## Resolution
2727

28-
To solve this issue, contact the Adyen support team and request to enable blind returns on your Adyen merchant account. For more information, see [Troubleshoot issues with Dynamics 365 Payment Connector for Adyen](adyen-support.md).
28+
To solve this issue, contact the Adyen support team and request to enable blind returns on your Adyen merchant account. For more information, see [What is the Service level agreement (SLA) for out-of-box payment connectors like Adyen?](/dynamics365/commerce/dev-itpro/payments-retail#what-is-the-service-level-agreement-sla-for-out-of-box-payment-connectors-like-adyen)
2929

3030
## More information
3131

support/dynamics-365/commerce/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,6 @@
6262
href: payments/refund-declined.md
6363
- name: Save for my next payment option doesn't appear
6464
href: payments/next-payment-link-not-appearing.md
65-
- name: Troubleshoot Dynamics 365 Payment Connector for Adyen issues
66-
href: payments/adyen-support.md
6765
- name: Point of sale (POS)
6866
items:
6967
- name: Store Commerce app (POS) is suddenly deactivated

support/dynamics-365/commerce/welcome-commerce.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,7 @@ landingContent:
9494
- text: Refund on a return order is declined
9595
url: payments/refund-declined.md
9696
- text: Save for my next payment option doesn't appear
97-
url: payments/next-payment-link-not-appearing.md
98-
- text: Troubleshoot Dynamics 365 Payment Connector for Adyen issues
99-
url: payments/adyen-support.md
97+
url: payments/next-payment-link-not-appearing.md
10098

10199
# Card
102100
- title: Point of sale (POS)
Lines changed: 26 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Resolve throttling errors in agents
3-
description: Learn how to identify and resolve throttling errors in Microsoft Copilot Studio agents, including error codes, causes, and solutions.
2+
title: Resolve usage limit and agent unavailable errors in Copilot Studio agents
3+
description: Learn how to identify and resolve usage limit errors that occur due to quotas and limits in Microsoft Copilot Studio agents.
44
ms.date: 09/09/2025
55
ms.reviewer:
66
- camogas
@@ -9,38 +9,44 @@ ms.reviewer:
99
ms.custom: sap:Licensing\Quotas and limits
1010
---
1111

12-
# Resolve throttling errors in agents
12+
# Resolve usage limit errors in agents
1313

14-
This article describes the causes of throttling errors and how to overcome them when interacting with Copilot Studio agents.
14+
This article describes common throttling errors you might encounter when using Copilot Studio agents. It explains the underlying causes, which typically stem from capacity limitations or licensing constraints, and outlines solutions for resolving these issues.
1515

1616
## Symptoms
1717

18-
Users might receive the following error messages when interacting with a Copilot Studio agent:
18+
You might receive one or more of the following error messages when interacting with an agent:
1919

20-
- **GenAISearchandSummarizeRateLimitReached**: "The usage limit for search and summarize has been reached. Please try again later."
21-
22-
- **GenAIToolPlannerRateLimitReached**: "The usage limit for generative orchestration has been reached. Please try again later."
23-
24-
- **OpenAIRateLimitReached**: "Your agent reached the maximum number of generative answers responses."
20+
- **EnforcementMessage:** "This agent is currently unavailable. It has reached its usage limit. Please try again later."
21+
- **GenAISearchandSummarizeRateLimitReached:** "The usage limit for search and summarize has been reached. Please try again later."
22+
- **GenAIToolPlannerRateLimitReached:** "The usage limit for generative orchestration has been reached. Please try again later."
23+
- **OpenAIRateLimitReached:** "Your agent reached the maximum number of generative answers responses."
2524

2625
## Cause
2726

28-
Copilot Studio has default constraints applied to agents that limit how often messages can be sent to the agent. These constraints exist primarily to protect against unexpected usage surges that otherwise might impact the functionality of the application.
27+
Copilot Studio enforces default rate and usage constraints to protect against unexpected usage surges that might affect the functionality of the application. Agent usage is measured in Copilot credits. The number of credits an agent consumes depends on the design and features of the agent. When consumption exceeds available capacity in an environment, the environment is in overage. Once overage enforcement is triggered, you see the message, "This agent is currently unavailable. It has reached its usage limit. Please try again later." For more information on credits and overage enforcement, see [Overage enforcement](/microsoft-copilot-studio/requirements-messages-management#overage-enforcement).
2928

30-
For messages generated with the usage of generative AI and for topic orchestration, quotas limit how many requests can be sent per hour and minute per Dataverse environment. Once the limit is reached, a message is sent to the user interacting with the agent when they try to send a new message.
29+
For messages generated with the usage of generative AI and for topic orchestration, quotas limit the number of requests that you can send per minute and per hour. Once you reach the limit, subsequent agent messages are blocked, resulting in one of the listed symptoms. These quotas and limits apply per Dataverse environment. For more information, see [Quotas and limits for Copilot Studio](/microsoft-copilot-studio/requirements-quotas).
3130

3231
## Solution
3332

34-
If you see these error messages due to reaching the agent rate limit, review your licensing model to determine how many extra capacity packs you should acquire to cover your consumption quota, or if you should change to a pay-as-you-go model. For more information about quotas and tenant billing capacity, see [Quotas and limits](/microsoft-copilot-studio/requirements-quotas#generative-ai-messages-to-an-agent).
33+
### Confirm the licensing and capacity model
3534

36-
### Increase the rate limit
37-
38-
Another option is to contact Microsoft Support and request a rate limit increase. However, this option doesn't guarantee that an exception or increase is granted. Each request is subject to review and approval based on eligibility and current licensing. Requests are only assessed if the environment has pay-as-you-go for Copilot Studio. Environments operating solely on message-based functionality aren't eligible for consideration.
35+
Review the [Copilot Studio quotas and limits](/microsoft-copilot-studio/requirements-quotas) for the plan you're using, and compare it against your recent usage. To view consumption in the Power Platform admin center, see [View Copilot Credit consumption](/microsoft-copilot-studio/requirements-messages-management#view-copilot-credit-consumption).
3936

40-
## Related information
37+
If you reach the limits, an administrator can either:
4138

42-
For further information on rate limits and consumption of generative answers for Copilot Studio agents, review the following documentation:
39+
- [Purchase additional capacity packs to cover your consumption quota](/power-platform/admin/manage-copilot-studio-messages-capacity)
40+
- Switch to [pay as you go billing plan](/microsoft-copilot-studio/billing-licensing#copilot-studio-pay-as-you-go)
41+
> [!NOTE]
42+
> Currently, only production and sandbox environments support pay-as-you-go.
4343
44-
- [Quotas and limits](/microsoft-copilot-studio/requirements-quotas#generative-ai-messages-to-an-agent)
44+
### Request a rate-limit increase
4545

46-
- [Generative AI messages to an agent](/microsoft-copilot-studio/requirements-quotas#generative-ai-messages-to-an-agent)
46+
[Contact Microsoft Support](/microsoft-copilot-studio/fundamentals-support#microsoft-support) and request a rate-limit increase. This option doesn't guarantee that an exception or increase is granted. Each request is subject to review and approval based on eligibility and current licensing. Only pay-as-you-go environments are eligible; environments operating solely on message-based functionality aren't eligible for consideration.
47+
48+
## Related information
49+
50+
- [Copilot Studio licensing](/microsoft-copilot-studio/billing-licensing)
51+
- [Quotas and limits](/microsoft-copilot-studio/requirements-quotas#generative-ai-messages-to-an-agent)
52+
- [Understand agent error codes](~/power-platform/copilot-studio/authoring/error-codes.md)

0 commit comments

Comments
 (0)