## 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

```text
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