Skip to main content
Solved

BC Time zone Change

  • Oct 20, 2026 3:16 PM UTC
  • 15 replies
  • 284 views

navid.fotovaty
Supporter
Forum|alt.badge.img+4

Hey everyone, 

Any idea how the time zone in BC change going to affect Forms and Flow? Windows update is going to add a whole new time zone name “(UTC-07:00) Pacific Time (British Columbia)” on Nov 1 if I understand it correctly. 

I guess Flow will use server time, but what about Form? What will happen if we have done a date conversion within a Form? 

Best answer by daveatsafe

Official Community article is now up at https://support.safe.com/hc/en-us/articles/49955477149837-New-Canadian-Time-Zones-and-FME-Are-You-Affected. It includes fixes for both FME Form and Flow.

View original

15 replies

sblazey
Contributor
Forum|alt.badge.img+1
  • Contributor
  • Oct 20, 2026 6:11 PM UTC

I came here looking for this.  I ran a Windows update on my computer this morning which added the new “(UTC-07:00) Pacific Time (British Columbia)” time zone to my computer (it is now an option for me in Outlook and our IT team announced it was coming).

I just ran some FME on my desktop that has a DateTimeCalculator that I use to “Calculate Interval between Datetimes”.  It compares the date in my “ModifiedDate” field with the @DateTimeNow().

I am getting this error now:

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to load timezone data. current_zone() failed: A mapping from the Windows Time Zone id "British Columbia Standard Time" was not found in the time zone mapping database.. Please visit http://www.safe.com/support

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to evaluate input expression: @DateTimeDiff(@DateTimeNow(),@Value(ModifiedDate),DAYS)

I am guessing I need to add the new time zone somewhere in FME Form and Flow?

 

Edited to add: I am running FME 2024.2.1.0 (20241202 - Build 24801 - WIN64)

 

Thanks,

Stephanie 


sblazey
Contributor
Forum|alt.badge.img+1
  • Contributor
  • Oct 20, 2026 6:55 PM UTC

As a workaround for this particular workspace, since I am comparing my ModifiedDate with a DateTimeNow() and I only care about the rough number of days that has lapsed between them, I changed my workspace to use a DateTimeStamper and a DateTimeConverter instead.

If I cared about a more accurate time or a precise level of hours/minutes, this wouldn’t work as-is (I would have to do extra math to accommodate for time zones).  

Sharing in case it helps someone dealing with a similar issue:

 

Previously, I had a DateTimeCalculator, where I compared my ModifiedDate with @DateTimeNow():

 

This threw the error I noted above:

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to load timezone data. current_zone() failed: A mapping from the Windows Time Zone id "British Columbia Standard Time" was not found in the time zone mapping database.. Please visit http://www.safe.com/support

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to evaluate input expression: @DateTimeDiff(@DateTimeNow(),@Value(ModifiedDate),DAYS)

 

The changes I made are as follows:

  1.  Add a DateTimeStamper in the Coordinated Universal Time (UTC):
  2.  

  3. Add a DateTimeConverter to format those dates to YYYYMMDD:

  4.  
  5. Then I changed my DateTimeCalculator to use the new _timestamp field instead of DateTimeNow():
  6. And kept the same tester I had to find values within the last 15 days:

  7.  
  8. This workaround works for this particular workflow because it is simple and I don’t mind if it’s off by 8 hours.

I am still interested to know if there are some better overarching configuration solutions for the rest of my workspaces on Form (and Flow?) that are not as easy to fix.  Some kind of blanket solution for everything that I can set somewhere instead of finding all the workspaces with DateTime related things would be awesome.

Thanks!

Stephanie


daveatsafe
Safer
Forum|alt.badge.img+24
  • Safer
  • Oct 20, 2026 11:51 PM UTC

This issue will be fixed in the upcoming FME 2026.3.1 maintenance release (builds 26660+). We have updated FME’s time zone database to include the BC, Alberta, NWT and Manitoba time zone changes.


