Skip to main content
  • EN

Hi,

What timezone are FME Server Schedules supposed to be operating in?

I currently have a Schedule, set to “Once a Day” at 2.00am, and the job is being triggered at 1.00am each morning. After daylight savings this year, the job on the Schedule moved backward by an hour.

 

I also currently have an Automation Trigger schedule set to “Once a Day” at 12.30am, and the job is being triggered at 1.30am. After daylight savings this year, the job on the Schedule moved forward by an hour.

 

Last month, these were triggering at the correct time, but not any more.

The Automation is running in UTC, and the Schedule’s timezone is unknown or invalid. Time jumped forward, not backward. Can these be made to respect server local time? FME Server 2022.2
Build 22765

According to the documentation https://docs.safe.com/fme/html/FME-Flow/WebUI/Automations-Triggers/Trigger-Schedule.htm

Basic and CRON Expression must be configured according to the time zone of the FME Flow that runs the task. All other times can be expressed according to your local time zone.

Personally, I’ve had the most predictable results if the OS of the FME Flow instance is set to UTC and all schedules and automations are also set relative to UTC.

Reply


Community Stats

30,108
Posts
114,284
Replies
37,742
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.