Views:

Applies to Product - Power Apps

What’s happening?
An automation flow is failing with error code 429, indicating throttling when attempting to collect data from a source folder to a destination folder on a SharePoint site. Additionally, an application using SQL components is encountering a similar error when accessing the server through a gateway.
 

Reason:
The error is caused by throttling, which occurs when the number of requests exceeds the service’s allowed limit. This can happen due to:

  • High-frequency requests from flows or apps
  • Shared connectors (e.g., SharePoint or SQL) hitting service protection limits
  • Lack of appropriate licensing or plan limits being exceeded

 

Resolution:

  1. Automation Flow Throttling
    • This was resolved by assigning a license to the flow.
    • This suggests the flow was operating under limited capacity, and licensing helped increase the allowable request threshold.
    • Refer to the internal documentation in Throttling Overview for flow behavior under throttling and notification patterns 
 
  1. SQL Component Throttling
    • The SQL gateway error also returned a 429 status.
    • While specific resolution steps were not documented in the case, it is recommended to:
      • Review the connector’s throttling limits (e.g., SharePoint: 600 actions/minute per connection)
      • Use telemetry and Kusto queries to analyze request patterns and identify bottlenecks
      • Consider distributing load across multiple connections or reducing concurrency
  2. Best Practices and Monitoring
    • Use the Analytics tab in Power Automate to monitor flow usage and action counts
    • Review connector-specific throttling documentation to understand limits
    • Optimize flow design to reduce unnecessary actions or loops
    • Refer to Feb 2025_ SMR Report Out and ASP - Intent Determination - PPAC for DTP Pilot using Intent Assist for diagnostics and mitigation strategies 

Public Documentation and Guidance