resetIf you ate and forgot to stop the timer, the continuing counter does not describe an actual fast. Correct the record to the time the interval really ended. You do not need to keep the inflated duration or start over with an empty history.
Establish the actual endpoint
Use the best information you have about when the interval ended. Check the date as well as the time. Breakfast yesterday and breakfast today are 24 hours apart even when the clock labels match.
Do not assume the target notification records the time you ate. It tells you the chosen duration was reached; it cannot detect the meal.
End the active session, then correct it
In Reset 1.1.0, a completed entry has an editable end time. End the active session first, then open the finished entry in history and correct the end to the actual past time.
Also verify the start and intended target. The app rejects an end before the start, future times and overlapping intervals.
Expect statistics to change
An accidentally long entry can raise the average and total hours. Correcting it removes those extra hours from the history calculations.
Target completion, streaks or badges may also change if they depended on the inaccurate record. That is an expected consequence of making the data truthful, not a separate fault to undo.
Prevent the same confusion next time
If a finish reminder would help, check the Android notification settings. Even with reminders enabled, record the actual end yourself.
A quick weekly review can catch unexpectedly long entries before they affect months of interpretation. If you cannot remember the exact endpoint, avoid treating the result as a precise measurement. The app’s role is to keep a useful timing record, not make a forgotten tap into evidence that you completed an unusually long fast.