Limits and quotas
The numbers you can run into — Discord's, and Arclo's — collected in one place, with what each of them means for how you configure things.
Discord's limits
These are not Arclo's to change, and several of them explain a design decision elsewhere in this documentation.
| Limit | Value | What it means here |
|---|---|---|
| Global slash commands per application | 100 | Why systems group their operations under one command name |
| Message context commands | 5 | Report Message, Stick Message, Remind Me, Add Emojis |
| User context commands | 5 | Moderation History, Warn Member, Report Member |
| Subcommands per command | 25 | Why /voice has exactly 25 and a 26th would need a group |
| Bulk message deletion age | 14 days | Every purge and auto-purge cap follows from this |
| Timeout length | 28 days | Longer mutes are renewed automatically |
| Channel renames | 2 per 10 minutes, per channel | Why counters update on a five-minute floor |
| Pins per channel | 50 | A pinned board cannot be pinned in a full channel |
| Components in a modal | 5 | Why a long form is asked across several popups |
| Embed description / total | 4,096 / 6,000 characters | Long placeholders can overflow at send time |
| Buttons | 5 per row, 5 rows | Why a 20-option poll is exactly at the ceiling |
| Select menu options | 25 | Dropdown panels, forms, ticket types |
| Interaction reply editing | 15 minutes | Why a pager on an old command reply stops responding |
| Roles per server | 250 | Auto Roles and reward ladders sit well inside it |
Arclo's limits
Per-server quotas. Every figure below is read from the constant the product enforces, so this table cannot fall behind the code.
| Thing | Limit |
|---|---|
| Verification panels | 3 per server |
| Auto Roles: roles per list | 10 |
| Auto Roles: reserved rules | 100, up to 10 roles each |
| Auto Roles: join delay | 14 days |
| Temporary roles | 365 days |
| Sticky-role retention | 90 days by default, up to 365, or forever |
| Starboards | 3 per server, 10 milestone tiers each |
| Forms | 10 per server, 25 questions each |
| Custom commands | 10, with 10 actions, 5 variants and 5 buttons each |
| Automations | 5 rules per server, with a chain-depth guard |
| Ticket panels | 2 per server |
| Ticket panel automations | 5 per panel |
| Ticket forms | 5 per server, 5 questions each |
| Sticky messages | 10, across up to 25 channels each |
| Tags | 50 per server |
| Embed messages | 20, with 10 elements each |
| Alerts per platform per server | 2 |
| Alert filter rules | 10 per alert |
| Alert history | 30 days |
| Join Guard filters | 10 |
| Emoji creator slots | 7 parts |
| Poll options | 20, 10 polls running at once |
| Auto Purge: interval / maximum age | 7 days / 13 days |
Things Arclo will not do
- Delete messages older than two weeks in bulk. Discord refuses; deleting them one at a time is rate-limited in hours. They are counted and reported instead.
- Act on somebody above it in the role list. No permission changes that.
- Attribute a vanity URL join to a person. Discord reports the use, not an inviter.
- Change your server's command list the instant you save. Arclo rebuilds and re-registers it within about a minute of a change, and Discord takes a little longer to show it to everybody.
- DM somebody it does not share a server with. Which is why there is no goodbye DM.
Data retention
How long each category of data is kept is set out in §13 of the Privacy Policy, which is derived from the schema rather than written separately. In short: configuration lasts as long as Arclo is in your server, records last as long as the feature that produced them needs them, and everything except backups is deleted when Arclo is removed.
Still stuck? Ask in the support server — somebody there has almost certainly configured this before.