API gate way time out Issue

Question

API gate way time out Issue

Revathi Subramaniam 21

Hi,

When run the logic app using API through postman, the gateway has timed out and says 504 gateway timeout.

But logic app is running after getting response in postman.

Could you please help on this how to extend time out in API gateway.
or
how to manage Async using polling?

if we use Async polling then also it will give time out due to API gate way.

Mike Urnun 9,792 Reputation points Moderator

2020-10-23T21:23:42.737+00:00

Hi @Revathi Subramaniam - Could you specify how long your Logic App workflow runs when you get the time-out error? Is it possible that your Postman client's TTL is expiring? In case that's the issue, here's a helpful post on extending the TTL value in Postman: https://stackoverflow.com/questions/36355732/how-to-increase-postman-client-request-timeout
Revathi Subramaniam 21 Reputation points

2020-10-26T08:13:50.023+00:00

Hi Mike,

Logic app runs max 3- 5 mins. while running in postman it got request time out error in 2m 12.54s even though increased request timeout value in postman settings

I am not sure why this is happening.

is there any way to handle this.
Mike Urnun 9,792 Reputation points Moderator

2020-10-26T21:46:20.147+00:00

Thanks @Revathi Subramaniam ! Could you share a screenshot of your LA workflow and elaborate specifically on how API Management Gateway is plugged into your workflow? Does the workflow succeed at the end on the Logic Apps side? I'd try setting 0 (for infinity) for the timeout option in Postman, but even then, I'm also seeing that Postman is aborting the connection at 2min mark which aligns with what you're seeing. I'll post an answer shortly about Async Polling pattern that might help.

2 answers

Your answer

Mike Urnun 9,792 Reputation points Moderator

2020-10-23T21:23:42.737+00:00

Hi @Revathi Subramaniam - Could you specify how long your Logic App workflow runs when you get the time-out error? Is it possible that your Postman client's TTL is expiring? In case that's the issue, here's a helpful post on extending the TTL value in Postman: https://stackoverflow.com/questions/36355732/how-to-increase-postman-client-request-timeout
Revathi Subramaniam 21 Reputation points

2020-10-26T08:13:50.023+00:00

Hi Mike,

Logic app runs max 3- 5 mins. while running in postman it got request time out error in 2m 12.54s even though increased request timeout value in postman settings

I am not sure why this is happening.

is there any way to handle this.
Mike Urnun 9,792 Reputation points Moderator

2020-10-26T21:46:20.147+00:00

Thanks @Revathi Subramaniam ! Could you share a screenshot of your LA workflow and elaborate specifically on how API Management Gateway is plugged into your workflow? Does the workflow succeed at the end on the Logic Apps side? I'd try setting 0 (for infinity) for the timeout option in Postman, but even then, I'm also seeing that Postman is aborting the connection at 2min mark which aligns with what you're seeing. I'll post an answer shortly about Async Polling pattern that might help.

Answer 1

Mike Urnun 9,792 Moderator

Hey @Revathi Subramaniam

Could you clarify the below?

But i am not able to see the location field in logic app trigger body output header section . Hence how i can get Location url in logic app.

You shouldn't need or expect the Location header in the trigger or the response output. URL in the Location header is only made available to the receiving client application (which in this case is a Postman), but typically, the client application is another Webapp, Logic app, or just another application that invokes your trigger and polls the given URL in the Location header of the response to check the status of the long-running job.

The following documentations might be a good read:

For understanding the async patter: Asynchronous Request-Reply pattern
For Logic Apps implementation of the async pattern: Asynchronous request-response behavior

Revathi Subramaniam 21 Reputation points

2020-10-31T09:11:33.043+00:00

Hey @Mike Urnun ,

Thank you.

Answer 2

Mike Urnun 9,792 Moderator

Hello @Revathi Subramaniam

For workflows that take longer, you'll definitely want to use the async polling pattern. This pattern is built into the Response action of the Request connector and can be turned on in the Settings of the connector:

Once Async Polling is enabled, whenever a request comes through, your Logic App will immediately return a successful 202 response back to your Postman client with a Location header containing a URL endpoint that your client can poll to check if the workflow has completed or not:

If you invoke the URL in the Location header in a separate request to check the status of the workflow, you'll notice a status property in the response payload:

In the example, I have a workflow with an HTTP trigger that takes 5mins to complete the workflow. I'm using the Delay action to mimic a long-running job:

After the workflow completes at 5mins mark, Response action returns a successful 200 response and the status should set to completed at the URL endpoint in the Location header.

Mike Urnun 9,792 Reputation points Moderator

2020-10-27T23:37:55.543+00:00

Hey @Revathi Subramaniam - Just checking in here again to see if my answer above helps resolve the issue. Let me know you had any further questions. Thanks!
Revathi Subramaniam 21 Reputation points

2020-10-30T10:07:44.54+00:00

Thank you Mike for your help.

when i run the logic app via postman i could see Location key under header section. But i am not able to see the location field in logic app trigger body output header section . Hence how i can get Location url in logic app.

could you please kindly help on this to get corresponding header url.

Thanks

Share via

API gate way time out Issue

2 answers

Your answer