---
schema_version: "1"
id: 4f95bde8893d4d920a0218b7965fde6bfb26a1503f38ac5535762ebda57e3a31
title: Rate Limiting
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/policies/rate-limit-policy-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/policies/rate-limit-policy-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: ce2c7cf76f7c9730a1cca18fe43f22398a76807ba9942921974003bea65fa17c
description: MuleSoft Documentation Site
latest: true
---
# Rate Limiting

## [](#1-4-2)1.4.2

**October 1, 2026**

### What’s New

- This release updates policy metadata only. There’s no functional change.

## [](#1-4-0)1.4.0

**September 28, 2022**

### [](#new-features-and-enhancements)New Features and Enhancements

- The policy definition and policy implementation file are now separate. This enables stronger validations for policy configuration parameters.

## [](#1-3-7)1.3.7

**September 29, 2022**

### [](#minimum-mule-version)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues)Fixed issues

- Nodes no longer become unresponsive on a cluster scenario when persistence is enabled.

## [](#0-9-1)0.9.1

**June 27, 2022**

### [](#fixed-issues-2)Fixed Issues

- Rate limit window is no longer limited to 24 days.

## [](#0-9-0)0.9.0

**May 17, 2022**

### [](#new-features-and-enhancements-2)New Features and Enhancements

- Flex support for the Policy.

## [](#1-3-6)1.3.6

**April 1, 2022**

### [](#minimum-mule-version-2)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues-3)Fixed issues

- Quota is now reset when editing tier configuration.

## [](#1-3-5)1.3.5

**June 16, 2021**

### [](#minimum-mule-version-3)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-3)New Features and Enhancements

- Improved error handling for connectivity issues in clusters.
- Improved logging for errors.

## [](#1-3-4)1.3.4

**Apr 30, 2020**

### [](#minimum-mule-version-4)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-4)New Features and Enhancements

- Error handling responses revised for WSDL APIs to be compliant with SOAP 1.1 and 1.2.
- Performance improvements are introduced to the header manipulation engine.

### [](#fixed-issues-4)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).
- Improved resiliency on cluster scenarios.
- Improved logging information in locking, object store, and distributed mechanisms for better troubleshooting.
- Several performance improvements are introduced in the algorithm of the Rate Limiting policy.

## [](#1-3-3)1.3.3

**November 26, 2019**

### [](#minimum-mule-version-5)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues-5)Fixed Issues

- Improved the algorithm to allow executing with small `throttling.distribution_percentage` values
- Removed the warning message (WARN) in the application log when multiple asynchronous quota requests are executed in a distributed scenario
- Fixed the `NullPointerException` error on the persistence scheduler when a distributed quota is temporarily unavailable

## [](#1-3-2)1.3.2

**November 13, 2019**

### [](#minimum-mule-version-6)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues-6)Fixed Issues

- Improved resiliency when the throttling algorithm is created under heavy load in clustering scenarios
- Optimized the threading usage of the algorithm
- Fixed the `NullPointerException` error on the persistence scheduler when counters are persisted due to a sudden surge in requests

## [](#1-3-1)1.3.1

**July 12, 2019**

### [](#minimum-mule-version-7)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-5)New Features and Enhancements

- Several performance improvements were introduced in this release.

## [](#1-3-0)1.3.0

**April 26, 2018**

### [](#minimum-mule-version-8)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-6)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.

### [](#fixed-issues-7)Fixed Issues

- The persistence scheduler was losing quota in a Mule Cluster when the node’s clocks were out-of-sync. This error is now resolved.

## [](#1-2-3)1.2.3

**February 14, 2019**

### [](#minimum-mule-version-9)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues-8)Fixed Issues

- Fixed `NullPointerException` thrown when disposing policy in a Mule Cluster.

## [](#1-2-2)1.2.2

**October 17, 2018**

### [](#minimum-mule-version-10)Minimum Mule Version

**Mule 4.1.0**

### [](#fixed-issues-9)Fixed Issues

- Resolved the WSDL error response issue.
- An object store error occurred when hitting the API concurrently. This error is now resolved.
- Optimized throttling connector performance.
- An `ExpressionRuntimeException` error occurred when a WSDL proxy received an empty payload, or an invalid XML. This error is now resolved.

## [](#1-2-1)1.2.1

**June 25, 2018**

### [](#minimum-mule-version-11)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-7)New Features and Enhancements

- Added 'violationCategory' in the YAML configuration file for Feedback Loop.

### [](#fixed-issues-10)Fixed Issues

- If an extension set authentication using an Authentication object containing null properties, a `NullPointerException` error occurred. This error is now resolved.

## [](#1-2-0)1.2.0

**March 22, 2018**

### [](#minimum-mule-version-12)Minimum Mule Version

**Mule 4.1.0**

### [](#new-features-and-enhancements-8)New Features and Enhancements

- Parameterized throttling algorithm introduced for Mule 4.
- Migrated pluggable Hazelcast to 4.x.

### [](#fixed-issues-11)Fixed Issues

- The Rate Limiting policy was rejected from scheduler during high network traffic. This error is now resolved.

## [](#1-1-0)1.1.0

**January 25, 2018**

### [](#minimum-mule-version-13)Minimum Mule Version

**4.1.0**

### [](#new-features-and-enhancements-9)New Features and Enhancements

- Updated `WWW-Authenticate` header value from `mule-real` to `Client-ID-Enforcement`.
- Reduced error-handling verbosity in templates.

### [](#fixed-issues-12)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)1.0.0

**November 14, 2017**

### [](#minimum-mule-version-14)Minimum Mule Version

**4.0.0**

## [](#see-also)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)