Unanswered

Getting "MovedPermanently" error with status code 301

Like (0) Share

Report

Posted on 17 May 2018 03:50:55 by nitishbijalwan

Hi Team,

I am getting "MovedPermanently" error with status code 301 on calling SharePoint HTTP to get items from the list. I am passing $filter option in the call. The Postman is returning the data, while Flow is throwing error.

Any idea when does flow throws "MovedPermanently" error and how to resolve it?

image (1).png

All responses (2)

Answers (0)

nitishbijalwan 11 on 24 May 2018 at 03:28:50

Like (0)

Report

Re: Getting "MovedPermanently" error with status code 301

Thanks Kris for replying. I am using a loop which iterate over a collection of list ids, but this flow is failing only for a paticular list id.
I have created a new flow with same functionality but now having only that list and its working fine in that case.
Now I have to maintian 2 flows to perform same actions 😞
v-xida-msft on 18 May 2018 at 09:30:46

Like (0)

Report

Re: Getting "MovedPermanently" error with status code 301

Hi @nitishbijalwan,

Could you please show a bit more about the Uri that you specified within the "Send an HTTP request to SharePoint" action?

The 301 "MovedPermanently" error told that the requested resource has been permanently moved to a new URL provided by the Location response header. More details about the HTTP 301 error, please check the following article:

https://blogs.msdn.microsoft.com/tijujohn/2012/05/31/different-redirect-http-response-status-codes-and-how-the-browser-should-reacts-301-vs-302-vs-303-vs-307/

I have made a test on my side and don't have the issue that you mentioned. My flow's configuration as below:

The flow works successfully as below:

Please check if you have provided proper Uri within the Uri field of the "Send an HTTP request to SharePoint" action. In addition, please take a try to clear cache of your browser and re-create your flow to check if the issue is solved.

Best regards,

Kris