Agent-Level Webhook Request Aborting Within Timeout While in Transit

Support Help
1

We are experiencing an issue where the agent-level webhook request from Retell is being aborted while the request is still in transit to our production server. this issue is generally noticed when the webhook payload is huge usually for the call duration frames of more than 10 minutes.

Our server logs show that the request remains open for approximately 30 seconds, which corresponds to the webhook timeout configured for the agent. The request is aborted when this timeout is reached, before the complete webhook payload has been received and processed.

Sample Call ID where such issue was faced: call_de1caffef2769f765a4a2a21109.

Below are the redacted logs from our server where it says that request was aborted.

[INFO	19-08-2026 05:24:04.88] [SERVER.JS @     1] Request from: /chatbot-channels/retell/response-webhook req.method: POST cluster id: 1
[INFO	19-08-2026 05:24:04.88] [SERVER.JS @     1] [REQ_START] {"method":"POST","url":"/chatbot-channels/retell/response-webhook","httpVersion":"1.1","contentLength":"151106","transferEncoding":null,"connection":"close","host":"xxx","userAgent":"axios/1.15.2","xForwardedFor":"xxxx","xRealIp":"xxxx","xForwardedProto":"http","remoteAddress":"xxxx","remotePort":xxx,"worker":1,"pid":30}
[INFO	19-08-2026 05:24:04.88] [SERVER.JS @     1] Request from: /chatbot-channels/retell/response-webhook req.method: POST cluster id: 1
[INFO	19-08-2026 05:24:04.88] [SERVER.JS @     1] [REQ_START] {"method":"POST","url":"/chatbot-channels/retell/response-webhook","httpVersion":"1.1","contentLength":"150655","transferEncoding":null,"connection":"close","host":"xxx","userAgent":"axios/1.15.2","xForwardedFor":"xxx","xRealIp":"xxx","xForwardedProto":"http","remoteAddress":"xxx","remotePort":36048,"worker":1,"pid":30}


[ERROR	19-08-2026 05:24:34.51] [SERVER.JS @     1] [HTTP_CLIENT_ERROR] {"code":"HPE_INVALID_EOF_STATE","message":"Parse Error","bytesParsed":0,"rawPacket":null,"remoteAddress":"xxx","remotePort":36048,"localAddress":"xxx","localPort":3008,"socketBytesRead":0,"socketBytesWritten":0,"destroyed":false,"worker":1,"pid":30}
[ERROR	19-08-2026 05:24:34.51] [SERVER.JS @     1] [REQ_ABORTED] {"method":"POST","url":"/chatbot-channels/retell/response-webhook","elapsed":29632,"expectedBytes":150655,"receivedBytes":21420,"complete":false,"readableEnded":false,"destroyed":true,"socketBytesRead":0,"socketBytesWritten":28,"remoteAddress":"xxx","remotePort":36048,"xForwardedFor":"xxx","xRealIp":"xxx","worker":1,"pid":30}
[INFO	19-08-2026 05:24:34.52] [SERVER.JS @     1] [RESP_CLOSE] {"method":"POST","url":"/chatbot-channels/retell/response-webhook","elapsed":29637,"status":400,"writableFinished":true,"headersSent":true}
[INFO	19-08-2026 05:24:34.52] [SERVER.JS @     1] [REQ_CLOSE] {"method":"POST","url":"/chatbot-channels/retell/response-webhook","elapsed":29637,"complete":false,"destroyed":true,"receivedBytes":21420,"socketBytesRead":0,"socketBytesWritten":28}
[ERROR	19-08-2026 05:24:34.52] [SERVER.JS @     1] [HTTP_CLIENT_ERROR] {"code":"HPE_INVALID_EOF_STATE","message":"Parse Error","bytesParsed":0,"rawPacket":null,"remoteAddress":"xxx","remotePort":36046,"localAddress":"xxx","localPort":3008,"socketBytesRead":0,"socketBytesWritten":0,"destroyed":false,"worker":1,"pid":30}
2

Hello @Streebo_DEVTEAM Thanks for sharing your Call ID. Let me check this with the team, and I’ll get back to you with an update.

Thank You

3

Hello @Streebo_DEVTEAM 30 seconds generally seem more than enough for 150KB. Could you check if your server is having some network congestion?

Otherwise, you can extend the webhook timeout to up to 5 minutes using our API Update Voice Agent - Retell AI . It’s longer than the exposed limit in our dashboard.

Thank You

4

Subject: Retell webhook abort / 30-second transfer cutoff

Hi Streebo team,

I saw your Retell Community thread about large webhook payloads aborting around the 30-second mark before the full payload reaches your production endpoint.

The timing looks worth isolating carefully because the abort aligns closely with the configured Retell webhook timeout, while your server logs also show only a fraction of the payload arriving before the connection closes.

A clean diagnostic would compare:

  • one failed large-payload request
  • one successful smaller request
  • transfer timing / bytes received
  • Retell timeout setting
  • any proxy/load-balancer/server timeout settings on the receiving path

That should help distinguish a sender-timeout issue from slow transfer or an intermediate infrastructure limit.

I do bounded async diagnostics for workflow/integration failures like this. No production access needed — redacted logs/config screenshots are enough.

Small diagnostic is $350. Same-day triage is $650.

If useful, send over a redacted failed + successful comparison and I’ll confirm whether it’s a fit before payment.

Best,
Eric