Reminders

Attach a schedule to a task so TTM pings its owner on time, every time.

A reminder turns a task into something that reminds you, instead of the other way round. You set it once; TTM handles the pings.

Adding a reminder

On the second button row, click Reminder until it turns blue (edit mode), then pick the task from the check selector. TTM opens the When form:

Everything arrives pre-filled with ten minutes from now, so a reminder for “in a moment” needs no typing at all — just submit. Submit and you’re done: the task shows the scheduled time and the reminder fires once.

The start must be at least 5 minutes in the future.

Repeating reminders

By default every reminder is a single event — one form, one ping, nothing else to decide. Repetitions are a Premium feature, like webhooks: on the Free plan every reminder is single (see What Premium unlocks; during the beta everything is unlocked). On a plan that includes them they are still an opt-in: a server manager enables Recurring reminders in Configuration.

With recurring reminders on, submitting When doesn’t save yet. TTM shows you a private summary card with the date it understood and four buttons:

With recurring reminders off — or on the Free plan — the card appears only when you edit a reminder that is already recurring, so it doesn’t lose its repetitions: Edit recurrence then lets you keep them or lower them, never go above the number it already has. A new reminder goes straight through When and is saved as a single event.

The repetition fields

How the reminder arrives

When the time comes, TTM reminds the task’s owner, with the task, the date it was due for and a button that jumps straight to the list. If the owner is a person, the reminder is a direct message. If the owner is a role, it is a message in the list’s channel that mentions the role, as a reply to the list: Discord notifies everyone who has that role and can see the channel. Either way it arrives within about ten seconds of the scheduled time — sends are spread out to stay within Discord’s limits — and always in the right minute. With Push notification off it still arrives, without the plain text that makes phone previews readable.

If the owner doesn’t accept direct messages from server members, or no longer shares a server with the bot, the DM can’t be delivered. 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 note.

A role is notified only if it can be mentioned: either the role allows it (Server Settings → Roles, the role can be @mentioned by anyone), or the bot has the Mention @everyone, @here and All Roles permission in the list’s channel — the invite link grants it. Otherwise the reminder still appears in the channel, but nobody gets a notification; TTM tells you when you set the reminder or make the role the owner. For a task owned by @everyone, only the permission counts. A role TTM creates for several owners is born mentionable, so its reminders notify it even without that permission — unless someone turns the setting off. Either way, only the members who can see the list’s channel are notified. If the role has been deleted, no reminder is sent at all: TTM tells you that too, and the fix is to choose another owner.

If the task had no owner yet, whoever sets the reminder becomes its owner — a reminder always has someone to reach. Set a different owner with the Owner button before or after creating the reminder.

Reading a reminder on the task

On the task line the reminder always shows the date of the first ping, rendered by Discord in each reader’s local time. A repeating reminder adds two compact values:

↻ interval · × repetitions

So ↻1h ×3 means: after the first ping it repeats every hour, three more times. A single event shows just the timestamp — there is no badge, because there is nothing to repeat.

In Bulk update the same reminder appears as a timestamp followed by a triplet:

- [] <t:1726497546> [2d3h,1h,3] Ship the release notes

The triplet is [distance,interval,repetitions]. The first value lets you create a reminder from text, without an absolute date: it is counted from the moment you save the list. A single event uses the sentinel interval 0m and 0 repetitions — [2d3h,0m,0].

The same rules apply as in the forms. Where recurring reminders can’t be created — on the Free plan, or with the toggle off — a triplet with repetitions above 0 is accepted only for a reminder the list already had: you can change its date, move it to another task or lower its repetitions, but not raise them. If several reminders break a rule, one message lists them all, one paragraph each — together with any other problem in the text, such as a list that’s too long or has too many tasks.

A reminder that could never arrive is taken out of the task’s text: one without an owner (reminders go to the owner — by DM to a person, as a mention in the channel to a role — and a mention without the colon is a tag, not an owner) or one whose alerts are all in the past. The list is saved anyway, and a message only you can see tells you which tasks lost their reminder, and why.

Finding your time zone

TTM needs an official time-zone name like Europe/Rome. Look yours up on the time zone map (opens in a new tab): select your area on the map, copy the value, and paste it into the field.

Editing or removing a reminder

• Edit — click Reminder to blue, pick the task, and set the new values. If the task already has a repeating reminder — or any reminder, with recurring reminders on — you land straight on the summary card, with the current date and badge, so you can change only what you need. Otherwise When opens, pre-filled with the current date.
• Remove — click Reminder until it turns red (delete mode), then pick the task. The reminder is removed.

Completing a task also stops its reminder — no need to clean up afterwards.

Closing a form is not cancelling

Discord never tells a bot that you closed a form with the ✕, so TTM cannot know: the list stays locked. Use Cancel on the summary card when it's there, and the unlock button if you closed a form the hard way.

Common errors