Known limits
The ceilings on lists, tasks, reminders and more — most come from Discord itself, and how to work within them.
Team Tasks Manager works entirely inside Discord, so most of the limits below aren’t TTM’s choice — they come from Discord itself: how long a message can be, how many menus fit in one message, how far back messages can be deleted in bulk. Where a limit is Discord’s, we say so.
Lists and tasks
| Limit | Value | Why |
|---|---|---|
| Characters per list | 4000 | The whole list is edited inside a single Discord field, and Discord caps that field at 4000 characters. This counts everything shown — task text, checkboxes, any reminder time and one line break per row — not just what you type. TTM keeps a small safety margin below the hard limit. |
| Items per list | 50 (tasks + subtasks) | Discord allows 5 component rows per message and up to 25 options per dropdown. TTM reserves rows for the action buttons, which leaves room for 50 selectable items in total — subtasks included. Your plan can stop lower: see What Premium unlocks. |
| List title | 256 characters | The create, edit and clone windows don’t let you type more. |
| Imported file | .txt, up to 64 KB | /create-list imports only the file made by Download. A file that isn’t .txt, or is bigger, is refused before TTM even downloads it. |
Download always gives you a file. A normal Discord message is capped at 2000 characters, so Download, in the 
More panel, never posts the list as text: it sends a .txt file to you alone, in a message only you can see. It’s the same file /create-list can import back.
Deleting the message is not the same as deleting the list. A list lives in its message, but its data — tasks, owners, tags and above all reminders — lives in TTM. If you delete the message by hand, the list disappears from the channel while its reminders keep arriving, pointing at a message that is no longer there.
Three ways out, all under your control:
- Delete list, inside the More panel of the list itself: the ordinary way, which takes the reminders with it. Needs Manage messages on the channel.
- Seal list, in the same panel, when you’d rather keep the message as a record: the list stays in the channel as it is, without buttons, with a Sealed list line at the bottom. Its data leaves TTM, its reminders stop and it frees its place on your plan. Needs Manage messages too.
/config lists, when the message is already gone: it shows every list of the server and lets you delete the leftovers — or regenerate the list, if the message was deleted by mistake. It can seal lists too, but only while their message still exists: with the message gone there is no record to leave, so use Delete.
TTM does not detect the deletion of a message on its own: doing so would mean asking Discord about every list, every time, and guessing from silence is exactly how data gets destroyed by accident. The panel shows you what exists and leaves the decision to you.
Sealing is final. A sealed list has no buttons, so it can no longer be edited, reopened or downloaded, and it isn’t in /config lists any more, because it’s no longer in TTM. If you may want to reuse it, download it before sealing.
Reminders
| Limit | Value | Why |
|---|---|---|
| Repetitions per reminder | up to 50 on Premium, none on Free | Recurring reminders are a Premium feature: on the Free plan every reminder is a single event. On Premium a reminder can repeat at most 50 times after the first one (51 pings in total); set repetitions to 0 for a one-time reminder. |
| How soon a reminder can fire | 5 minutes from now | The start date must be at least five minutes in the future, so the scheduler has time to pick it up. |
| How punctual a reminder is | within about 10 seconds | Reminders due together are spread over up to ten seconds, to stay within Discord’s rate limits. The reminder still arrives within the right minute. |
Repetitions are offered only on a plan that includes recurring reminders, and only when Recurring reminders is enabled in Configuration; by default every reminder is a single event. Recurring reminders created before — during the beta, for example — keep firing either way, and stay editable: you can move them or lower their repetitions, but not raise them. See Reminders for how repetitions and intervals work.
A person’s reminders arrive by direct message, so they depend on the owner’s DM settings. If the owner doesn’t accept direct messages from server members, or no longer shares a server with the bot, Discord refuses the message and that reminder doesn’t arrive. TTM remembers it and doesn’t try that person again for 6 hours; after that it tries again, and the first DM that gets through clears the pause.
Roles TTM creates count toward Discord’s 250 roles per server. When several people own a task, TTM creates a role for them; at 250 roles it can’t, and says so. It deletes the role when no list uses it any more and it’s still as TTM left it — see The roles TTM creates.
TTM sees how many members a role has, not who they are. Swap one member of a role TTM created for another and it can’t tell: the owner menu keeps showing the people TTM gave the role to.
A role’s reminder notifies only a role that can be mentioned. When a task’s owner is a role, the reminder is a message in the list’s channel that mentions it. Discord turns that into a notification only if the role can be mentioned by anyone, or the bot has Mention @everyone, @here and All Roles in the channel; otherwise the message appears and nobody is notified. TTM warns you when you set up such a reminder. And only the members who can see the channel are notified — which, for a task on that list, is who you’d expect.
Owners and tags
Each task has one owner — a person or a role; on Premium also up to 25 people, who share a role TTM creates for them (25 is the owner menu’s maximum). A task can carry up to 25 tags (users or roles to notify): 25 is Discord’s per-menu maximum for the tag picker.
Webhooks
| Limit | Value |
|---|---|
| Webhooks per server | 25 on Premium, none on the Free plan — the picker is a Discord dropdown, and 25 options is its maximum, so that is also the cap |
| Webhook name | up to 96 characters * |
| Webhook URL | up to 2000 characters |
* Discord’s own cap is 100, but the name travels inside the form field’s identifier together with a short marker, and those characters count too: TTM checks 96 and says so if you go over. The error message quotes the same number you read here.
The activity timeline
When the timeline is on, TTM posts each action into a thread next to the list, through a Discord webhook. Discord allows 15 webhooks per channel, so TTM creates one webhook per channel and reuses it for every list in that channel — the name and picture you see on each message are set per message, so nothing changes visually.
If a channel has already reached Discord’s 15 (because of other bots or integrations), the timeline for a new list can’t start. Free one up in Channel settings → Integrations → Webhooks.
Notifications
When TTM tidies up its own notification messages, Discord only allows bulk-deleting messages from the last 14 days. Older notifications may stay in the channel — you can remove them manually.
These numbers reflect the current version of the bot. Anything that changes will be noted in the Release notes.