196
Views
4
Comments
502 (Bad Gateway) error after 40 seconds even though timeout set to 3 minutes
Question

Hi

I am getting a 502 (Bad Gateway) error after 40 seconds even though the server timeout is set to 3 minutes. Why is it not allowing the full 3 minutes before failing? There is a lot of data being pulled and so it is expected to take some time which is why I made it 3 minutes. I read that it is not always about the server but also about the proxy but not sure how this works and how I can fix it in OutSystems.

Thanks

2022-11-02 07-18-33
Nicholas Campbell

This is for a Screen Aggregate specifically.

2022-11-02 07-18-33
Nicholas Campbell

Getting the following messages in the Service Center error log. But as I said, they are not waiting for the full server request timeout which is 3 minutes,

- Error executing query. Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. 

and

- Request failed with status 502 

2022-11-02 07-18-33
Nicholas Campbell

This question has been logged with OutSytems and they are looking into it. I have some feedback already and when I get final answers will share the findings so others who get this in future can learn from it.

2022-11-02 07-18-33
Nicholas Campbell

In conclusion, it was an infrastructure issue and not an OutSystems issue. 

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