cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
tomh
Resolver I
Resolver I

Delay Until 2am

Hello All:

 

I have a simple Approval flow that triggers upon recurrence every 3 days. It gets file properties and if file approval=pending it sends email to approver for approval. Our biggest challenge is that users are often in the files needing to be approved. Therefor when the the approver approves and the flow tries to update the file properties to 'Approve' it cannot do so because the file is locked for editing. The flow continues and errors but the approver is not aware of the fact that the file properties have not been updated. Then again on the third day they receive an email for approval of the same file because the properties are still=pending becuase the file was locked for editing and the metadata could not be updated on previous attempt. I have worked with this flow for months now and have tried just about everything. The only thing I have left is to try to add some kind of delay function into the flow to update the file properties at a specific time when the least amount of users are potentially in the file, say 2am. 

 

I am open to options here. I have not been able to successfully implement a delay in such a way that would only update at 2am. The closest I have been able to get is to delay updating for a given amount of hours say 10 hours. This presents a problem as well as hours of business are roughly between 6am and 6pm. So even if an approver approves at 6am sharp the metadata would then be updated at 4pm, which still falls between our business hours thus potentially leaving the file locked for editing. 

 

Any help or suggestions would be greatly appreciated.

 

Thanks all!

 

Tom

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
tom_riha
Most Valuable Professional
Most Valuable Professional

Hello @tomh ,

to delay until 2am the next day you can use the following expression inside 'Delay until' action.

addHours(utcNow('yyyy-MM-dd'),26,'yyyy-MM-ddTHH:mmZ')

utcNow('yyyy-MM-dd') will give you today's date at 00:00, to which you use the addHours() expression to add 26 hours to get tomorrow 2am and format it as 'yyyy-MM-ddTHH:mmZ' to fit the requirements of the 'Delay until' action.

image.png

 



[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]

View solution in original post

22 REPLIES 22
Anonymous
Not applicable

@tomh ,

 

You could calculate how many hours are between utcNow() and 2am tomorrow and have the flow delay for that amount of time:

 

the flow in the below screenshot does the following:

 

1. Converts the current time in UTC (Universal Coordinated Time) to local timezone and returns only the Hours number (from a 24-hour format, so 1:00PM=13).

 

2. subtracts the current hour from 26 and returns that figure. 26 is the number of hours there are from 00:00 on day one to 0200 (2:00AM) the following day. this calculation determines how many hour there are from right now to 0200 tomorrow morning.

 

3. delays the flow for that many hours

DelayFlow.png

 

the expressions that you need are in the action block comments in the screenshot.

 

 

I hope this helps!

 

thanks,

Kyle

Is there a reason that I am not understand that you cannot just use the delay until action?

 

DelayUntil;.PNG

tom_riha
Most Valuable Professional
Most Valuable Professional

Hello @tomh ,

to delay until 2am the next day you can use the following expression inside 'Delay until' action.

addHours(utcNow('yyyy-MM-dd'),26,'yyyy-MM-ddTHH:mmZ')

utcNow('yyyy-MM-dd') will give you today's date at 00:00, to which you use the addHours() expression to add 26 hours to get tomorrow 2am and format it as 'yyyy-MM-ddTHH:mmZ' to fit the requirements of the 'Delay until' action.

image.png

 



[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]
Anonymous
Not applicable

It looks like I like doing things the hard way... @Paulie78  and @tom_riha 's solutions are much more simple and elegant.

@Anonymous don't feel too bad about it. I came up with an elaborate solution also, which I think is quite neat! That is when I noticed delay until 😥

@tom_riha 

Thank you for this. Are you saying that utcNow always returns time of 00:00? So, adding any hours to that figure will always update at set time regardless of whether the approval occurs at 7am or 3pm?

 

tom_riha
Most Valuable Professional
Most Valuable Professional

@tomh 

Expression utcNow() without parameter returns date and time when the action was executed = now. But you if you add a format parameter where you ignore the time part utcNow('yyyy-MM-dd') it'll give you 00:00 time.



[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]

Does this look correct?

Rhia.JPG

tom_riha
Most Valuable Professional
Most Valuable Professional

Yes, that looks just fine. 🙂



[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]

@tom_riha 

Thank you again for this. I will test now and report back the success. 

 

Tom

tomh
Resolver I
Resolver I

@tom_riha 

Hello.

 

The flow did not work as expected.

The flow was manually triggered at 1:09pm on 11/6 as a test on four files added to SharePoint. The flow proceeded to update the file properties at 9:00pm on the same day. The intended result was to update file properties at precisely 2:00am. The delay until input value shown on the successful run shows 'Delay Until 2020-11-07T02:00:002.

 

Any thoughts on why the flow updated the file properties at 9:00pm instead of at 2:00am?

 

Thanks!


Tom

 

Anonymous
Not applicable

@tomh ,

 

my first thought would be to check the TimeZone.

 

In your screenshot above, you're adding the number of hours required to get from utcNow() (when the flow was triggered) to 2:00AM UTC.

 

If you're in Eastern Time, that means the flow is going to wait until 9:00PM EST.

 

You can either manually adjust your expression to account for the timezone difference (note that this will not account for DST next spring), or you can use the Convert TimeZone action block and pass in your addHours() expression.

 

