You’re offline. This is a read only version of the page.
I am working with the the http functionality to gather data from a variety of API's to write to Log Analytics. I have one API which requires the ability to handle a 307 redirect (details are below). Currently the Flow errors out at the 307 with a "Temporary Redirect" error. I'm not seeing any options to do http redirect or url forwarding in the http functionality.
Handling 307 redirects
When making REST or REST streaming calls, your product will need to handle 307 redirects. Also known as URL forwarding, a 307 Temporary Redirect response provides a new URL for the browser to resubmit a request.
When a 307 redirect happens, you'll need to make the call again with the new URL information. When you do this, you should cache the host and port number for use in future calls with that user/access token. Remember, each call counts toward the rate limit. Consider how your user is interacting with your product. Some users will press a button or choose a setting repeatedly, so if you make a call for every user action, it can impact rate limits very quickly. If a user makes a series of changes in rapid succession, you should only make an API call for the last (most recent) value.
For more information and an example, see How to Handle Redirects.
I am getting this error like status code 307 "TemporaryRedirect." and i have also added one more action for HTTP and they send other status code 308.
If anybody solve it anyway please let me know.
Thanks for help.
It looks like Nest changed their link to this location: How to Handle Redirects | Nest Developers
Please see the step-by-step blog post I posted using Nest as an example.
@MarkStokes I came across this old post and can't figure out how to get the redirect url from the HTTP get response.
I'm glad that I could help on this one, have a great day!
Thanks @CFullerMVP - I was actually expecting to set the "Run After" IN the HTTP Step.
Configuring it in the following step totally makes sense now!
Thanks for your amazing help 🙂
Mine is using the standard HTTP and I'm doing the Configure Run After on the step after the HTTP request which in my case is a parse JSON. The trigger for mine at the start was just a timed request. Can you see the blog post I referenced where I documented this? (It won't let me post the URL here)
"Run After" is not available for me when using HTTP..
Which trigger are you using for HTTP call @CFullerMVP?
The step after the original query is set the Configure Run After option available by the three dots in the top right corner on the step after the original query. Within that I set it to has failed and it's working for me.
#1
Tomac
986
Moderator
#2
stampcoin
699
Super User 2025 Season 2
#3
Riyaz_riz11
577
Super User 2025 Season 2
Share
Report
All responses (
Answers (