Retry transient TLS network failures

[cursor]

Changes

• Add transient network error detection for Node/undici TLS disconnects such as Client network socket disconnected before secure TLS connection was established.
• Reuse the shared retry wrapper for webhook dispatch fetches so transient socket resets get retried there too.
• Add focused unit coverage for retrying status-less TLS/network failures while leaving unrelated errors non-retryable.

Testing Criteria

• yarn test src/app/api/core/utils/withRetry.test.ts --runInBand passed.
• yarn lint:check passed with existing React hook/compiler warnings only.
• yarn tsc was attempted; it still fails before these changes on existing missing SVG module declarations from src/icons/index.ts.

Notes

• Linear/Sentry MCP access was unavailable (Linear returned 401 and Sentry requires auth), so the investigation used the trigger metadata, repository Sentry config (project: 'tasks'), and code paths for outbound network calls.

Impact & Surface Area of Change

• Affects shared Copilot API retry behavior for HTTP retries plus transient network failures with known retryable network codes (ECONNRESET, ETIMEDOUT, EAI_AGAIN) and the exact TLS disconnect message.
• Webhook dispatch keeps its existing swallow/log behavior after retries are exhausted; successful transient retry prevents one-off TLS resets from surfacing as failures.

  

[linear-code]

OUT-3956

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jul 2, 2026 4:20pm