Agent Credit Limits and Alerts - Copilot Studio

The agent limit and the capacity used by its flows need to be checked separately. Microsoft documents that an agent's monthly limit does not stop the agent flows it calls, and that the limit is not enforced instantly.

For this incident, I would first separate agent interactions from Agent flow actions in the consumption report. Then check the configured limit, Stop usage setting, notification time and last successful invocation in a controlled test. Billing timestamps and execution timestamps should remain distinct: a delayed accounting update does not mean that execution continued until that moment.

This should help identify whether the spike came from delayed reporting, delayed enforcement or flows governed by a different capacity boundary. The dashboard refresh cadence alone cannot establish the alert-delivery interval.

Microsoft documentation: https://learn.microsoft.com/en-us/power-platform/admin/manage-copilot-studio-copilot-credits-capacity