In Flexera One Automation, users may encounter HTTP 429 errors ("Too Many Requests") when running or scheduling policies, especially in environments with a large number of policies or frequent execution schedules. This error indicates that the rate limit for API requests has been exceeded, which can disrupt policy execution and reporting.

This article explains the common causes of 429 errors in Flexera One Automation, how to identify which rate limit is being hit, and provides actionable steps to resolve and prevent these errors.

What is a 429 error?

A 429 error is returned by the Flexera API when the number of requests exceeds the allowed rate limit. Flexera enforces rate limits at various levels, such as organization, service account, user, or client IP. For example, the organization's rate limit is typically 1000 requests per minute.

Common causes

• High number of scheduled policies: Organizations with thousands of policies, especially those scheduled to run every 15 minutes or hourly, are more likely to hit rate limits.
• Frequent execution of meta policies: Meta parent policies running at short intervals can quickly consume the available request quota.
• Not using service accounts: Requests made without a service account may be subject to stricter organization-level rate limits.

Determine which rate limit is being exceeded

1. Review error logs: Look for messages like 429 Too Many Requests in policy execution logs.
2. Check policy schedules: Audit how many policies are scheduled and their frequency (for example, every 15 minutes, hourly, daily).
3. Determine rate limit type: Refer to Rate Limiting to understand which limit (organization, user, service account, or client IP) applies to your scenario.