> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/webforms/konfiguracja/limit-wnioskow-dlawik.md).

# Request limit (throttling)

{% hint style="info" %}
Availability of functionality depends on the license and may not be available in all deployments.
{% endhint %}

## Limit of active request instances

Limit of active request instances (so-called *throttle*) allows you to limit the number of simultaneously running requests of a given type on **a specific server**. After the limit is exceeded, the user cannot start another instance – instead, an information page is displayed.

This solution is especially useful in situations of increased system load or during maintenance work.

## Configuration

The configuration of limits is done in the file:

```
/etc/eximee/webforms.xml
```

{% hint style="info" %}
Changes in the file are applied without the need to restart the Tomcat server.
{% endhint %}

Sample configuration in the .xml file:

```js
<webforms>
    <server> 
        <limits>
            <forms>
                <_uwmappertest>3</_uwmappertest>
                <_demo_porownywarka_ofert>3</_demo_porownywarka_ofert>
            </forms>
        </limits>
    </server>
</webforms>
```

In the tag `<forms>` we define the requests covered by the limit:

```
<_FORMNAME>LIMIT</_FORMNAME>
```

Where:

* `FORMNAME` – request name,
* `LIMIT` – maximum number of active instances.

**Important rules:**

* each request name `FORMNAME` must have the \_ prefix
* no entry means **no limit**,
* setting the value to 0 means complete **blocking of the request**.

### Configuration examples

**Complete blocking of the request**

```
<_przykladowy_wniosek>0</_przykladowy_wniosek>
```

After opening the request, the user will see a page informing them that it is unavailable.

**Limiting the number of instances**

```
<_przykladowy_wniosek>2</_przykladowy_wniosek>
```

A third attempt to start the request will result in an error page being displayed.

## Information page

The text on the information page can be set from **Eximee Designer**, in the **Library → Content** and by searching for formatted content **error\_page\_formLimitExceeded**.

You also need to update the file **webforms-error-pages.xml** by adding the fragment below:

```xml
<code_formLimitExceeded>
    <content>error_page_formLimitExceeded-*</content>
</code_formLimitExceeded>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/webforms/konfiguracja/limit-wnioskow-dlawik.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.