‎SLA Timer Flow - Date & Time Mismatch in the Sharepoint‎

(1) Share

Report

Posted on by IB-22040114-0

Hi everyone, I am facing a date and time mismatch issue in SLA Timer Flow that uses Clamp logic. The flow is to calculate SLA timestamp, sets status (OnTrack/Warning/Breach), and saves the WarningDue and BreachDue to SharePoint.
The flow runs successfully and shows the timestamp in the run output, but after saving to SharePoint, the stored date/time is different.
This mismatch affects SLA tracking and reporting accuracy, even though no errors occur during flow execution. I need help to correct the SLA timestamp is stored correctly in SharePoint.

The example is here:

In SharePoint
SLAStartDate: 4/22/2026 9:30 AM
WarningDue: 4/23/2026 5:00 PM

BreachDue: 4/23/2026 9:00 PM

Output History:
WarningDue: 2026-04-23T09:00:00Z
BreachDue: 2026-04-23T05:00:00Z

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 2,126 on at

Like (0)

Report
Copy link

Link copied!

The mismatch occurs because Power Automate is producing timestamps in UTC (indicated by “Z”), while SharePoint stores and displays them in the site/user’s

local timezone.

Additionally, your flow likely applies incorrect or double timezone conversion, causing swapped or shifted values.

The correct solution is to ensure all SLA timestamps are converted to UTC using convertTimeZone() before saving to SharePoint. SharePoint will then

automatically display the correct local time without discrepancies.

Was this reply helpful? Yes No
Suggested answer

Haque 2,543 on at

Like (1)

Report
Copy link

Link copied!
Hi @IB-22040114-0,

The example you shared shows a classic timezone swap issue:

SharePoint SLAStartDate: 4/22/2026 9:30 AM (local time)

WarningDue: 4/23/2026 5:00 PM (local time)

BreachDue: 4/23/2026 9:00 PM (local time)

But the flow output shows:

WarningDue: 2026-04-23T09:00:00Z

BreachDue: 2026-04-23T05:00:00Z

Here, the WarningDue and BreachDue times appear swapped and shifted by hours, indicating a timezone conversion mismatch.

The possible reasons:

The flow outputs timestamps in UTC (the "Z" suffix means UTC).

SharePoint expects local time or converts incoming UTC to local time automatically.

The flow may be passing the wrong timestamp to the wrong field or mixing up WarningDue and BreachDue values.

Or the flow is not converting timestamps consistently before saving.

To have possible fix let's check the follwing checkpoints:

Double-check that the flow assigns the correct timestamp to each field (WarningDue and BreachDue).

Use convertTimeZone() in Power Automate to explicitly convert all timestamps to UTC before saving.

Confirm SharePoint date/time columns are set to "Date and Time" with the correct timezone setting (usually "Date & Time (UTC)" or "Date & Time (Local)").

When saving, format timestamps as ISO 8601 strings with the "Z" suffix for UTC.

If SharePoint expects local time, convert timestamps to that local timezone explicitly before saving.

Example Power Automate expression to convert to UTC ISO 8601:

convertTimeZone(triggerOutputs()?['body/SLAStartDate'], 'YourLocalTimeZone', 'UTC', 'yyyy-MM-ddTHH:mm:ssZ')

Note: Replace 'YourLocalTimeZone' with your actual timezone name, e.g., 'Eastern Standard Time'.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
David_MA 14,424 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

To expand on what the others have said, all dates in SharePoint are stored in UTC. But how they display are affected by the time zone setting of the site, which converts the UTC value to the time zone of the site. If you work in a company with offices around the world, this could be set differently on every site.

'

This can further be affected by language and region settings in your user profile:

If I did not have this set, I would see dates in SharePoint in Pacific Time. But since I have my profile set to Eastern Time, dates are converted to this time zone instead. Users can change this at My Account - Settings & Privacy.

Was this reply helpful? Yes No