Recurring scheduling, schedules in the past instead of the future #548

Closed
opened 2026-04-05 16:20:27 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @wzrdtales on 2/18/2025

Describe the bug

With the following settings:

Image

On day 1 everything is expected, from day 2 on the first and any future recurrence, the event doesn't get scheduled as expected. It gets scheduled in the past as can be seen here:

Image

Interestingly enough, it is not just in the future, but the scheduled event is even one day earlier than the original first schedule.

To Reproduce

See screenshot settings.

Expected behavior

The scheduling settings are transported into the future depending on the recurrence setting.

Deployment Type
self hosted -

API: 7.0.3621 (f32b1950d9)
Dashboard: 7.0.3621 (f32b1950d9)

*Originally created by @wzrdtales on 2/18/2025* **Describe the bug** With the following settings: ![Image](https://github.com/user-attachments/assets/f1f5e120-58cb-4d82-8d94-f269dbbea3b8) On day 1 everything is expected, from day 2 on the first and any future recurrence, the event doesn't get scheduled as expected. It gets scheduled in the past as can be seen here: ![Image](https://github.com/user-attachments/assets/23f44ab7-2036-4109-b54e-275c8b9c1b93) Interestingly enough, it is not just in the future, but the scheduled event is even one day earlier than the original first schedule. **To Reproduce** See screenshot settings. **Expected behavior** The scheduling settings are transported into the future depending on the recurrence setting. **Deployment Type** self hosted - API: 7.0.3621 (f32b1950d9ac63c9c6a24e1bf44eeec2ffdb7805) Dashboard: 7.0.3621 (f32b1950d9ac63c9c6a24e1bf44eeec2ffdb7805)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#548