thanks,

Kyle

@Anonymous 

Thank you for this. Yes we are on EST and want the flow to execute the 'Update File Properties' at precisely 2:00am the following day. Can you provide the formula for this by chance?

Thanks!


Tom

tom_riha
Most Valuable Professional
Most Valuable Professional

Hello @tomh ,

that could be a difference in a timezone. What account is running the flow? What timezone it has configured? I'm not sure but it could be user specific.

Edit: I just did a few tests and it expects time in UTC timezone, so you'll need to adjust the time as @Anonymous already suggested.



[ If I have answered your question, please Accept the post as a solution. ]
[ If you like my response, please give it a Thumbs Up. ]

[ I also blog about Power Automate solutions even for non-IT people. ]
Anonymous
Not applicable

@tomh ,

 

I would suggest attempting one of the solutions that I suggested, and then request assistance if you're unable to get either (or both) to work.

 

You've been given the expression that will get you want you want, you just need to adjust it to meet your specific needs.

 

thanks,

Kyle

Hello @Anonymous 

 

Maybe I'm misunderstanding what has been provided as the initial expression. I have control over when the flow is triggered but do not have control over when the approval is completed. The 'Update File Properties' action is the step that I believe I need to address here and that is dependent on when the actual approval is executed. I have no control over when the approval action is executed and so simply adding hours in the form of a delay will not achieve what I need if I apply it to when the approval is executed. I need a set value I believe irrelevant of when the approval is executed to update file properties at 2:00am EST only.

Does that make sense?

 

Or is it as simple as adding 6 hours to the 26 hour value to get to 2:00am? 

Anonymous
Not applicable

@tomh ,

 

Yes, that does make sense; and I understand where you're coming from and that it seems counter-intuitive to be adding a set number of hours when you don't know WHEN the approval will be executed (i.e. you don't know the value of "utcNow()" [ remember that utcNow() returns the current time in UTC timezone] ).

 

what @tom_riha's solution does is help you calculate how many hours are between:

 

1. The time that the flow runs AKA the "current" time AKA the value of the expression utcNow()

 

and 

 

2. the next occurence of 2:00AM (let's agree to call it 2:00AM tomorrow morning since we'll assume that the flow is executing "today")

 

To calculate that time gap we need to know both of those points in time.

 

The first one is easy: the expression utcNow() returns that exact value. If the flow executes today at 12 noon UTC, the value of utcNow() will be 2020-11-09T12:00:00Z (utcNow() is a datetime value, hence why it has the date in it also). Keep in mind that UTC is five hours ahead of EST so when the value of utcNow() is 12pm (noon), it's actually 7:00AM EST.

 

The second point in time is a little more tricky to figure out, but it involves finding a concrete reference point from which we can calculate when (in how many hours) 2:00AM tomorrow morning will occur. @tom_riha's expression above does just that by using a starting point of 00:00 this morning, the beginning of the day, by taking utcNow() and removing the time component; this effectively reduces the time component to 00:00 as he explained above. So, now, it doesn't matter when utcNow() is; the above expression will always return 00:00 (i.e. midnight) this morning.

 

Since 2:00AM tomorrow morning will always be 26 hours after 00:00 this morning, we can add 26 hours to 00:00 this morning to get the datetime of 2:00AM tomorrow morning.

 

HOWEVER!

 

Remember that all of the numbers we just crunched are based on utcNow() which returns the datetime in the UTC time zone. With no adjustments, the above calculations will return datetimes five hours EARLIER for each of the calculated values. So, if the flow was run at noon today UTC, you'd get the following values in for the respective time zones:

UTC (desired):

utcNow() = 2020-11-09T12:00:00Z

utcNow('yyyy-MM-dd') = 2020-11-09T00:00:00Z

addHours(utcNow('yyyy-MM-dd'),26,'yyyy-MM-ddTHH:mmZ') = 2020-11-10T02:00:00Z

 

EST (actual):

utcNow() = 2020-11-09T07:00:00Z

utcNow('yyyy-MM-dd') = 2020-11-08T19:00:00Z

addHours(utcNow('yyyy-MM-dd'),26,'yyyy-MM-ddTHH:mmZ') = 2020-11-09T21:00:00Z

 

 

If that makes sense, then it's clear now that an adjustment has to be made to the value that is being passed into the Delay Until action block.

 

Either you can add five hours to the "26" in the expression above, OR, you can pass that expression into a Convert Time Zone action block and pass the output of that into the Delay Until.

 

Does that makes sense?

 

thanks,
Kyle

@Anonymous , @tom_riha 

 

I'm still not sure we are on the right path...the GetUTCNow with the formatting applies to when the flow was triggered correct? I think I need to apply the Get UTCNow to when the approval occurs and set specific value vs setting in relation to when the flow was triggered. No? Because it could be 2 hour or two days before the approval step is completed and if the Get UTCNow applies to when the flow is triggered rather than when the approval occurs then the file update could happen prematurely, correct? If the GetUTCNow is nested below the Condition, would it pull the UTC of when the approval occurs or the UTC of when the flow initially triggers?

THx all!

 

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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 (4,034)