I have created flow which ideally writes 500-1000 rows of data in an excel which is kept in centralized sharepoint/onedrive. This flow has been shared with around 600 users and this flow is scheduled to run everyday 8am. The problem is Excel going as Not responded and flow got timeout. I am guessing that since all the flows trying to write the data in almost same time, I am facing this issue. Kindly advice me on the approach. I can't have different excels for all the users.
MMm... it looks like a concurency problem. So, all these 600 users already installed you flow and invokes your flow simoultaneously, right? Or, does it run only once a day, but it creates/updates so many rows the file get blocked during the process?
If so, did you consider an alternate architecture? Sharepoint? CDS?
Did you consider an hybrid approach?
Sharepoint to avoid concurrency problems; you flow should store daily related data there.
Once a day you can backup daily data from SP to an Excel, and delete Sharepoint old entries. So Excel to avoid too many rows on SP.
Anyway, it is difficult to say, I am just guessing you are implementing some sort of COVID report per employee/patient. IN such a case I would try with this hybrid approach. But if your flow that is executed by 600 users at the same time need to process old data, then my suggestion is nonsense.
Hope this helps
Yes it is going to be triggered by all the 600 users same time. But there will be small difference in time based on dataset.
Is SharePoint has a concurrency issue?
Check out new user group experience and if you are a leader please create your group
On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks
Check out how to claim yours today!
Test your skills now with the Cloud Skill Challenge.