Forum Discussion
Sergento79
May 09, 2024Copper Contributor
Unexpected error. Unable to fetch
I have a flow in Power Automate. The last step is to write items to a list in SP after changes/updates are detected and made. So it will write up to 50 items without any issues. If above 50, it could 52 or 450, the last step will hang when only 4-5 items left to write. so if 250, it will stop at 247 or 248, if 500 it will stop at 496 or something like that.
Before it fails completely I get this error while 99% of the records are written
then this what I see when the Run fails
- ArefHalmstrandSteel ContributorAre you able to provide more information about your Power Automate solution?
What is the trigger, what type of data do you collect and how do you collect it?
When you run for each (I see you have three loops). What do you do within each for-each loop?
There seems to be conditions used, what are the conditions for the flow to continue?- Sergento79Copper ContributorThank you for replying.
I will try to answer to the best of my ability, as I am new at this and followed a video.
The trigger is Manual Run or Test flow
The data is in Excel sheet all columns are single lines of text except the date column. And I used ISO 8601 for date format. It uses Intersection Var Array to see if Item is there and writes it to list. I will watch the video again on the explanation and hope to come up with a better answer to your questions. btw the video is on youtube if interested https://www.youtube.com/watch?v=aNoPNcXIg08&t=10s Date format is the only thing I did not incorporate in my flow as it worked by changing it to ISO 8606 in list rows present in table.
I just dont understand why everything works as intended if under 50 items. And it still writes 95% if over 50.- ArefHalmstrandSteel ContributorHello again,
Thank you for the detailed description. This video seems to be a part 2 out of 3. Are all three videos released? have you followed them as shown in the video, or have you made any customizations?
Is there a reason you would like to work in Excell first and then have a script to update it in SharePoint Online? Because, if you could consider working from SharePoint first, there is a standard function to export to Excell.