Don't crash SharePoint Online with your PowerAutomate

With PowerAutomate you have enough power to crash an entire SharePoint Intranet / Workspace. This is comparable to a friendly fire or DOS attack from your own network. There are concepts and strategies to prevent this. Everyone should know them. This article gives an overview.

Throttling is a technique used by SharePoint Online to preserve the service's peak performance and dependability. To prevent resource misuse, throttling restricts the volume of API calls or actions within a given range.

SharePoint Online will refuse requests when your application is throttled and deliver an HTTP status code of 429 ("Too many requests") or 503 ("Server Too Busy"). In all situations, the response includes a Retry-After header that specifies how long the calling application should hold off on retrying or sending a new request.

Open in Microsoft

Using RateLimit headers to optimize the throttling behavior

SharePoint Online uses throttling to maintain optimal performance and reliability of the SharePoint Online service. Throttling limits the number of API calls or operations within a time window to prevent overuse of resources:

https://github.com/OneDrive/samples/tree/master/scenarios/throttling-ratelimit-handling