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.

On this page

Discord's limits

These are not Arclo's to change, and several of them explain a design decision elsewhere in this documentation.

LimitValueWhat it means here
Slash commands per server100Shared with your Custom Commands, and why systems group their operations under one command name
Message context commands5Report Message, Stick Message, Remind Me, Add Emojis
User context commands5Moderation History, Warn Member, Report Member
Subcommands per command25/voice uses 25 of them
Bulk message deletion age14 daysEvery purge and auto-purge cap follows from this
Timeout length28 daysLonger mutes are renewed automatically
Channel renames2 per 10 minutes, per channelWhy counters update on a 5-minute floor
Pins per channel250A pinned board cannot be pinned in a full channel
Components in a modal5Why a long form is asked across several popups
Embed description / total4,096 / 6,000 charactersLong placeholders can overflow at send time
Buttons5 per row, 5 rowsWhy a poll stops at 20 options: four rows of choices and one of controls
Select menu options25Dropdown panels, forms, ticket types
Interaction token15 minutesHow long Arclo has to finish a command and edit its reply
Roles per server250Auto 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.

ThingLimit
Verification panels3 per server
Auto Roles: roles per list10
Auto Roles: reserved rules100, up to 10 roles each
Auto Roles: join delay14 days
Temporary roles365 days
Sticky-role retention90 days by default, up to 365, or forever
Reaction role menus10 per server, 15 roles each
Level rewards20, up to 3 roles each
Achievements100 per server, 8 tiers each
Starboards3 per server, 10 milestone tiers each
Giveaways10 active (drafts and running) and 5 scheduled at once, up to 100 winners each; the newest 50 ended ones are kept
Suggestion boards3 per server
Statistics channels10 counters, 5 social counters and 5 goals
Temporary voice hubs3 per server
Backups5 saved per server and 10 chat logs
Forms10 per server, 25 questions each
Custom commands10, with 10 actions, 5 variants and 5 buttons each. Each one also takes one of the server's 100 slash-command slots
Reminders50 per server; members' own, made with the command, 3 each by default and up to 50
Automations5 rules per server, with a chain-depth guard
Ticket panels2 per server
Ticket panel automations5 per panel
Ticket forms5 per server, 5 questions each
Sticky messages10, across up to 25 channels each
Tags50 per server
Embed messages20, with 10 elements each
Alerts per platform per server2
Alert filter rules10 per alert
Alert history30 days
Join Guard filters10
Emoji creator7 part slots
Emoji archive300 per server
Image storage25 MB and 100 images per server
Your cards10 designs per card, per member
Poll options20, 10 polls running at once
Auto Purge: interval / maximum age7 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 kind of data is kept is set out in §13 of the Privacy Policy. In short: configuration and records last as long as Arclo is in your server. Removing Arclo marks the server for deletion, and 14 days later everything tied to it is deleted for good; inviting Arclo back within those 14 days restores it exactly as it was. Backups, chat logs and published templates belong to the person who made them, so they outlive Arclo's removal until their owner deletes them.

Still stuck? Ask in the support server: somebody there has almost certainly configured this before.