Is there a known issue in Fusion where some of the planned completion date timestamps coming over from Workfront differ by an hour?

[NicholasPa1]

Hi,

We have seen some discrepancies where the timestamps on the task planned completion date are differing by an hour:

For example, 2025-02-13T22:00:00.000Z or 2025-02-13T21:00:00.000Z

The planned completion date is set to 5 pm EST on all our tasks so my expectation would be that they all come over to Fusion with the T22:00:00.000Z timestamp, which is 10 pm GMT.

Hoping to gather some insight.

Thank you,

Nick

[DawnmarieD]

This may be a silly question but did you consider Daylight Savings? I'm not sure it auto adjusts for that hour but if not that might be the issue.

[Pan_Shahbazian]

It sounds like you’re running into a classic time zone mismatch in Workfront. Even though your tasks are set for 5 PM EST, Workfront still uses UTC under the hood, then converts display times according to both the system time zone (your organization’s main Workfront setting) and each user’s personal time zone. If those two differ—like, if one is configured for EST while another is set for something that observes daylight saving differently—you can see timestamps come through an hour off (for example, 21:00 UTC instead of 22:00 UTC).

From the official documentation, Workfront times can shift if the “instance” time zone (often tied to your office location) disagrees with the user profile time zone, or if the project schedule references a different zone than the user’s schedule.

[NicholasPa1]

Thank you!

So that looks to be the issue where Fusion does not have a built in detection for timezones.

I am trying code now but still not working:

I am pulling the plannedCompletionDate from Workfront and trying to parse out the months with parseNumber and substring but it doesn't seem to be evaluating the if statement correctly.  It's not looking at the range and am wondering if the AND is not correct?

Would appreciate any further insight!

Thank you!

Nick