All my backups ran outside of schedule

[Tungsten]

I switched on my PC this morning and the four backup tasks I have all started to run outside of their scheduled time slot. Non of the backups were previously missed.

Here in the UK the clocks went back an hour overnight, could this be the cause?

[al3x]

Hi,

That's hard to tell based on what you have provided so far.

For my PC my HBS schedule was triggered normally this morning (Germany here, we also went back 1 hour last night).
But I've ticked "Run missed schedule at the next system startup", so this was expected behavior.

To help you with your question, I think we need at least these things:
- What schedules have you set up exactly (with specific times and settings)?
- At what time was your PC started the last time and when did you power it down?
- At what time did you start the computer today?

Also, if possible, please provide the log files for your HBS. This might help the developers to further analyze what was happening:

Please click "" > "Save log file" to open the save log file dialog, save the zip file and attach it to your post.



Cheers,
al3x

[Tungsten]

My Schedule summary is:
1. Disk Partition to run every other day at 10AM to USB backup drive.
2. Disk Partition to run weekly on Sunday at 11AM to NAS drive
3. Disk Partition to run manually to USB drive
4. File Backup to run daily at 12PM to USB Backup Drive

None of these backups had been missed and were all on schedule.

The only thing I did different today from any other day was I manually ran backup No3 from above as soon as my PC started around 7-7.30 this morning.

[al3x]

Thanks!

So just to make sure I understood this correctly:
- Tasks 1, 2 and 4 ran instantly today after you started your PC this morning?
- Have you ticked "Run missed schedule at the next system startup" for any of those tasks?

If you have ticked that option and the last runs at 10am/11am/12pm all finished successfully last time, then there might indeed be a bug somewhere that causes HBS to misinterpret the time of the last run.

My guess is:
- HBS probably saves the last successful run of a task in unix timestamp format, e.g. 2026-10-24 10:00am UTC+2 might be 1792828800.
- Then the time shift happened last night causing the time to go back 1 hour.
- Today HBS might have used the unix timestamp of the last run and interpreted it as UTC+1 instead.
- Now HBS probably thinks the last run was at 2026-10-24 09:00am.

That would result in running the schedule again because HBS thinks it missed the last run yesterday.

I can't reproduce this on my side unfortunately and I'm also not sure how HBS handles the last run check exactly, but maybe this could be the issue here.
I'm sure @admin (Hasleo staff) might have an idea and the logs you provided could still be helpful.

[Tungsten]

I do have "Run missed schedule at the next system startup" but at the time of switching off my PC last night ALL backup tasks were completed and on schedule to run at 11am and 12pm today and 10am, 12pm tomorrow.

From the attached screenshot you can see that:

1st task ran at 7.39am but was not scheduled to run until 10am tomorrow.
2nd task to my NAS drive failed with error 0x0B3300DA00000001 at 7.15am then completed successfully at 11am on schedule.
3rd task war triggered manually at 7.15am
4th task ran at 7.42am and then again on schedule at 12pm

[al3x]

Ok, perfect, that adds up with my unix timestamp theory then.

That's actually a hard to find bug that needs a combination of things to show. We need a schedule that triggers sometime after the PC was started and we also need a time shift to standard time. That's also why I didn't see this bug on my PC: My schedules are at 9:00am every day and I usually start the PC afterwards, so I always have a missed schedule anyway 

Let's wait for Hasleo, this is probably something that can be fixed soon. Also, next time shift is in 1 year, so plenty of time to fix this 

[Tungsten]

This has not caused any problems with my backups I just thought it strange why they all seemed to want to run at once, off schedule.

Thanks for you time and assistance.

[al3x]

You're welcome! And thanks for reporting this, because I don't think a lot of people try to get to the bottom of such issues and probably just move on instead.