HTTP 504 timeouts during high-volume API & webhook syncs

flsc

Hello GoTo Community,

We are testing background listener stability and remote webhook payload handling when integrating GoToConnect VoIP endpoints into automated management 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:

1. Under heavy concurrent load spikes, background POST webhook listener sockets occasionally report HTTP 504 gateway timeout responses before acknowledging payload completion.
2. Direct REST API requests to the same remote host resolve normally under 150ms thresholds.
3. Are there recommended network socket keep-alive settings 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!

Eric_S

I do not understand the issue. What are you referring to as "background POST webhook listener sockets"? Are you referring to the Notification Channels API with the websocket implementation? Please explain the use case and expectations a bit clearer and I will try to answer them.