--- schema_version: "1" id: f841aed7419984c14c1d2bb43eafcdbfcb15e089eebec42589c7d6ade6ff1128 title: Rate Limiting - SLA-based collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/policies/rate-limit-sla-release-notes.md canonical_url: https://docs.mulesoft.com/release-notes/policies/rate-limit-sla-release-notes source_site: docs.mulesoft.com content_type: documentation content_hash: 1f86ab52d55e6953138adc946a8141c8b0d7f96d031f95777c8abc4dc0c61af6 description: MuleSoft Documentation Site latest: true --- --- product: Release Notes version: master keywords: mule, rate-limit, policy, release notes --- # Rate Limiting - SLA-based > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ## 1.3.2 **October 1, 2026** ### What’s New - This release updates policy metadata only. There’s no functional change. ## 1.3.0 **September 28, 2022** ### New Features and Enhancements - The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters. ## 1.2.9 **September 29, 2022** ### Minimum Mule Version **Mule 4.1.0** ### Fixed issues - Nodes no longer become unresponsive on a cluster scenario when persistence is enabled. ## 0.9.0 **May 17, 2022** ### New Features and Enhancements - Flex support for the Policy. ## 1.2.8 **June 16, 2021** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Improved error handling for connectivity issues in clusters. - Improved logging for errors. - Corrected spelling issues and typos in policy’s code snippets. ## 1.2.7 **January 06, 2021** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Added OAS 3.0 code snippet in the policy YAML file. ## 1.2.6 **Apr 30, 2020** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Error handling responses revised for WSDL APIs to be compilant with SOAP 1.1 and 1.2. - Performance improvements are introduced to the header manipulation engine. ### Fixed issues - After a policy was applied, HTTP headers did not follow the RFC 2616 requirement of case-sensitivity: [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). ## 1.2.5 **March 13, 2020** ### Minimum Mule Version **Mule 4.1.0** ### Fixed issues - Improved logging information in locking, object store, and distributed mechanisms for better troubleshooting. - Added client name in the authentication attributes for the request to an API that has the Rate Limiting policy applied. - When request quota exceeds, authentication objects are now made accessible to the protected resource in the authentication store. - Several performance improvements were introduced in the algorithm of the Rate Limiting policy. ## 1.2.4 **November 26, 2019** ### Minimum Mule Version **Mule 4.1.0** ### Fixed issues - Improved algorithm to allow executing with small `throttling.distribution_percentage` values. - Removed the warning (WARN) message in application log when multiple async quota requests are executed in a distributed scenario. - Fixed the `NullPointerException` error on persistence scheduler when distributed quota is temporarily unavailable. ## 1.2.3 **November 13, 2019** ### Minimum Mule Version **Mule 4.1.0** ### Fixed issues - Improved resiliency when throttling algorithm is created under heavy load in clustering scenarios. - Optimized the threading usage of the algorithm. - Fixed the `NullPointerException` error on persistence scheduler when counters are persisted due to a sudden surge in requests. ## 1.2.2 **July 12, 2019** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Several performance improvements were introduced in this release. ### Fixed Issues - The persistence scheduler was losing quota in a Mule Cluster when the node’s clocks were out-of-sync. This error is not resolved. ## 1.2.1 **April 30, 2019** ### Minimum Mule Version **Mule 4.1.0** ### Fixed Issues - An error occurred when multiple client applications using one rate limiting algorithm were configured with the same SLA in Anypoint Platform. This error is now resolved. ## 1.2.0 **April 26, 2019** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Unless explicitly configured, by checking the "Expose headers" option, the policy header will not be propagated or returned. The default configuration is modified to support this behaviour. - Several performance improvements were introduced in this release. ## 1.1.3 **February 14, 2019** ### Minimum Mule Version **Mule 4.1.0** ### Fixed Issues - Fixed `NullPointerException` thrown when disposing policy in a Mule Cluster. ## 1.1.2 **January 10, 2019** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Improved the RAML and OAS snippets. ## 1.1.1 **June 25, 2018** ### Minimum Mule Version **Mule 4.1.0** ### New Features and Enhancements - Migrated pluggable Hazelcast to 4.x. ### Fixed Issues - The Rate Limiting policy was rejected from scheduler during high network traffic. This error is now resolved. - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. - If an extension set authentication using an Authentication object containing null properties, a `NullPointerException` error occurred. This error is now resolved. ## 1.1.0 **January 25, 2018** ### Minimum Mule Version **4.1.0** ### New Features and Enhancements - Changed `WWW-Authenticate` header value from `mule-real` to `Client-ID-Enforcement`. - Reduced error-handling verbosity in templates. ### Fixed Issues - An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved. ## 1.0.0 **November 14, 2017** ### Minimum Mule Version **4.0.0** ## See Also - [Rate Limit for Mule 4](https://docs.mulesoft.com/gateway/latest/policies-included-rate-limiting) - [Known Issues](https://help.salesforce.com/s/issues)