Solved: Please spot the error in this flow logic

if-man · ‎02-24-2022

So, working with this flow I have it set for 3:30 PM EST and 23:30 EST. However, when I make it check for whether or not it is less than 16:00, it goes directly to no when it should have gone to yes. Right now it is 11:23 AM when I post this message. It SHOULD work to use at this time but it defaults to 16 as input for some odd reason.

Need a second pair of eyes on this to see where I'm going wrong.

mattias1172 · ‎02-24-2022

Can you try with this method (apologize for the small text):

Result:

*Update*

I didn't see your second response until after posting this. The reason the time comes back as 20:XX is because the expression you are using uses UTC, not the time zone you are actually in. Pretty much anything time related in Power Automate does this. The above flow I posted will fix this by converting to a new time zone. In my case, EST but change if you are elsewhere.

View solution in original post

mattias1172 · ‎02-24-2022

For the screenshots attached, what did you have as your time input? According to the second screenshot, the output being passed into the logic is 16 and in that case, 16 < 16 being false is correct (16 = 16, not less than 16).

For this to come out as True, you'd need 16 is less than or equal to 16.

if-man · ‎02-24-2022

My time output was set to utcnow as it formats it to basically 11. But the number comes out to 16, even if it was around 11:23 AM EST it still defaulted to a 16. Still have no understanding as to why it was setting that way when I wanted to let it grab from the time it has at that time.

Also I can set it to less than or equal to but when it hits around 3:30 PM/ 15:30 I'm sure it will work. I'm worried that if it isn't past that time which it should trigger around 23:30

if-man · ‎02-24-2022

Update: It did not work. For some reason the input was 20 at 3:30 PM EST/ 15:30 and do not understand how the input/output works for this certain design. It makes no sense on how it would work like that.

mattias1172 · ‎02-24-2022

Can you try with this method (apologize for the small text):

Result:

*Update*

I didn't see your second response until after posting this. The reason the time comes back as 20:XX is because the expression you are using uses UTC, not the time zone you are actually in. Pretty much anything time related in Power Automate does this. The above flow I posted will fix this by converting to a new time zone. In my case, EST but change if you are elsewhere.

if-man · ‎02-24-2022

How did you set up the Int? is it Int(Converted Timezone) or something else?

mattias1172 · ‎02-24-2022

the syntax is: int(string)

Here is the exact expression: int(body('Convert_Timezone'))

I passed the dynamic content of the "Convert Timezone" action:

if-man · ‎02-25-2022

Thank you so much for the help @mattias1172! But just a closing question is Power Automate always on the UTC even if I put down the EST UTC? Or am I just getting the timezones wrong?

if-man · ‎02-25-2022

Thank you so much for the help @mattias1172! But just a closing question is Power Automate always on the UTC even if I put down the EST UTC? Or am I just getting the timezones wrong?

mattias1172 · ‎02-25-2022

Unless there is an option to select the time zone, it defaults to UTC. If there is no option within the action itself, you would just need to use the time zone convert action.

As an example, the "Create Event" Outlook action has an option to select the time zone:

If you ever look at Azure/Exchange logs, you'll see a lot of UTC as well.