Route Occasionally Returns 200 Status with Empty Payload, Requires Multiple Refreshes

[Ebentim]

Description
I'm experiencing inconsistent behavior with a Next.js route where:

• The initial request often returns a 200 status code with an empty response payload
• After multiple refreshes (usually 5 or more attempts), the route eventually returns the expected payload
• There are no error messages or warnings in the console

Expected Behavior
The route should consistently return the expected payload with a 200 status code on the first request.

Reproduction Steps

1. Navigate to [route path]
2. Observe response (often empty)
3. Refresh page 5 or more times
4. Observe successful response

Environment

• Next.js version: 15
• Node.js version: 22
• Operating System: Windows 11
• Browser: Chrome, Edge
• Deployment: Vercel, local development,