Faulty error about creating a trigger loop?

[Power_Robert]

Hi,

I'm creating a flow which is triggered when a file is created in a Sharepoint Document Library folder:

Root\Input

Somewhere at the end an outpute file is created and saved in:

Root\Output

This setup worked perfectly fine when the trigger was looking at a OneDrive Folder, same folder structure, different service. Now I changed it to SharePoint, I get the error as shown below:

Actions in this flow may result in an infinite trigger loop. Please ensure you add appropriate conditional checks to prevent this flow from triggering itself.

(When I change the Site Address and Folder Path in the orange square, I do not get the error.)

To me this doesn't seem right. The folder is not the same, the Site is, but the folder isn't. Why is this triggering an error?

Thanks your any help.

[Gristy]

That seems like a bug to me, it must not realise that you are using a sub folder and only picking up the library name, which if youw ere of course infinite loop.

Can you put a start condition on and see if it goes away? i.e. a @equals on the folderpath?

[v-litu-msft]

Hi @Power_Robert, 

If your trigger is When a file is created in a folder, and the newly created file is in the other subfolder, the Flow will not be an infinite trigger loop. The notification just a warning, because it detected you are creating a file at the same folder of trigger monitored. You can ignore it if you ensure Flow logic will not infinite a loop.

Or you can create an additional column to avoid an infinite loop for the sake of insurance when a file was created in the Flow, it will create a status to distinguish between files Created in Flow and Created in SharePoint.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Power_Robert]

Hi @v-litu-msft,

Thank you for the explaination. In my opinion it is a bit confusion and not user friendly while the message is also blocking the test button. I would expect an application like MS Flow can figure out itself that is is not the same folder being addressed.

Can you please show me what you mean by creating an "additional column"?

Kind regards,

Robert

[v-litu-msft · Accepted solution]

Hi @Power_Robert,

The addition column means that a column to mark the file created by Flow. There is the Region for instance.

First, when a file is created in a subfolder, then I check it's Region column whether it is NULL. If yes, it means it is not created by Flow, then cocurate the following steps--create a file.

And the file is created by Flow, so after I create the Flow, I should update its properties. I should set its Region as some value to distinguish between file created by Flow and file created by manually.

Then, the Flow won't be an infinite loop and will not appear warning about it.

Please have a try, I hope it can help you.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.