# Application limits and constraints

A reference for every cap that applies to application panels and submissions. For panel-wide caps shared with ticket panels, see [Panel limits](/docs/panels/panel-limits.md).

## Per application option

| Limit                         | Value                 | Notes                                                             |
| ----------------------------- | --------------------- | ----------------------------------------------------------------- |
| **Application Type** label    | 50 characters         | The form title members see.                                       |
| **Application Questions**     | 5                     | The same Discord limit as tickets, 5 per form.                    |
| **Granted Roles**             | Up to 20              | Roles added on approval. The bot's role must be above each one.   |
| **Roles to Remove**           | Up to 20              | Roles removed on approval. The bot's role must be above each one. |
| **Reviewer Roles**            | Up to 20              | Who can approve or deny.                                          |
| **Minimum Account Age**       | 0 to 365 days         | 0 turns it off.                                                   |
| **Minimum Server Membership** | 0 to 365 days         | 0 turns it off.                                                   |
| **Cooldown Period**           | 0 to 365 days         | Used only when Allow Reapplication is on.                         |
| **Decision reason**           | up to 1000 characters | Public. It can be DM'd to the applicant.                          |
| **Decision note**             | up to 1000 characters | Internal. It is never sent to the applicant.                      |

## Per submission

| Limit                                             | Value             | Notes                                                                                    |
| ------------------------------------------------- | ----------------- | ---------------------------------------------------------------------------------------- |
| Pending submissions per applicant per option      | 1                 | The member cannot submit again to the same option while a previous one is still pending. |
| Reapplication when Allow Reapplication is **off** | 0                 | After any decision, the member cannot apply again to that option.                        |
| Reapplication when Allow Reapplication is **on**  | Per cooldown days | The member must wait the cooldown after a decision.                                      |

## What happens when limits are hit

* **A sixth question in the editor.** The Add Question button is hidden, so you cannot add one.
* **A submission while a pending application exists.** The member sees a message that they already have a pending application.
* **Reapplication during the cooldown.** The member sees a message saying when they can apply again.
* **Account too young or server membership too short.** The member sees the block message with the required number of days.
* **A Granted Role above the bot's role.** The approval goes through, but the role is not granted. Move the bot's role above the Granted Role so it works.

## Discord-side limits

These come from Discord, not Ticket King:

| Limit                      | Value                                                                        |
| -------------------------- | ---------------------------------------------------------------------------- |
| Fields per pop-up form     | 5 (this sets the 5-question cap)                                             |
| Text input response length | up to 4000 characters. In Ticket King you set it from 1 to 4000, default 500 |

## Related

{% content-ref url="/pages/XQsrUSeSCzERWqbhESgi" %}
[Applications overview](/docs/applications/overview.md)
{% endcontent-ref %}

{% content-ref url="/pages/pbpPkSOpGXKKb0wl3JHx" %}
[Panel limits](/docs/panels/panel-limits.md)
{% endcontent-ref %}


---

# 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://ticketking.xyz/docs/applications/limits-and-constraints.md?ask=<question>
```

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.