I have created a manually triggered Flow on SP SitePages.
This flow will copy the file in several different site collections' Sitepages libraries.
I have a big issue here :
My Copy File action returns a Status 202, which is equal to "Request Accepted".
I have to precise that these actions are set in a Apply to each loop.The Concurrency Control of this Loop is set to off, because after that loop, I have to send an email with all the actions done inside. I know performance-wise it is not the best...
I would like the next steps to run only when the status returned is 200 (aka OK), with some more info (like ItemID etc..), because I need those in my flow.
Here are some screenshots of my flow :
My trigger :
My Copy file Action :
The Output of my Copy file action :
The settings for my Copy file action (yes, I unchecked Asynchronous Pattern, because I wanted to avoid any strange behavior, because I will use what it returns !.. But still does not work.)
The run after of the next step.
Do you know how I could achieve queuing my next actions until the Copy file returns a 200 Status ?
Do I have to do a Do until loop ? but actually, it won't do anything Until i have the right status.
Do you have any idea on how I could improve the performances of this flow ? (Because copying a SitePage from a site to 23 other sites is really taking a long time.)
Thanks a lot !
Hi @Anonymous ,
For your first question, there is no anyt way in microsoft flow could check the return code, so there is no any way for you to achieve queuing my next actions until the Copy file returns a 200 Status in microsoft flow currently.
For your first question, you could take a try with flow before:
For your third question, I afraid that there is no any way to improve the performances of this flow now.
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @v-alzhan-msft ,
Thanks for your time but your solution won't work :
the Copy file action does not fail nor timeout. It returns something, a status considered as a success, but which did not do anything :
a 202 is only saying "Request accepted, we'll work on it".
So FLow does not see this as a failure. A 400 or 404 is a failure. Not that one.
Do you have any other idea?
Explore the latest innovations, learn from product experts and partners, level up your skillset, and create connections from around the world.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.