How to propagate AbortController signals through Next.js API routes to prevent orphaned database operations on client disconnect

Direct answer

Manually create an AbortController inside the route handler, bind its signal to the incoming request’s close lifecycle, and pass that signal to every cancellable database query or external HTTP call. Next.js does not automatically propagate request abort signals to database drivers or upstream fetch clients.

Confirmed behavior

• Pages API routes and Node.js runtime Route Handlers expose a Node.js req object; client disconnect usually emits close on req.socket.
• fetch(url, { signal }) and axios honor AbortSignal and reject when the controller is aborted.
• Database driver support varies: some accept a signal directly, others require polling signal.aborted or driver-native cancellation before commit.
• Vercel (10s hobby / 60s pro) and AWS Lambda (15m maximum) can terminate the function before cleanup finishes, so abort handlers must return quickly.

Likely explanation

Next.js API routes are thin wrappers around Node.js HTTP or Web Request APIs. The framework does not inject an abort signal into Prisma, pg, mysql2, or upstream fetch calls by default. When a client disconnects, the socket closes, but in-flight database transactions keep running unless your code explicitly rolls them back or releases the connection.

Steps for this case

1. Create the controller at the top of the handler:

const controller = new AbortController();
const { signal } = controller;

2. Wire the socket close event (Pages API or Node.js runtime Route Handlers):

req.socket?.on('close', () => controller.abort());

3. Pass the signal to external calls:

fetch('https://api.example.com/data', { signal });

4. Guard database work. Check signal.aborted before starting a transaction and after awaiting each query. If aborted, roll back, release the client, and throw:

if (signal.aborted) {
  await client.query('ROLLBACK');
  client.release();
  throw new DOMException('Aborted', 'AbortError');
}

5. Wrap the handler so the function exits promptly after abort:

try {
  await doWork({ signal });
} catch (err) {
  if (err.name === 'AbortError') {
    await cleanupDatabase();
    return new Response(null, { status: 499 });
  }
  throw err;
}

Platform differences

Platform	Timeout	Behavior on disconnect
Vercel Hobby	10s	Function may be killed before abort cleanup completes.
Vercel Pro	60s	More time for rollback, but still bounded.
AWS Lambda	15m maximum	Abort signal fires, but forced termination can leave orphaned work.
Custom Node.js	Server-configured	Depends on keep-alive and server timeout settings.

Verification

1. Start a long-running route that inserts a row and sleeps.
2. Cancel the client request mid-flight, for example curl --max-time 2 http://localhost:3000/api/route, then close the tab.
3. Check server logs for an abort entry and confirm the database has no partial row or open transaction.
4. Repeat on each target platform because timeout behavior differs.

Missing diagnostic detail: Are you using Pages API routes or App Router Route Handlers, and which runtime? The signal source changes between req.socket and Web Request properties, and Edge runtime limits socket access.