@remotion/serverless: Retry on socket hang up and ECONNRESET errors

[JonnyBurger]

Summary

• Adds socket hang up and ECONNRESET to the list of retryable errors in streamRenderer's callFunctionStreaming catch handler
• Previously only Error: aborted and ETIMEDOUT were retried, causing transient connection failures to be treated as fatal

Closes #6127

Test plan

• Verify that a socket hang up error during streaming now triggers a retry instead of failing immediately

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Feb 17, 2026 11:59am
remotion	Error		Feb 17, 2026 11:59am

[Copilot]

Pull request overview

This PR adds retry logic for socket hang up and ECONNRESET network errors that can occur during Lambda function streaming invocations. Previously, only Error: aborted and ETIMEDOUT errors were retried in the transport layer, causing transient connection failures to be treated as fatal errors. The fix aligns the streaming error handling with the existing isFlakyError function that already considers these errors retryable in the browser/renderer execution context.

Changes:

• Extended the retry condition in streamRenderer's catch handler to include socket hang up and ECONNRESET errors