I've attached some screenshots to show what it's doing.
It will only reset the hour back to 12 it still honors the exact minute I specify.
I did look over the known bugs for 2022.x but was unable to find any mention of this.
FME Server 2022.1 Build 22618 - win64
Hmmm, seems to be related to the timezone. (17 - 5 is 12). What platform are you running FME Server on?
Hi @virtualcitymatt. We're running on Windows Server 2019 64bit. I've also verified the time zone is set correctly for where we're at.
Did some more testing today and tried changing it to different times to see what it does.
When I changed it to start at 16:25 with a date of 2022-08-31 it will then change it to 23:20 on 2022-08-30 when I reexamine the parameter.
Here's the correct time I set:
Here's what it changes it to when I leave the Automations page and return:
UPDATE: This issue has been resolved for FME Server 2022.2 b22729 and newer.
Hi @ngstoke
I'm sorry that you have encountered this issue, I have been able to reproduce it and have filed a report with our development team to request a fix (issue ID: FMESERVER-18922). It looks like if FME Server is hosted in a different time zone when creating a Basic or CRON Schedule the start and end times are adjusted.
For example, if my current Server time: Fri-02-Sep-2022 11:30:00 AM -0700 and I set my schedule to start at 2022-09-02 20:00. After saving the Schedule it becomes 2022-09-02 13:00.
In FME Server 2021.2.6 this problem will occur in Schedules created from the Schedules page or from within an Automation.
In FME Server 2022.1+ this problem will occur in Schedules created from within an Automation only.
To workaround this issue, please set the Schedule Type to Repeat on Interval instead. I'm sorry for any inconvenience this may cause!
Also had this in 2022.1.1 build 22623. Only upgraded recently from 2021 so have used the repeat on interval workaround for the moment which appears to have worked.
Confirmed issue. We also recently upgraded our FME Server from 2021 to 2022.1 Build 22618.