You’re offline. This is a read only version of the page.
8
Hi All,
There is a scheduled flow I have created which runs at 12:00 am everyday. When the flow running user is in IST zone and the date condition is met, the flow is running successfully to send the notification but when the flow running user is in UTC zone, there is 05:30 hours difference and the flow is not running for the same record.
For Example, with IST Time zone : 25-09-2023 is due date, it works fine but with UTC it shows as 24-09-2023T06:30 and it didn't fetch the record.
Could you please help me get this with this regard.
Thank you!
Hi @wskinnermctc ,
This was just an example of the convert time action itself, the actual usage in the screenshot wasn't designed to be the solution but rather to consider using convert time zone. I probably should have shown a blank action (that was my point).
@trice602 you probably understand the issue more than I do, I don't really follow what is going on.
However, I wanted to ask you about converting the timezone but then putting it into UTC? If they use the Universal Sortable [u] it will end the time with a "Z". Therefore it will be recognized as the UTC timezone. So why convert from Source A to Destination B, but then call it UTC?
If you set the destination timezone as Arizona, but then put a "Z" at the end, it is no longer Arizona, it is UTC.
#1
WarrenBelz
146,645
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,997
Most Valuable Professional
Share
Report
All responses (
Answers (
