Introduction
British Columbia, Alberta, the Northwest Territories, and Manitoba will not set clocks back on November 1, 2026, and will stay on permanent year-round time:
- British Columbia (most of the province): UTC-7
- Alberta, and aligned locations in the NWT and southeastern BC: UTC-6
- Manitoba: UTC-5
Until FME is updated, this can cause problems in two areas:
- Workspaces that use date-time transformers or functions may fail. This applies to FME Form and to jobs running on FME Flow.
- FME Flow schedules, automations, job logs, and timestamps may be off by one hour.
Am I Affected?
Workspaces in FME Form and Jobs on FME Flow
You are likely affected if the operating system running FME is set to one of the new Windows time zones and your workspaces use date-time transformers or functions:
- (UTC-07:00) Pacific Time (British Columbia)
- (UTC-06:00) Mountain Time (Alberta)
- (UTC-05:00) Manitoba
FME Flow Schedules and Automations
You are affected if all of these are true:
- You run self-managed FME Flow 2026.3 or earlier on Windows or Linux.
- The machine running FME Flow is in one of the four provinces or territories, whether or not it has already been switched to the new Windows time zone.
- The machine uses one of the affected time zones: on Windows, (UTC-08:00) Pacific Time (US & Canada), (UTC-07:00) Mountain Time (US & Canada), (UTC-06:00) Central Time (US & Canada), one of the new regional zones, or one of Microsoft's temporary zones (as of October 8, 2026; see Microsoft's interim guidance under Additional Resources); on Linux, the matching regional or US zone, or an Etc/GMT zone. See the FME Flow article for the full list.
- You use Basic schedules, CRON schedules, or Repeat-on-Interval schedules measured in days, weeks, months, or years; Automations with a Schedule trigger; or queue control active periods.
Not Affected
- FME Flow Hosted. Users are unable to select the new time zones in account settings.
- FME Flow running on a machine set to UTC, or to a time zone outside the four provinces and territories, unless it is one of Microsoft's temporary time zones.
Fix Status
| Product | Version | Status |
|---|---|---|
| FME Engine (FME Form and FME Flow jobs) | Hotfix | Coming soon. This article will be updated when the hotfix is released. |
| FME Flow (schedules, automations, logs) | 2026.4 | Fix expected |
| FME Form and FME Flow | Older than 2026.3 | Workaround under review |
| FME Flow Hosted | Not affected | Users are unable to select the new time zones |
| FME FlexNet License Server | Not affected | It is possible logs may be off for one hour if the license server is not reset after changing the operating system time zone |
Articles
Known Issue: Date/Time Transformers Do Not Recognize New Canadian Time Zones
For workspaces in FME Form and jobs run on FME Flow. Explains the issue and the workarounds until you can upgrade.
Known Issue: FME Flow Schedules Run Late After Canadian Time Change
For self-managed FME Flow. Explains why schedules run one hour late and the steps to fix each machine running FME Flow.
Additional Resources
Microsoft: Interim guidance for British Columbia time zone changes 2026
Microsoft: Interim guidance for Alberta time zone changes 2026