Overview
When customers attempt to export their Auth0 configuration using the Auth0 Deploy CLI, they may observe a global rate limit exceeded (429) error in the logs. Despite this error, the export process completes successfully.
Applies To
- Auth0 Deploy CLI
Cause
The Auth0 Deploy CLI sends a burst of requests to retrieve the configuration data, which can trigger the global rate limit error.
Solution
Understanding Rate Limits
- Auth0 applies different rate limits for production and non-production environments.
- The global rate limit error is the expected behavior when exporting configurations.
Why Customers Should Not Worry
- The latest version of the Auth0 Deploy CLI includes a built-in retry mechanism that handles these errors automatically.
- Even if the error appears in logs, the CLI will retry failed requests and ensure a successful export.
Customers can optimize their export by:
- Using the include_only option – Export only specific configurations instead of the entire tenant.
- Using the exclude option – Skip unnecessary configurations to reduce the number of API requests.