Forum Discussion
HTTP 504 timeouts during high-volume API and webhook syncs
Hello Microsoft Tech Community,
We are testing background listener stability and remote webhook payload handling when integrating enterprise Azure telemetry endpoints into automated systems.
Technical Setup:
Our integration architecture at Frontline Sales Consultancy (flsc.co.uk) triggers automated B2B notifications and REST API syncs over HTTPS (TLS 1.3).
The Issue We're Facing:
Under heavy concurrent load spikes, background POST webhook listener sockets occasionally report HTTP 504 gateway timeout responses before acknowledging payload completion.
Direct REST API requests to the same remote host resolve normally under 150ms thresholds.
Are there recommended network socket keep-alive settings, Azure App Service timeout adjustments, or queue worker retries to prevent connection drops during high-volume data syncs?
Any advice on managing asynchronous background worker threads would be appreciated!
Thanks!
1 Reply
Seems backend services exceed the configured timeout thresholds or connections idle out, may consider adjusting Application Gateway/App Service timeout settings, using queue-based background workers (WebJobs/Functions), and enabling retries with keep-alive to stabilize high-volume integrations.
https://learn.microsoft.com/lb-lu/troubleshoot/azure/app-service/web-request-times-out-app-service