@Deepesh Kalura, based on the info you have shared; I see that your webapp Healix-backend.azurewebsites.net shows - HTTP 504 error, which usually indicates timeout.
Checking internally, I see that most of the HTTP 504 are failing after 240 seconds.
Azure Load Balancer has a default idle timeout setting of four minutes, it is the maximum amount of time that a request can take without sending any data back to the response. It is not configurable. Kindly checkout the following approaches to overcome this issue:
A. Optimize code to finish execution within 240 seconds or send some data back at regular intervals to keep the connection alive.
B. If sending data back to keep connection alive is not feasible, consider using async pattern.
That is:
- First request starts with the script and returns an HTTP 202
- Subsequent requests from clients check the progress, and eventually return 200 when it's done.
C: Leverage background processing for long running tasks.
Please checkout this example: Azure Web Jobs
FAQ: Why does my request time out after 230 seconds?
https://learn.microsoft.com/troubleshoot/azure/app-service/web-apps-performance-faqs#why-does-my-request-time-out-after-230-seconds
It looks like Always On
is not enabled.
- Please enable it from Azure Portal – Your WebApp > Configuration blade (> General settings).
To fetch more details about the issue, you may try these:
3. You may leverage App Service diagnostics from Azure Portal> Navigate to your App Service app in the Azure Portal -to fetch more info
https://learn.microsoft.com/azure/app-service/overview-diagnostics
4. If the issue still persists, by default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the WEBSITES_CONTAINER_START_TIME_LIMIT
app setting.) (up to a maximum of 1800)
Kindly let us know, I'll follow-up with you further.