daveatsafe
Safer
Forum|alt.badge.img+24
  • Safer
  • Oct 21, 2026 12:08 AM UTC

The fix is already in the current FME 2026.4 beta, which can be downloaded from safe.com/beta.


navid.fotovaty
Supporter
Forum|alt.badge.img+4

This issue will be fixed in the upcoming FME 2026.3.1 maintenance release (builds 26660+). We have updated FME’s time zone database to include the BC, Alberta, NWT and Manitoba time zone changes.

Hi Dave, 
So, for someone like me who is on on 2026.1.2, what should I do? Is there a hotfix I can download? 


sblazey
Contributor
Forum|alt.badge.img+1
  • Contributor
  • Oct 21, 2026 10:43 PM UTC

This issue will be fixed in the upcoming FME 2026.3.1 maintenance release (builds 26660+). We have updated FME’s time zone database to include the BC, Alberta, NWT and Manitoba time zone changes.

This is great to hear.  We are planning our next FME, Esri, and server environment upgrade in June 2027, so is there a workaround I can implement in the meantime?  Can I add the new time zone somehow?


navid.fotovaty
Supporter
Forum|alt.badge.img+4

Hey everyone, 

Any idea how the time zone in BC change going to affect Forms and Flow? Windows update is going to add a whole new time zone name “(UTC-07:00) Pacific Time (British Columbia)” on Nov 1 if I understand it correctly. 

I guess Flow will use server time, but what about Form? What will happen if we have done a date conversion within a Form? 

A work around I have found for @CurrentDateTime() failing in Flow is to declare it with utc as a parameter likeso @CurrentDateTime(utc). This has fixed many of my current issues. 


navid.fotovaty
Supporter
Forum|alt.badge.img+4

As a workaround for this particular workspace, since I am comparing my ModifiedDate with a DateTimeNow() and I only care about the rough number of days that has lapsed between them, I changed my workspace to use a DateTimeStamper and a DateTimeConverter instead.

If I cared about a more accurate time or a precise level of hours/minutes, this wouldn’t work as-is (I would have to do extra math to accommodate for time zones).  

Sharing in case it helps someone dealing with a similar issue:

 

Previously, I had a DateTimeCalculator, where I compared my ModifiedDate with @DateTimeNow():

 

This threw the error I noted above:

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to load timezone data. current_zone() failed: A mapping from the Windows Time Zone id "British Columbia Standard Time" was not found in the time zone mapping database.. Please visit http://www.safe.com/support

DateTimeCalculator_1 (TeeFactory): DateTimeCalculator_1: DateTimeCalculator: Failed to evaluate input expression: @DateTimeDiff(@DateTimeNow(),@Value(ModifiedDate),DAYS)

 

The changes I made are as follows:

  1.  Add a DateTimeStamper in the Coordinated Universal Time (UTC):
  2.  

  3. Add a DateTimeConverter to format those dates to YYYYMMDD:

  4.  
  5. Then I changed my DateTimeCalculator to use the new _timestamp field instead of DateTimeNow():
  6. And kept the same tester I had to find values within the last 15 days:

  7.  
  8. This workaround works for this particular workflow because it is simple and I don’t mind if it’s off by 8 hours.

I am still interested to know if there are some better overarching configuration solutions for the rest of my workspaces on Form (and Flow?) that are not as easy to fix.  Some kind of blanket solution for everything that I can set somewhere instead of finding all the workspaces with DateTime related things would be awesome.

Thanks!

Stephanie

Hi Stephanie, 
This is working too “@DateTimeNow(utc)”
This is the output : 20261022153916.6156082+00:00

 


daveatsafe
Safer
Forum|alt.badge.img+24
  • Safer
  • Oct 22, 2026 4:00 PM UTC

