Resolving HTTP 504 timeouts during high-volume telemetry REST API & webhook syncs
Hello ST Community,
We are optimizing background listener stability and remote webhook payload handling when integrating embedded telemetry data into enterprise management pipelines.
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 TCP keep-alive settings or queue worker retries to prevent connection drops during high-volume sensor/telemetry data syncs?
Any advice on managing asynchronous background worker threads would be appreciated!
Thanks!
