Skip to content
← Back to activity

Solution skill

pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection

Version 2Sign in to save

Complete solution

Serverless: pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection. The verified fix is Fix: [jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with `pipelineConnect`, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung. Use this when you hit the symptoms above in serverless; not for unrelated serverless errors or general setup questions.

TL;DR

Fix: [jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with pipelineConnect, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung. Fixed server-side on production; no package update needed.

The error

Issue neondatabase/serverless#209 (closed, 5 comments): ## Bug: `pipelineConnect` silently hangs for payloads in ~32KB - 42KB range on pool reconnection

Fix

  1. [jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with pipelineConnect, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung.
  2. Fixed server-side on production; no package update needed.

Success check: the symptom above is gone and the original operation completes.

When to use

  • You hit this exact symptom in serverless.
  • You want the verified fix without digging through the thread.

When not to use

  • A different error in serverless, even a similar-looking one.
  • General serverless setup or credential questions.

Compatibility

  • Serverless (neondatabase/serverless)

Variant phrasings

  • How to fix "pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection" in serverless
  • serverless: pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection

Source

  • https://github.com/neondatabase/serverless/issues/209

Evidence

Asked in gh:neondatabase/serverless#209 (https://github.com/neondatabase/serverless/issues/209): pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection. The issue report: Issue neondatabase/serverless#209 (closed, 5 comments): ## Bug: pipelineConnect silently hangs for payloads in ~32KB - 42KB range on pool reconnection

Description

When pipelineConnect is set to "password" (the default for Neon hosts), queries that are the first on a newly created connection (after pool idle reaping) silently hang - the Promise never resolves and no error is thrown - if the total wire message falls within a specific size range (~32KB - 42KB of JSON parameter data).

Payloads below and above this range work correctly on reconnection. The issue only manifests when all three conditions are true simultaneously:

  1. **Connect The verified answer: [jawj (maintainer)]: Bug is in Neon's proxy code, not the npm package: with pipelineConnect, a first query of roughly 65-84KB wire size (Prisma sends UPSERT data twice - once for INSERT, once for UPDATE branch) silently hung. Fixed server-side on production; no package update needed. Reporter confirmed the hang no longer occurs.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_48h_sz9IlIKHNbeeTDym2w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">pipelineConnect silently hangs for payloads in ~32KB-42KB range on pool reconnection <span>— Vectle</span></a>