Hello,
Thank you for the additional details — that observation about the schedule correcting itself after a restart is very helpful.
At this point, we don’t have enough evidence to confirm the exact root cause or whether this behaviour is expected or a defect, especially around daylight saving time handling. The fact that restarting the scheduler temporarily resolves the issue suggests there may be a timing or caching inconsistency, but we need more data to validate this.
To move this forward, I’d like to gather a bit more information:
The exact version of your Devolutions Server
The timezone configured under Administration > System Settings > General > Time-based usage
The Windows timezone on the server hosting Devolutions Server
Confirmation of when the DST change occurred vs when the schedule started drifting
If possible, a short extract of logs around a rotation event before and after restarting the scheduler
Regarding your question: at the moment, there is no built-in mechanism to automatically resync the scheduler after a DST change without a restart.
Once we have the information above, we can determine whether this is a known limitation, a configuration issue, or something we need to escalate further.
Best regards,
