resetReset rejects overlapping fasting sessions so the same period cannot count twice. An overlap error usually means the proposed start or end crosses a neighbouring record, or an active session is still running.
Check the underlying times rather than changing a real time just to make the error disappear.
Compare two concrete intervals
A completed entry from Monday 8 pm to Tuesday 9 am overlaps another entry from Tuesday 8 am to Tuesday 10 am. Both include the hour from 8 am to 9 am Tuesday.
By contrast, an entry ending at 9 am and another starting exactly at 9 am do not overlap under Reset’s boundary checks. That does not make consecutive sessions a useful eating pattern; it only explains the software’s validation.
Look for a duplicate first
If you manually add a fast that was already recorded by the live timer, the new entry may cover the same interval. Inspect history before trying to save it again.
A duplicate can also be less obvious when one version has rounded times. The calendar dates and surrounding entries are more informative than the title alone.
Check midnight and AM/PM
A wrong end date can accidentally turn an overnight entry into a multi-day one. Similarly, entering 8 am instead of 8 pm can extend it into another session.
Correct the record that is actually wrong. Keep the original intended target separate from these timing corrections.
Consider the active timer
An active session has no final end time yet. A completed entry cannot extend into that active interval. If the active start is wrong, correct it; if the session actually finished, end it and record its real endpoint.
The manual logging guide covers the normal workflow. If a valid non-overlapping entry is still rejected, contact support with the app version, device model and a minimal example of the dates and times. There is no need to include a full personal history or medical details.