Unanswered

Approval Flow not triggering consistently!

(0) Share

Report

Posted on by pocketens

Hello I have a several Flows that are not being triggered consistently. Its based upon when someone adds a file to a folder and then an approval is sent. If approved the file is marked as approved, and then it sends a confirmation email to both the approver and the one who created it.

IT ONLY WORKS ABOUT 60% OF THE TIME.

Its very frustrating as I was tasked to create this flow for an enterprise wide project and its really a bad look.

Further information, there are actually about 25 flows that are just slightly modified for each folder and doc library but essentially have the same thing, and are having the same issues.

Any suggestions? Maybe a move to logic apps might resolve this?

Thanks

Categories:

Using flows

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Pstork1 69,547 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

I would try an experiment. Turn off all the flows in that library other than one. See if it still is unreliable. I suspect you have so many Flows with the same trigger that the triggers are stepping on each other. YOu might need to consolidate your flows into one Flow with more complex logic.

Was this reply helpful? Yes No
v-bacao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Could you share a screenshot of the Flow configuration?

You could try to use When a file is created or modified (properties only) as a trigger. Flow can be triggered regardless of which folder the file is added to in the specified library.

If you want to specify the folder path, you could determine in Condition whether the file is uploaded to the specified folder, and if so, perform the following approval process.

Best Regards,

Hi @pocketens ,

Was this reply helpful? Yes No
pocketens 40 on at

Like
a
(0)

Report
Copy link

Link copied!

All of the flows are using that trigger to start.

Was this reply helpful? Yes No
Pstork1 69,547 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

As I said, I think your problem is too many Flows on the same library using the same trigger. Since you mentioned 25 different Flows all running off the same trigger that means 25 instances of that trigger on one document library all trying to fire at the same time. I suspect they are steping on each other and some are getting lost in the congestion. You need to consolidate them down into just a couple of Flows. You can test that theory by turning most of them off and seeing if the reliabilty of the remaining ones improve. If it does you need to consolidate them so you are only using one or two triggers per library. If the Flows are complex one way to do that would be to have the main Flow with one Trigger trigger a flow and then based on logic have that Flow invoke one of the other Flows through HTTP.

Was this reply helpful? Yes No