My reminder did not fire
Work through this in order — the checks are arranged by how often they turn out to be the cause, so the early ones are worth doing even if they seem unlikely.
1. Was the browser open at the time?
This is the cause in most reports. Latr schedules reminders with the browser's alarm system, and that system only runs while the browser runs — so a reminder due at 10am on a laptop that stayed shut arrives when you next open Chrome, not at 10am.
How to confirm it: open the popup and look at Recent activity. If the reminder is there marked Missed, this was the cause — Latr caught it late and told you so.
What to do: read what happens when Chrome closes. The short version is to use the calendar handoff for anything you genuinely cannot miss, because a calendar entry reaches your phone and an extension cannot.
2. Are notifications allowed by your operating system?
Latr can fire perfectly and you still see nothing, because the notification is suppressed after it leaves the browser — by Focus on a Mac, or Focus assist and notification settings on Windows.
How to confirm it: the reminder shows in Recent activity as fired (not missed) but you never saw a toast.
What to do: follow if notifications never appear, which has the exact steps per operating system.
3. Was it inside your quiet hours?
If the reminder came due inside your quiet window, Latr held it deliberately and delivers it when the window ends. The row in the queue says held for quiet hours while it is waiting.
What to do: nothing, unless the window is wrong — check it in Settings → Notifications. The reminder's own schedule is untouched: a daily 2am reminder held until 7am is still a daily 2am reminder tomorrow.
4. Is it waiting on another reminder?
If you use dependencies, a reminder set to wait for another one will not fire until that one is done. The row shows what it is waiting for.
What to do: complete or delete the reminder it is waiting on — deleting the blocker releases anything waiting on it immediately.
5. Did it fire while you were away from the screen?
A notification that nobody interacts with is retired by the operating system after a few seconds. Latr records this: the history marks each delivery as clicked, dismissed or ignored, and ignored means the toast appeared and timed out.
What to do: set that reminder's priority to high or critical when you save it. Both keep the notification on screen until you answer it, instead of letting it retire on its own.
Still nothing
If none of the above matches, these are worth checking in order:
- Is the reminder actually in the queue? Open the popup. If it is not listed under Upcoming and not in Recent activity, it was never saved — the composer refuses a time in the past and shows why, and that message is easy to miss.
- Is the extension enabled? Check
chrome://extensions. An extension disabled by a profile sync or a policy fires nothing and looks normal. - Did the storage quota fill up? Latr says so explicitly when it happens, and names the setting to turn off. Page thumbnails are the largest thing it stores and the first thing to disable.
If you have worked through all of it and a reminder still did not arrive, tell us — include what the popup's Recent activity section says about it, because that distinguishes "never fired" from "fired and you never saw it", which are completely different bugs.
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.