resetA countdown and a notification use different parts of Android. Reset can display the elapsed time correctly while an alert arrives later than its intended schedule. Start by checking the record and the phone’s alert settings.
Confirm the expected time
Check the actual session start and target. A reminder scheduled from an incorrect start will appear wrong even if Android delivered it exactly as requested.
If you recently changed the start, the remaining reminder schedule changes too. Past reminder times are not replayed. Keep that distinction in mind when comparing an alert with an old screenshot.
Review exact-alarm access
Reset requests Android’s exact-alarm capability for more precise scheduling. If that access is unavailable, the app uses an inexact alarm that Android may deliver later.
Exact-alarm access and ordinary notification permission are separate controls. Granting permission to show a notification does not automatically grant every scheduling capability.
For platform context, Android’s alarm scheduling documentation explains the distinction between exact and inexact alarms.
Check how the phone presents alerts
Do Not Disturb, silent channels and device battery settings can affect your experience of an alert. A notification visible in the shade without a sound may be a presentation setting rather than a timer error.
Phone manufacturers vary. Avoid disabling broad system protections indiscriminately. Check the controls relevant to Reset and consult the device’s own guidance.
Gather one clear example
For a support report, note the intended reminder time, when it appeared, app version, Android version and phone model. State whether the phone was restarted, the session edited or a quiet mode active.
Read the general reminder checklist if no alerts appear at all. Do not extend a fast merely because a notification has not arrived: the app cannot determine whether continuing is appropriate, and the actual end belongs in the record regardless of alert timing.