cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
asmith2
Frequent Visitor

item modified flows skipping

Hey everyone!

 

I have a powerapp being used for requests inside the company. There's an edit record lock that engaged in order to keep more than one person from accessing the record. I'm trying to create a flow to email when someone changes the status and/or comments of an item. The process goes like this:

 

• person hits edit record -> app patches to list { in edit: "yes"} {edit person: current user}. 

• person saves their changes -> app submits form 

• on success of form -> app patches to list {in edit: ""} {edit person: ""}

 

The problem is that these events happen very close together sometimes. So the flow doesn't seem to pick up each trigger. From some tests, if they happen too close together, it will pick up the first trigger from the patch, and the last trigger, also from the patch. But it doesn't seem to pick up the trigger in between, when the form was submitted. This results in status change = false. Because the change happened before the second patch. Which means no emails to the employee. 

 

Is there something I could do to keep this from happening? Perhaps a separate flow when the edit record is enabled?

1 ACCEPTED SOLUTION

Accepted Solutions
Kcronic1
Community Support
Community Support

Hello @asmith2 ,

 

In reviewing your post I understand that you are having issues with the actions of your flows happening too soon causing issues with the triggering of the next flow. 

 

I would suggest using delays of about 2 min at the end of your actions to see if this will allow time for the update to fully complete. 

 

Here's a link to the delay action in Power Automate: Use wait conditions to delay flows - Power Automate | Microsoft Docs

 

Hopefully this helps! 🙂

 

Regards,

Kristie

Community Support Team

 

If this post helps, then please click on the "Accept it as the solution" to help the other members find it more quickly.

 

If you would like to create a ticket with Microsoft Customer Support here is a link on how to do so: Get Help + Support - Power Platform | Microsoft Docs

View solution in original post

1 REPLY 1
Kcronic1
Community Support
Community Support

Hello @asmith2 ,

 

In reviewing your post I understand that you are having issues with the actions of your flows happening too soon causing issues with the triggering of the next flow. 

 

I would suggest using delays of about 2 min at the end of your actions to see if this will allow time for the update to fully complete. 

 

Here's a link to the delay action in Power Automate: Use wait conditions to delay flows - Power Automate | Microsoft Docs

 

Hopefully this helps! 🙂

 

Regards,

Kristie

Community Support Team

 

If this post helps, then please click on the "Accept it as the solution" to help the other members find it more quickly.

 

If you would like to create a ticket with Microsoft Customer Support here is a link on how to do so: Get Help + Support - Power Platform | Microsoft Docs

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Top Solution Authors
Users online (3,081)