Weekly Tasks Limit in Co-Pilot

Copilot task throttling is driven by enforced quotas and usage limits that protect the service from overload and from unexpected consumption. When those limits are exceeded, Copilot enters a throttled state and blocks further requests until the quota window resets or additional capacity is available.

In Copilot Studio, this behavior appears as errors such as:

• GenAISearchandSummarizeRateLimitReached – search and summarize quota reached.
• GenAIToolPlannerRateLimitReached – generative orchestration quota reached.
• OpenAIRateLimitReached – maximum number of generative answers reached.

These limits are applied per Dataverse environment and are tied to licensing and capacity. If the environment is in overage or consistently hitting rate limits, the agent or copilot can remain unavailable until the quota period resets or capacity is increased.

When throttling does not clear automatically (for example, messages like “come back Friday” but the state remains blocked), the supported remediation paths are:

1. Align capacity and licensing with usage
   • Check the current licensing model and available capacity/credits for the environment.
   • If usage regularly exceeds the default allocation, add extra capacity packs or move to a pay‑as‑you‑go model so that the quota matches actual usage. For Copilot Studio agents, this is the primary way to avoid repeated rate‑limit enforcement and stuck “usage limit” states.
2. Request a rate‑limit increase (where supported)
   • For Copilot Studio agents, a rate‑limit increase can be requested through Microsoft Support.
   • Requests are only evaluated for environments that use pay‑as‑you‑go for Copilot Studio; environments that rely solely on message‑based allocations are not eligible.
   • Approval is not guaranteed; each request is reviewed based on eligibility and licensing.
3. Open a support ticket for backend investigation/reset
   • Local or client‑side actions (such as resetting apps, clearing caches, or signing out/in) cannot reset backend throttling or quota state.
   • To address a stuck throttled state or to request a manual backend reset, a support case must be opened with Microsoft Support via the appropriate admin portal.
   • In the ticket, include:
     • That the Copilot account or agent is stuck in a throttled state.
     • The exact error messages (including any “come back Friday” or similar text) and approximate times.
     • Confirmation that local resets and standard troubleshooting have already been attempted.
   • Support can access backend data, verify whether quotas and overage enforcement are behaving correctly, and escalate to engineering if a manual reset or configuration correction is required.

If throttling recurs repeatedly, the underlying cause is typically sustained usage that exceeds the configured quota for the environment. Without additional capacity or a rate‑limit adjustment, the throttled state will continue to reappear even after each reset window.

References:

• Resolve usage limit errors in agents
• Resolve throttling errors in agents