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: one that isn’t ticked yet. TTM opens the When form, titled Set reminder for task …:

Everything arrives pre-filled with ten minutes from now, so a reminder for “in a moment” needs no typing at all. Submit it, and the task shows the scheduled time. The reminder fires once. With recurring reminders on, a summary card follows: press Save (see Repeating reminders).

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

Who gets it. The reminder goes to the task’s owner, by direct message if the owner is a person. If the task has no owner yet, you become it. From then on only you, and whoever has Manage messages on the channel, can tick that task. To give it to someone else, set the owner with Owner before or after creating the reminder. Owners, and what they can do: see Owners and tags. Nothing arrived? The owner must accept direct messages from members of that server: see Reminders by direct message.

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.

How the reminder arrives

When the time comes, TTM reminds the task’s owner. The reminder shows 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, and always in the right minute. TTM spreads the sends out to stay within Discord’s limits. With Push notification off it still arrives, without the plain text that makes phone previews readable.

A direct message can be refused, and then TTM waits some hours before it tries that person again: see Reminders by direct message.

Don’t want reminders by direct message?

You decide, from Discord’s own settings:

• Keep them, without a ping. Right-click your conversation with TTM and choose Mute. The reminders still arrive, silently.
• Stop them. Click the server name, then Privacy Settings, and turn off Direct Messages. This stops direct messages from every member of that server, not only TTM.
• Hand the task over. Ask whoever manages the list to give the task to someone else, with Owner .

Muting the server is not enough: it silences the server’s channels, not your direct messages.

A role is notified only if it can be mentioned. When that is the case, and what happens with @everyone or a deleted role: see Reminders to a role.

Editing or removing a reminder

• Edit — click Reminder to blue, pick the task, and set the new values. You land straight on the summary card if the task already has a repeating reminder. With recurring reminders on, you land there for any reminder (see Repeating reminders). The card shows the current date and badge (Reading a reminder on the task), so you can change only what you need. Save stays off until you change the date or the recurrence. Otherwise When opens, pre-filled with the current date. Submitting the same date and recurrence the reminder already has changes nothing: TTM tells you, and sends no notification.
• 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. If you closed a form the hard way, open More under the list and press Unlock list.

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, a Recurrence line and four buttons. The line says none for a single reminder, or shows the recurrence badge:

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

The repetition fields

The form has three menus, so there is nothing to type and no format to get wrong.

The menus always offer the values the reminder already has, even when they aren’t in the list: a reminder set in Bulk update can run 37 times, or every 48 hours. One that already runs more than 50 times keeps its number. An interval that mixes units, such as 1d12h from Bulk update, shows in its smallest unit, 36 hours: leave Every and Unit as they are and it stays 1d12h.

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 · × times in total

So ↻1h ×4 means four pings, one an hour, the first included. 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. The repetitions are the pings after the first one, so the task line shows one more: [2d3h,1h,3] is ↻1h ×4, and the most a plan allows here is 49, 50 pings in total. A single event uses the sentinel interval 0m and 0 repetitions — [2d3h,0m,0]. Distance and interval use only d, h and m. A value in months, such as [1M,0m,0], is refused, and the line is marked with an arrow.

The same rules apply as in the forms. Where new recurring reminders can’t be created, a triplet with repetitions above 0 is accepted only for a reminder the list already had. Even then, the limits in Repeating reminders apply. If several reminders break a rule, one message lists them all, one paragraph each. The same message also lists any other problem in the text, such as a list that’s too long or has too many tasks.

Two kinds of reminder can’t be saved, and the message names the task to fix:

• a reminder on a task with no owner. Reminders go to the owner, and a mention without the colon is only a tag: see Owners: the mention with a colon;
• a reminder with no date and a distance of zero, such as [0m,0m,0] on its own. Its only alert would be the moment you save, already gone;
• a reminder that can’t be read: a number too large, such as [1h,1d,99999999999], or a date that doesn’t exist.

A reminder written badly is marked with an arrow, like a line without a dash: two dates or two triplets on one line, a date without its triplet, or a reminder without task text. TTM doesn’t guess which one you meant.

TTM never removes a reminder by itself. A reminder whose alerts are all in the past stays on its task, as a record. It sends nothing more, and it doesn’t count among the reminders waiting.

These checks look only at the lines you change. Bulk update checks the lines you add or edit, and a task edit checks that task. A new list, a clone and an import check every line. Clean list, Reopen all, tags and deleting a task leave every reminder as it is.

Common errors

A reminder didn’t arrive, or something else went wrong? See Something not working?