Apollo Server v4 resolver continues after client disconnect

Apollo Server v4 does not automatically reject or cancel in-flight resolver promises when a client aborts an HTTP request. The GraphQL execution engine continues to process the resolver until the returned Promise resolves or rejects, regardless of the connection state.

Propagation of Abort Signals

To stop downstream work upon a client disconnect, resolvers must manually forward the req.signal (provided via the request object in the context) to the data source. If the signal is not passed to the underlying database client or API call, the server will continue to consume resources until the operation completes naturally.

Implementation Steps

• Pass the signal: Pass context.req.signal directly to libraries that support AbortSignal (such as fetch, pg, or mongodb).
• Manual checks: For long-running synchronous loops or logic not supported by a signal-aware library, periodically check req.signal.aborted and throw an error to exit the resolver early.

Combining Request Cancellation with Deadlines

To implement an operation-level deadline that triggers regardless of whether the client is still connected, use AbortSignal.any(). This creates a composite signal that aborts if either the client disconnects or the timeout expires.

const timeoutSignal = AbortSignal.timeout(5000); // 5 second deadline
const combinedSignal = AbortSignal.any([context.req.signal, timeoutSignal]);

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

Technical Assumptions and Constraints

Feature	Requirement	Behavior
AbortSignal.any()	Node.js v20.0.0+	Triggers on the first signal to abort.
AbortSignal.timeout()	Node.js v17.3.0+	Triggers after the specified milliseconds.
Downstream Cancellation	Library Support	Only works if the driver/client explicitly implements AbortSignal.

Verification Method

To verify this behavior in your environment:

1. Create a resolver with a 10-second setTimeout wrapped in a Promise that logs "Completed" upon resolution.
2. Trigger the request and manually abort the connection (e.g., stop the browser tab or kill the curl process).
3. Observe that "Completed" still prints to the server console.
4. Replace the timeout with a fetch call passing req.signal and verify that the promise rejects with an AbortError immediately upon disconnect.

Diagnostic Detail: Are you using a custom integration package (e.g., @apollo/server with a specific Express/Fastify wrapper) or a managed hosting environment? Some proxy layers may handle timeouts differently before the signal reaches Node.js.