503 XAS error in the browser on On-Prem deployed app

There are multiple XAS calls taking place from the page. But at random, when the page loads, some XAS calls fails with response <TITLE>Service Unavailable</TITLE> </HEAD><BODY> <H1>Service Unavailable - Zero size object</H1> The server is temporarily unable to service your request. Please try again later.<P> The microflows that these XAS are calling are quite straight forward and cannot result into error as there is nothing complex going on there.  There is nothing related to this on Mendix Server Logs.  I enabled the log node to debug and working with DevOps team to monitor the network layers, but apart from this, what should be the best debug approach here?
1 answers

Hi Romil!

  I can confirm that the 503 error is not being served up from the Mendix Runtime. So when you see ‘Zero sized object’ that is unrelated to Mendix objects. That’s a bit of a red herring here. If the XAS calls are working some of the time, then perhaps there is some type of thread/throttling occurring within the on-prem network that is preventing traffic from getting through?