SQL Server Insert Date is off in workflow

Question

SQL Server Insert Date is off in workflow

Christopher Fryett 195

I ran a set of performance tests on a flow which does an insert into a database and I am seeing odd results in the datetime fields. In some records it is an hour off, ie.. showing 9am when it is 10am. Is there an issue around using utcNow() in the flows for sql server shared connector? The on-premises db resides in mountain time while the resource is in US West.

User's image

Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-09T12:00:27.12+00:00
Hi Christopher Fryett,
Could you please provide below information to assist you further on this.

Confirm the exact Logic App expression used to produce the timestamp (e.g. utcNow(), formatDateTime(...), convertTimeZone(...)).

The SQL column type (e.g. datetime, datetime2, datetimeoffset(7)) and the table schema or CREATE TABLE statement.

Whether the insert is done by the Logic App mapping fields directly, or by calling a stored procedure (and if the stored proc uses GETDATE() etc.)

Whether the SQL Server is on-prem (you already said Mountain Time) and whether an on-premises data gateway is used (and the gateway/server OS timezone).

Is the highlighted rows and non-highlighted rows all inserted at same time with same logic app or the highlighted ones are from logic app and they are supposed to be 10am?
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-10T09:21:49.71+00:00

Hi Christopher Fryett, following up to see if you had a chance to check my previous response and if it was helpful. Do let me know if you're still facing the issue.
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-11T09:48:29.92+00:00

Hi Christopher Fryett, I hope you checked my last response, and it was helpful. Please do let me know if you need any further assistance on this.
Christopher Fryett 195 Reputation points

2025-09-15T15:05:40.53+00:00

@Rakesh Mishra My apologies for the delay. I am using the utcNow() and the insert is initiated through the SQL Server Insert row (v2) shared connector. The database is on-prem and going through an on-prem data gateway. The highlighted ones should show 10am.
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-22T08:26:01.4266667+00:00

Hi Christopher Fryett, following up to see if you had a chance to check my previous response and if it was helpful. Please do let me know if you're still facing the issue.

Answer accepted by question author

0 additional answers

Your answer

Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-09T12:00:27.12+00:00

Hi Christopher Fryett,
Could you please provide below information to assist you further on this.

Confirm the exact Logic App expression used to produce the timestamp (e.g. utcNow(), formatDateTime(...), convertTimeZone(...)).

The SQL column type (e.g. datetime, datetime2, datetimeoffset(7)) and the table schema or CREATE TABLE statement.

Whether the insert is done by the Logic App mapping fields directly, or by calling a stored procedure (and if the stored proc uses GETDATE() etc.)

Whether the SQL Server is on-prem (you already said Mountain Time) and whether an on-premises data gateway is used (and the gateway/server OS timezone).

Is the highlighted rows and non-highlighted rows all inserted at same time with same logic app or the highlighted ones are from logic app and they are supposed to be 10am?
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-10T09:21:49.71+00:00

Hi Christopher Fryett, following up to see if you had a chance to check my previous response and if it was helpful. Do let me know if you're still facing the issue.
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-11T09:48:29.92+00:00

Hi Christopher Fryett, I hope you checked my last response, and it was helpful. Please do let me know if you need any further assistance on this.
Christopher Fryett 195 Reputation points

2025-09-15T15:05:40.53+00:00

@Rakesh Mishra My apologies for the delay. I am using the utcNow() and the insert is initiated through the SQL Server Insert row (v2) shared connector. The database is on-prem and going through an on-prem data gateway. The highlighted ones should show 10am.
Rakesh Mishra 9,670 Reputation points Microsoft External Staff Moderator

2025-09-22T08:26:01.4266667+00:00

Hi Christopher Fryett, following up to see if you had a chance to check my previous response and if it was helpful. Please do let me know if you're still facing the issue.

Answer 1

Rakesh Mishra 9,670 Microsoft External Staff Moderator

Thanks @Christopher Fryett and apologies for delay in response.

From what you said: the flow is sending utcNow() and the insert uses the SQL Server Insert row (V2) connector to an on-prem DB via the on-prem gateway. Most likely the flow is inserting a UTC timestamp into a timezone-naïve SQL column (e.g. datetime/datetime2), so the row appears “off” when viewed in Mountain Time.

Please check

(a) the Logic App run history to see the exact value sent in the Insert action,

(b) the SQL column type (INFORMATION_SCHEMA.COLUMNS) and

(c) the server time (SELECT SYSDATETIMEOFFSET()).

To fix quickly, either convert UTC --> Mountain before insert with formatDateTime(convertTimeZone(utcNow(),'UTC','Mountain Standard Time'),'o') and store in DATETIMEOFFSET(7), or continue storing UTC and convert in your read/presentation layer.

Official docs: Logic Apps expressions, Convert time zone, SQL connector, and datetimeoffset.

Christopher Fryett 195 Reputation points

2025-09-22T22:29:23.18+00:00

Problem resolves as one of the data engineers stated the 'T' and 'Z' in the date is throwing things off going through the data gateway. I changed the Logic Apps to use formatDateTime(). Thank you for helping.

Share via

SQL Server Insert Date is off in workflow

0 additional answers

Your answer