Repeating reminders
A repeat reopens the same page on a schedule. Ten rules cover most of what real life asks for, including the two that calendars usually get wrong — the same weekday each month, and the last working day.
The rules
| Rule | What it does |
|---|---|
| Daily | Every day at the same time. |
| Every weekday | Monday to Friday. Nothing at the weekend. |
| Weekly | Once a week, on the day you set it. |
| Monthly | The same date each month. A 31st clamps to the last day in short months rather than skipping them. |
| Same weekday each month | "The third Thursday" — how recurring meetings are actually described. |
| Last working day of the month | Steps back off a weekend. Invoices, payroll, month-end reports. |
| Every 2 weeks | Fortnightly. |
| Every 30 days | A fixed interval, ignoring month lengths. |
| Every 90 days | Quarterly reviews, password rotations, filter changes. |
| Every N days | Any interval you type — every 10 days, every 6 weeks. |
Repeat lives behind the composer's More disclosure, because most saves are one-offs. Set it once and the reminder keeps coming back on its own.
How it rolls forward
When a repeating reminder fires, Latr immediately schedules the next occurrence from the original time rather than from the moment it actually went off. A daily 9am reminder delivered late at 11:20 — because the browser was shut — is still a 9am reminder tomorrow.
That sounds obvious and it is the thing repeat features most often get wrong. If the next occurrence stepped from the delivery, a reminder you kept opening a bit late would drift later every day until it was arriving at midnight.
Locking a time zone
A repeating reminder can be pinned to a specific time zone. A 9am London standup stays 9am London whether you are in Lisbon or Denver.
Without the lock, a repeat follows your machine's clock, which is right for personal routines — you want your evening reminder in the evening wherever you are — and wrong for anything shared with other people. Set it on the meeting, not on the gym.
Snoozing one occurrence
Snoozing a repeat pushes only the occurrence in front of you. The series is untouched, and the next one arrives at its normal time. That is a different mechanism from rescheduling, which moves the reminder itself.
See snooze and early warning for the presets and how they stack.
Seeing that it fired
A repeating reminder never leaves the queue — it rolls forward instead — so "did last Monday's actually go off?" cannot be answered by looking at the list. Latr keeps a seven-day delivery log for exactly this, shown under Recent activity in the popup. Each occurrence appears there with the time it was delivered and whether you clicked it.
Log entries have no row menu, because the reminder itself is still in the queue and that is where acting on it belongs.
Stopping one
Edit the reminder and set Repeat back to none, or delete it. Deleting is undoable — see accidental deletions.
Marking a repeat as done does not end it. Completion ticks off the current occurrence and rolls the series forward, which is what you want for a weekly task you have just finished. To end the series, remove the repeat.
Something unclear, or something Latr does that this page does not cover? Tell us — the page is easier to fix than the confusion it causes.