The time database in FME appears to be fairly self-contained, so you could try installing FME 2026.4 beta to a separate folder, then copying the time database to the earlier FME version:

  • rename the existing FME folder <FME home>\datetime\txdata to <FME home>\datetime\txdata_backup
  • copy FME 2026.4\datetime\txdata to <FME home>\datetime\txdata

If this transplant causes any problem, you can just replace it with the backup.


adamminke
Contributor
Forum|alt.badge.img+5
  • Contributor
  • Oct 22, 2026 6:11 PM UTC

The time database in FME appears to be fairly self-contained, so you could try installing FME 2026.4 beta to a separate folder, then copying the time database to the earlier FME version:

  • rename the existing FME folder <FME home>\datetime\txdata to <FME home>\datetime\txdata_backup
  • copy FME 2026.4\datetime\txdata to <FME home>\datetime\txdata

If this transplant causes any problem, you can just replace it with the backup.

 

Dave,

You mentioned this will be fixed in the upcoming FME 2026.3.1 maintenance release (build 26660+). But we can't easily upgrade our FME Flow and Form builds right away due to organizational constraints. Will there be any backported patch releases for earlier versions? Or is moving to build 26660+ the only official software fix?

Thanks for suggesting the workaround of downloading 2026.4 beta and copying the time database. Will Safe be doing any testing of this solution? We’d like to know if this will be considered an officially supported workaround for production FME Flow environments?

Our team in Alberta has suggested an interim solution of switching our host server's OS time zone to a known zone like Saskatchewan (UTC-06:00) to bypass the issue. This is not our preferred long-term solution, but it should work for now. Unless there are other implications of this I should be considering…

 


daveatsafe
Safer
Forum|alt.badge.img+24
  • Safer
  • Oct 22, 2026 8:33 PM UTC

I’ve tested this workaround on a few versions of FME, and it appears to work OK. The dev team also thinks it is a viable option. Keeping the old folder as a backup makes it really easy to reverse if any problems are found.

The structure of the tzdata doesn’t change between versions, just the entries, so it is one of the few parts of FME amenable to a patch.

We are looking into the best way to provide a patch for users of older FME versions of Form and Flow, and will be testing it more extensively. 


adamminke
Contributor
Forum|alt.badge.img+5
  • Contributor
  • Oct 23, 2026 5:53 PM UTC

I’ve tested this workaround on a few versions of FME, and it appears to work OK. The dev team also thinks it is a viable option. Keeping the old folder as a backup makes it really easy to reverse if any problems are found.

The structure of the tzdata doesn’t change between versions, just the entries, so it is one of the few parts of FME amenable to a patch.

We are looking into the best way to provide a patch for users of older FME versions of Form and Flow, and will be testing it more extensively. 

 

Thanks Dave (and the Safe team) for looking into this and testing the workaround. Hopefully we’ll also hear more about the patch sometime soon.

 


nic_ran
Supporter
Forum|alt.badge.img+20
  • Supporter
  • Oct 26, 2026 3:32 PM UTC

Hi ​@daveatsafe , just throwing in my own two cents here. All my clients’ workspaces on Flow failed last night due to a server patch and the new Alberta timezone. It would be great if Safe could provide an officially tested and supported fix for this for those clients who are unable to upgrade to the latest version of FME.


daveatsafe
Safer
Forum|alt.badge.img+24
  • Safer
  • Best Answer
  • Oct 28, 2026 4:06 PM UTC

Official Community article is now up at https://support.safe.com/hc/en-us/articles/49955477149837-New-Canadian-Time-Zones-and-FME-Are-You-Affected. It includes fixes for both FME Form and Flow.


sblazey
Contributor
Forum|alt.badge.img+1
  • Contributor
  • Oct 29, 2026 5:53 PM UTC

You guys are so awesome!  We ran the fixes for Form and Flow on our server and desktops and so far everything looks great.  I ran some test workspaces that had failed before and they worked with no errors.  Thanks for your work on this, you guys are always on the ball :)