Microsoft Flow with File Created Action is not triggered all the time

[sibeeshvenu]

I have one drive synced local folder and the files will be synced with a SharePoint site when we add files to this folder. I also have a Flow that gets triggered for every file added.

The complete flow and details can be found here in this article.

The t problem is that it is not triggered all the time. Let's say I added 100 files and the Flow triggered only 78 times. Are there any limitations on the Flow that it can run only this many times in a timeframe? Anyone else faced this issue? Any help is really appreciated. #sharepoint #sharepointonline #flow #onedrive

[Jcook]

Hello @sibeeshvenu 

Which trigger are you using?

Depending on the trigger you can try turning on concurrency, this can be done by clicking the 3 dots on our trigger, click settings and turn on Concurrency/parallelism.

set the value to 50.

NOTE:

Be aware that once you turn on Concurrency, you cannot turn it off (depending on the trigger)

[sibeeshvenu]

Hello, @Jcook Thanks a lot for your response. I have updated my question. Please have a look. Are you saying that I should enable this Concurrency Control on for the trigger "When a file is created"?

[sibeeshvenu · Accepted solution]

Thanks, @Jcook for giving the right direction.

Finally, after spending a few hours, I got it working with 120 files at the same time. The flow runs smoothly and efficiently now. Here is what I did.

Click on the three dots on your trigger in the flow, and then click on settings.

Now in the new screen, enable the Split On (Without this my Flow was not getting triggered) and give the Array value. Clicking on the array dropdown will give you the matching value. Now turn on the Concurrency as shown in the preceding image and give the Degree of Parallelism to maximum (50 as of now).

According to Microsoft:

Concurrency Control is to Limit the number of concurrent runs of the flow or leave it off to run as many as possible at the same time. Concurrency control changes the way new runs are queued. It cannot be undone once enabled.

[sibeeshvenu · Accepted solution]

Thanks, @Jcook for giving me the right direction.

Finally, after spending a few hours, I got it working with 120 files at the same time. The flow runs smoothly and efficiently now. Here is what I did.

Click on the three dots on your trigger in the flow, and then click on settings.

Now in the new screen, enable the Split On (Without this my Flow was not getting triggered) and give the Array value. Clicking on the array dropdown will give you the matching value. Now turn on the Concurrency as shown in the preceding image and give the Degree of Parallelism to maximum (50 as of now).

As per Flow documentation:

Concurrency Control is to Limit the number of concurrent runs of the flow or leave it off to run as many as possible at the same time. Concurrency control changes the way new runs are queued. It cannot be undone once enabled.