# Rate Limiting
If messages, such as push notifications, are sent too rapidly, a sudden surge of traffic on the client’s server can occur, potentially leading to service outages. FlareLane's Rate Limiting feature provides an optimized speed control feature to prevent such situations and ensure smooth message delivery.
## Configuring Rate Limiting
Image by FlareLane
Dispatch speed control can be configured on a per-project basis. Within the FlareLane console, you can choose between two options on the project page:
1. **No limit**: No restrictions are applied to the notification dispatch speed.
2. **Set the speed limit for sending messages**: You can specify the number of messages to be sent per minute.
## How It Works In Practice
The configured messages per minute are converted to messages per second for more stable dispatching. For example, if 1,019 messages are set to be sent per minute, it is converted to 16 messages per second by rounding down to the nearest whole number. The conversion method is as follows:
```
(1019 ÷ 60) = 16.98333333...
```
In practice, FlareLane sends 16 messages per second, totaling 960 messages per minute.
```
16 x 60 = 960
```
In summary, messages are sent per second at a steady rate, allowing clients to maximize the use of their server resources.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://guide.flarelane.com/engagement-tools/rate-limiting.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.