You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating System (Including distribution name and version number)
Windows Server 2019
AMP version and build date (Always use the version number, 'latest' is not valid!)
version 2.4.8 - 20240129.1
Which AMP release stream you're using (Mainline, Nightly or FastTrack)
Mainline
I confirm:
that I have searched for an existing bug report for this issue.
that I am using the latest available version of AMP.
that my operating system is up-to-date.
Symptoms
What are you trying to do?
Execute a time-managed task, e.g. at 16:50 a server start on Monday - Thursday.
What are you expecting to happen?
That the named server will start at 16:50 on the days mentioned above.
What is actually happening? ('Nothing' is not an acceptable answer!)
This is executed one hour later, i.e. at 17:50, which is why we suspect a summer/winter time zone problem. In the rest of the AMP the time is correct, the difference is only in the schedule
Reproduction
As I said, we think it is a summer/winter time problem, possibly only with Windows (Server 2019) with German time zone.
The text was updated successfully, but these errors were encountered:
All schedules currently follow UTC time, not the operating system's time.
There's an issue here regarding making the scheduler user-friendly again: #720
Though it may be worth requesting a configurable/general system offset for daylight savings and the like.
Bug Report
System Information
Windows Server 2019
version 2.4.8 - 20240129.1
Mainline
I confirm:
Symptoms
Execute a time-managed task, e.g. at 16:50 a server start on Monday - Thursday.
That the named server will start at 16:50 on the days mentioned above.
This is executed one hour later, i.e. at 17:50, which is why we suspect a summer/winter time zone problem. In the rest of the AMP the time is correct, the difference is only in the schedule
Reproduction
As I said, we think it is a summer/winter time problem, possibly only with Windows (Server 2019) with German time zone.
The text was updated successfully, but these errors were encountered: