You’re offline. This is a read only version of the page.
231
Hi,
I am using a automated Power Automate flow and Powerapps. Users have to fill out an approval form within the app, once they complete it, they hit submit. The submit button sets the column "Verifier Response" to "Yes".
The flow should wait until the "Verifier Response" column updates to "Yes" to proceed to the next set of actions in the flow.
I left the approval pending to test and within an hour, the workflow ended. How can I set up the Do Until condition to keep running until the "Verifier Response" column is set to "Yes"? And how can I set up the Do Until condition to proceed to the next step as soon as the condition is satisfied?
Here is what my power automate flow entails:
Update
Delay was set to 10 minutes
Timeout is still for 30 days
Count was 120 times.
I did not respond to the approval task for over 24 hours. The variable within the 120 instances it ran, was showing "No". However, the workflow ended at the 120th instance.
So I must need to increase the instances and the delay perhaps to see this stay activated for the 30 days unless an approval is submitted.
Thoughts on what I should change?
It should be but for testing it is fine, in production I would alow 10 minutes.
Come back to me once you have tested it. But do not forget to update the item on the result being YES.
Let me know how you get on, I would rather your test stuff than have a single issue ot resolve everytime.
Regards,
Andrew
Hi,
So I have set the Verifier Response column with a default value of No. The Do Until flow should run until it is yes.
My delay was set to 2 minutes, should I make the delay more?
Looking at the above then you are wanting to run the DO UNTIL every three hours. But even with this it still fails after 8 hours. What was your delay set to.
I am not doughting you but could it be down to the following:
Is the above correct. have you used a choice column in the SP List that has a default value of No, could this not be a plain text field with nothing in it. I am getting near to the end of my knowlege maybe @grantjenkins could assit as he did before.
Regards,
Andrew
So does this look correct:
Originally I also tried 240 count with a 30 day timeout and the workflow ran for 8 hours and then it ended.
I hope the below will help:
https://powerusers.microsoft.com/t5/Building-Flows/Delay-Until-Issue/m-p/2002433#M220810
I needed help to understand the timing etc. I put the above into place and it worked a treat in the end.
Regards,
Andrew
#1
Michael E. Gernaey
566
Super User 2025 Season 1
#2
David_MA
516
Super User 2025 Season 1
#3
stampcoin
492
Share
Report
All responses (
Answers (
