UND_ERR_HEADERS_TIMEOUT'

[saogalaxy]

Sampling texture SLat: 42%|████▏ | 5/12 [00:51<01:12, 10.34s/it]Error proxying status request to local API: TypeError: fetch failed
at async m (.next/server/chunks/[root-of-the-server]__9cd20083..js:1:1358)
at async d (.next/server/chunks/[root-of-the-server]__9cd20083..js:1:4774)
at async l (.next/server/chunks/[root-of-the-server]__9cd20083..js:1:5812)
at async P (.next/server/chunks/[root-of-the-server]__9cd20083..js:1:6890) {
[cause]: Error [HeadersTimeoutError]: Headers Timeout Error
at ignore-listed frames {
code: 'UND_ERR_HEADERS_TIMEOUT'

this needs to state that the job has failed or clear out the pending job if its not working. or restart the process .

[carlosgalveias]

I have the same issue , there is a timeout. If I increase the number of steps and takes more time it will give this error.

[stkevinwang-max]

This looks like a bug within Next.js. Anyone got a chance to investigate further into this?

[stkevinwang-max]

After days of reading online posts...... I have found a solution.

In Next.js, the built-in fetch uses undici under the hood, which defaults to a 5-minutes timeout. Since this is a hardcoded setting in the Node.js runtime, you can't override it via standard fetch options.

Solution: Use instrumentation.ts

1. Create instrumentation.ts in your /app folder:

import { Agent, setGlobalDispatcher } from 'undici';

export function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    setGlobalDispatcher(
      new Agent({
        headersTimeout: 30 * 60 * 1000, // 30 minutes
        bodyTimeout: 30 * 60 * 1000,    // 30 minutes
      })
    );
    console.log("✅ Undici global dispatcher configured: 30min timeouts active.");
  }
}

2. Run this command in your terminal under /app directory:
   pnpm add undici
pnpm build

3. Restart docker.

The default timeout is now set to 30 minutes.

nodejs/node#