cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

AddMinutes condition not reading Converted Time

Hello all!

 

I'm writing a Flow that scrapes an API for data that includes a timestamp. If the timestamp is within the last 30 minutes, the Flow should post a message as Flow bot to a Teams channel.

 

Time is displayed in the API as a 12-digit string in U.S. eastern time; I'm converting it to UTC in my Flow, which is testing successfully.

 

I then have a conditional: If converted time is greater than AddMinutes(utcNow(),-30), post the message to the Teams channel.

 

That conditional is not working. Even when the timestamp in the API is within the last 30 minutes, the conditional comes back as false. It never posts the message.

 

I've tried the conditional two ways; you can see that plus the output of converted time and how I'm converting time in the screenshots below.

 

Any guidance would be appreciated!

 

FLOW3.jpgFLOW2.jpgFLOW1.jpg

FLOW4.jpg

1 ACCEPTED SOLUTION

Accepted Solutions

Hey all! This is resolved. Thanks for your help working through this with me!

 

When I converted to Eastern I had been using this:

 

formatDateTime(concat(substring(outputs('Compose_2'),0,4),'-',substring(outputs('Compose_2'),4,2),'-',substring(outputs('Compose_2'),6,2),' ',substring(outputs('Compose_2'),8,2),':',substring(outputs('Compose_2'),10,2)),'yyyy-MM-dd hh:mm')

 

I needed to capitalize the hours; this fixed it:

 

...'yyyy-MM-dd HH:mm')

 

THANK YOU again!

View solution in original post

14 REPLIES 14
Pstork1
Most Valuable Professional
Most Valuable Professional

It should definately be the second way of doing it.  The parameter for UTCnow() is the format pattern you want, not the time.  In your first try you are feeding it the converted time, not a format pattern.  

 

So the second set of code looks correct.  But could you show us an actual run of the flow with a compose to show the output of the time conversion and the addminutes() function?  That way we can see what is actually being compared.  That will probably identify why its not working.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
eric-cheng
Solution Sage
Solution Sage

Hi @ianhillmedia ,

 

Please check to ensure the format of both dates are in the same format.  

 

I am not in front of my pc but try formatting the utcnow() into the same format.

 

 

As mentioned above, please post the data from your run.

Sure! Any guidance would be appreciated. In this case I used AddMinutes(utcNow(),-90), just to make sure there was data from the API to capture. Screenshots below. Let me know if I can provide anything else that would help! FYI it's 12:30 p.m. ET, whichis 4:30 p.m. UTC right now. THANK YOU!

FLOW3.jpgFLOW2.jpgFLOW1.jpg

That shows the converted time.  But can you also add a compose just before the condition and use the same AddMinutes() function as in the right side of the condition.  Then we can see what is actually being compared.  The converted time is in ISO 8601 format and the add minutes should default to that format as well, so I don't think formatting is the issue.  We need to make sure the AddMinutes is putting out the time you think it is.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Done! So here's what I get when I Compose:

 

 

addMinutes(utcNow(body('Convert_time_zone')),-90)

 

 

Screen Shot 2021-07-11 at 1.12.01 PM.png

 

I also Composed:

 

 

addMinutes(utcNow(),-90)

 

 

 

And got 

 

2.png

In both cases, the condition still returned...

Screen Shot 2021-07-11 at 1.17.30 PM.png

 

THANK YOU for your help!

Try this. Got it working in mine.  

 

formatDateTime(addMinutes(utcNow(),-30),'yyyy-MM-dd HH:mm:ssZ')

 

Screenshot_20210712-032046_Chrome.jpg

Add a formatDateTime() function around the addminutes() to make sure its in same format as the adjust time zone.  Use this format.  'yyyy-MM-dd hh:mm:ssZ'



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

No luck, unfortunately. 

 

I used:

formatDateTime(addMinutes(utcNow(),-60),'yyyy-MM-dd HH:mm:ssZ')

 

Results below.

 

Screen Shot 2021-07-11 at 6.14.30 PM.pngScreen Shot 2021-07-11 at 6.14.49 PM.png

And here's a weird rub. This — expression less than Converted Time — always returns the condition as false, no matter what. It should return true when Converted Time is within 60 minutes.

Screen Shot 2021-07-11 at 6.32.50 PM.png

 

Meanwhile, this — expression greater than Converted Time — always returns as true, even when Converted Time is within 60 minutes and it should be false.

 

Screen Shot 2021-07-11 at 6.33.05 PM.png

Not having any luck, unfortunately. See below.

Still no luck.

I've suggested several times now that you add a compose statement just before the condition and put the right side of your condition in there.  That will show you exactly what your date and time is comparing to.  Then we can figure out why its not comparing correctly.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Hi! Thanks for the reply; I believe that's what I did when you first suggested it — see my comment from seven hours ago — but I just did it again, see below. I did a compose with:

 

formatDateTime(addMinutes(utcnow(),-30),'yyyy-MM-dd HH:mm:ssZ')

Screen Shot 2021-07-11 at 8.44.28 PM.png

 

And one with:

formatDateTime(addMinutes(utcnow(body('Convert_time_zone')),-30),'yyyy-MM-dd HH:mm:ssZ')

 

Screen Shot 2021-07-11 at 9.00.46 PM.png

 

That said, I think I've narrowed the issue down.

 

I can get it to return true for any timestamp before 1 p.m. EST using something like:

 

formatDateTime(addMinutes(utcNow(),-700),'yyyy-MM-dd HH:mm:ssZ')

 

Anything with a timestamp that starts at 1 p.m. is not being compared to utcNow.

 

Wondering if that can help point us in the right direction?

 

And apologies for the multiple "no luck yet" comments above!

 

 

 

 

 

 

 

Hey all! This is resolved. Thanks for your help working through this with me!

 

When I converted to Eastern I had been using this:

 

formatDateTime(concat(substring(outputs('Compose_2'),0,4),'-',substring(outputs('Compose_2'),4,2),'-',substring(outputs('Compose_2'),6,2),' ',substring(outputs('Compose_2'),8,2),':',substring(outputs('Compose_2'),10,2)),'yyyy-MM-dd hh:mm')

 

I needed to capitalize the hours; this fixed it:

 

...'yyyy-MM-dd HH:mm')

 

THANK YOU again!

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (1,627)