Respect timeout passed to fetch

What version of Bun is running?

1.2.0+b0c5a7655

What platform is your computer?

Darwin 24.2.0 arm64 arm

What steps can reproduce the bug?

From #5930 (and #6217) it seems Bun hardcodes a fetch timeout to 5 minutes (which seems like a sensible default).

When I pass a longer timeout to fetch, e.g.:

fetch(url, {
      signal: AbortSignal.timeout(1000 * 60 * 60), // 1 hour
})

after 5 minutes bun throws

FetchError: The request failed and the interceptors did not return an alternative response
      at new FetchError (...)

AbortError: The operation timed out
 code: "ABORT_ERR"

and doesn't respect the longer timeout.

What is the expected behavior?

If a signal is given which is longer than the default, it should be respected

What do you see instead?

No response

Additional information

No response

Related to #13126 and #13302 which are closed but from my tests are still broken.

Your specific is longer though, but just out of curiosity does it let you set lower then 5mins?

This is happening because the timeout option in fetch doesn't know anything about AbortSignal.timeout

We can fix it. It won't be 100% robust.

with 1.2.4 AbortSignal.timeout only works with 6 milliseconds settings, higher than that it floats

// signal: AbortSignal.timeout(6)
The operation timed out.
[6.76ms] fetch

// signal: AbortSignal.timeout(7)
The operation timed out.
[130.29s] fetch

This is happening because the timeout option in fetch doesn't know anything about AbortSignal.timeout

We can fix it. It won't be 100% robust.

I tested the timeout option in Bun by setting it to false. It is working.

However, the documentation and typescript also has nothing to say about the timeout option being there.

@ts-ignore

Here is the current fix.

fetch(url, {
      signal: AbortSignal.timeout(1000 * 60 * 60), // 1 hour
      // @ts-ignore
      timeout: false
})

Do note that typescript will scream at you since typescript doesn't know that the fetch have a parameter of timeout. You can suppress it using @ts-ignore or something similar.

Hope it can be fixed soon

I am waiting for this to be fixed since #13302
But apparently that issue was closed for an unknown reason.

I tried again but still seems not to work. My approach:

console.log('oke');

// DOES NOT WORK
await fetch('https://devplesk.mintyserver.nl/a/a/a/a/a', {
    signal: AbortSignal.timeout(1000), 
    timeout: false
})

// WORKS without `timeout` prop
// await fetch('https://tools.arthurvanl.nl/api/v1/delay/time?duration=6000', {
//     signal: AbortSignal.timeout(1000), 
//     // timeout: false
// })
console.log('oke')

Bun should just disable the timeout by default. It causes more problems than benefits

@AkritW

This took a very long time to track down due to missing stack traces or any info other than a TimeoutError. Thank you @AkritW for posting your solution 🙏

fetch: a numeric timeout must not be preempted by the default socket-…

h2: treat a disarmed idle timeout as unbounded in the session aggrega…

e2e: bound per-attempt fetch timeout in spawn waitForReady

fetch: let an explicit `timeout` extend the socket idle deadline (#33647

fetch: add connectTimeout, socketTimeout, and a whole-request timeout

feat(cli): bridge OpenCode native compaction via internal REST API (#…

Session 29 (2nd continuation): DeepSolve resilience + real Bun-fetch-…

snap: switch runtime from Bun-compiled binary to bundled Node.js

docs: update AGENTS.md and README for the Node.js runtime

coding: disable the Bun runtime's 5-minute fetch timeout under the tr…

provider: timeout SSE reader reads to survive broken streams

feat(cli): bridge OpenCode native compaction via internal REST API (t…

Navigation Menu

Repository navigation

Respect timeout passed to fetch #16682

What version of Bun is running?

What platform is your computer?

What steps can reproduce the bug?

What is the expected behavior?

What do you see instead?

Additional information

8 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Respect timeout passed to fetch #16682

Description

What version of Bun is running?

What platform is your computer?

What steps can reproduce the bug?

What is the expected behavior?

What do you see instead?

Additional information

Activity

RiskyMH commented on Jan 24, 2025

Jarred-Sumner commented on Jan 24, 2025

themockingjet commented on Mar 5, 2025

AkritW commented on Apr 12, 2025

AkritW commented on Apr 20, 2025

orange-GuandeLi commented on Aug 4, 2025

arthurvanl commented on Aug 20, 2025

remorses commented on Oct 1, 2025

damassi commented on Oct 30, 2025

8 remaining items

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions