On our easymorph server it seems that when we schedule anything, it’s in central time, but then the task log records everything in eastern time.
The screenshot example is a morph that we have scheduled to run daily at 2:00 am but as you can see the task journal captures them as having run at 3:00 am.
Is there a way we can change this so that they are at least in the same zone?
It’s a known issue that will be addressed in a future version. Currently, there is no way to sync the timezones. The scheduler uses the server timezone (CST in your case), while the journal shows timestamps in the browser time zone (EST in your case). If all your EasyMorph users are in the Eastern timezone, I would suggest changing the Server time from CST to EST.
Please, ensure that you have correct UTC time on both machines by invoking wmic path win32_utctime get *
from the terminal (results should be the same)
Also, you can ensure that timezones are identical too using: systeminfo | find "Time Zone:"
How big is the difference reported in the server message?
Additionally, I wanted to mention that the Web client compares the time reported by the server with the time provided by the web browser. To verify that your browser is providing the correct timezone, you can open the developer console by pressing Ctrl+Shift+J in Chrome/Firefox and entering new Date() into the prompt. This should display the current time which you can compare against your local time.
The issue may be with the browser as it seems to assume that you are in GMT-4, while other sources indicate UTC-5. This could be a known bug, as it has been reported in instances such as this one Chrome displaying wrong time zone - Google Chrome Community.
Unfortunately, currently there is no option to disable the message if the browser reports a time that is off. However, I can suggest exploring the workarounds outlined in the link I provided. These may help Chrome to ‘recognize’ the correct time zone and avoid the message altogether.
That’s unfortunate. I tried the suggested link, it didn’t fix anything. I’ll just explain to my users to ignore this message as it is incorrect. Thanks.