162
Views
5
Comments
Solved
Error 504 Gateway Timeout on Traditional REST API call

Hello


I am maintaining a traditional web application where i consume slow API's.

We have a case of very slow BE systems and this seems to cause timeouts in our rest api calls.

The problem is we are getting these timeouts at around 35sec of waiting. And I can not pinpoint why at 35sec exactly. I have set the timeouts to occur at 500sec. This is too much but i want to trigger it so it just stay longer. Im expecting it around 120-150sec


Where can I change this 35 sec to a longer timeout period?

Do take note that it is a traditional web app and Service Center is Version 11.0.615.0 .

Can anyone shed some light on this?


EDIT: Most likely like Vikas said it is a server issue since I am having these timeouts in the swagger testing zone aswell. 


Thanks in advance!

Kind regards


UserImage.jpg
vikas sharma
Champion
Solution

Also if possible you can call the same API from postman client. If postman also have same 35 seconds timeout, then it confirms its due to server's responsiveness and there is no fault in your application's code.


UserImage.jpg
vikas sharma
Champion

Hi,

There is one possibility that called server (on which apis are hosted) have timeout of 35 seconds. Means once you request using API server is not able to deliver the response in 35 seconds and then it return timeout. So I think you can check this at API server end also.

regards

2025-08-01 13-50-51
Simon Vandersmissen

Hey 

Thank you for the quick response. So I am still looking perhaps for other reasons.

I guessed the same but they claim it is not :) I don't have access myself.

UserImage.jpg
vikas sharma
Champion

You can find out many articles on Google for this error. All suggest that its because server is not able to respond in time.

regards

UserImage.jpg
vikas sharma
Champion
Solution

Also if possible you can call the same API from postman client. If postman also have same 35 seconds timeout, then it confirms its due to server's responsiveness and there is no fault in your application's code.


2025-08-01 13-50-51
Simon Vandersmissen

Thank you Vikas. As time went on it was apparent that it was the case!

Thank you for your time

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.