Solved: Double status on each run (Cancelled and Succeeded...

Anonymous · ‎06-17-2021

Hello,

I am trying to create a folder approval flow so that when a sub-folder is added to my Pre-Approved folder, a request is sent out so that the contents can be viewed for approval or rejection. Right now my flow is running correctly and doing what it should, but I am also getting both a cancellation and a successful run notification in my history. I've attached photos of my flow below.

Thank you,

Nick

Flow 1.PNG

Flow 2.PNG

Flow 3.PNG

Flow 4.PNG

ccc333ab · ‎06-21-2021

I believe you are using the correct trigger (although I may use created only vs. created and modified so that it doesn't fire when things are updated). However, due to the nature of this trigger, it will always produce this issue.

Would you have a naming convention on your folders you want to trigger this flow upon? If so (or if you can create one), you can then use a trigger condition that will only fire for those specific folders as such:

1. Click on the settings for your trigger action.

2. Put in some type of trigger condition...in my example below, if the folder name has the word "Main" in it, triggeer the flow.

Or there is any number of trigger conditions you could use if you can use a naming convention, but I can't think of anything better for your situation.

View solution in original post

ccc333ab · ‎06-17-2021

The reason for the double run is that "When a file is created or modified (properties only)" will actually trigger even if you add items into the subfolders. So in your case:

You add your new folder and flow runs successfully
You add a file into that subfolder, and the flow runs and then termiates based on your logic

I just created a test with that trigger and tested this and it behaved exaclty as such. (I even created several subfolders and added many files in those subfolders and the flow triggered with every folder, subfolder and file created).

Anonymous · ‎06-21-2021

So should I not be using "When a file is created or modified (properties only)" and be using something else? Or is there something I could put before or after this function that will help solve the problem?

Thanks

ccc333ab · ‎06-21-2021

I believe you are using the correct trigger (although I may use created only vs. created and modified so that it doesn't fire when things are updated). However, due to the nature of this trigger, it will always produce this issue.

Would you have a naming convention on your folders you want to trigger this flow upon? If so (or if you can create one), you can then use a trigger condition that will only fire for those specific folders as such:

1. Click on the settings for your trigger action.

2. Put in some type of trigger condition...in my example below, if the folder name has the word "Main" in it, triggeer the flow.

Or there is any number of trigger conditions you could use if you can use a naming convention, but I can't think of anything better for your situation.