Please see screenshots below for details. This is a single Update Row (V2) SQL action. The only inputs are the id and a timestamp as a string in UTC (2025-06-09T18:11:45Z). The action itself is for some reason converting the timestamp I'm giving it in UTC to some other local time zone of UTC-4:00. I'm passing the Z to indicate the input is already UTC. Even if this is intended behavior, automate should not be setting the Z on the output after converting it. I struggle to believe this has not been noticed... Is this a known bug? Am I doing something wrong? I understand I can simply add time to the input to cover the unintended offset but as I have no idea what time zone it thinks I'm in at UTC-4:00 I don't know if I need to worry about DST or not.
Datetime and Datetime2 got the value + 2 ( my time zone). I think the problem is from the gateway, since the both cannot take an offset.
1. all columns used utcnow(). +2 timezone
2. Only last column used 2025-06-09T18:11:45Z. Run the flow in +2
3. Only last column used given value, others used utcnow(), run the flow in +8 timezone.
4. all columns used given value. +2 timezone
5. all columns used given value without Z. +2 timezone
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
11
Share
Report
All responses (
Answers (
