Unanswered

Trigger is not always triggered

Like (0) Share

Report

Posted on 6 Jul 2023 10:16:09 by CU05080900-1

Good day,
I have a flow that is triggered by storing files in a sharepoint.
Now it can happen that 200 files are stored in the sharepoint at the same time. In this case it happens that the flow does not offer all files and sends them by mail. Sometimes 50 remain, sometimes 30 or less. If files are uploaded individually, it cuts out. How can you manage such a mass upload? I was thinking of waiting 5 minutes when the first file is declared and then triggering the actual flow.
The flow should distribute the files by mail according to specifications.

All responses (2)

Answers (0)

VictorIvanidze 12,538 on 11 Jul 2023 at 09:42:39

Like (0)

Report

Re: Trigger is not always triggered

Please show your trigger options.
Unknown geen idee 1,755 on 11 Jul 2023 at 09:36:30

Like (0)

Report

Re: Trigger is not always triggered

Dear Andy,

In the past when I faced a similar problem (triggers did not always trigger), I changed the trigger to a 'Re-occurence' trigger. For example to run every 30min.
Then the flow would get all the files via a 'List items in folder' or something similar and compare the output with a central file of previously processed files. Files not in the list would get 'processed' further as per actions you decided.
You could even considered moving 'processed' files to a different folder.

I know this may be a bit more complicated than the 'Trigger when file created', but it should prevent you from missing anything in high volume.

Hope the suggestion helps,
Happy flowing,
Koen