Skip to content
AnglinAI Docs

ERR_URL_TIMEOUT — URL Timeout

HTTP Status: 408 Retryable: Yes Automatic retry: None. The fetch is attempted once with an AbortController timeout.

What the User Sees

The remote server took too long to respond. (ERR_URL_TIMEOUT)

What Causes This Error

The remote file server did not respond within the URL_FETCH_TIMEOUT_MS limit (defined in packages/shared/src/constants.ts). The fetch uses an AbortController that aborts the request after this timeout period.

Common causes include: the remote server is slow or under heavy load, the file is very large and the remote server has limited bandwidth, the remote server requires authentication and is waiting for credentials (appearing as a hang), DNS resolution for the remote hostname is slow, or a network intermediary (proxy, CDN) is introducing latency.

This is different from ERR_NETWORK_TIMEOUT (which is about the client’s connection to our API). This error specifically relates to the server-side fetch of a remote URL that the user provided.

Resolution Steps

For Users

  1. Try again — the remote server may have been temporarily slow.
  2. Download the file manually to your computer and upload it directly instead of using the URL fetch feature.
  3. If the file is hosted on a slow server, manual download and direct upload is the most reliable approach.
  4. Verify the URL is correct and the file is still available by opening it in a browser.

For Administrators

  1. The timeout is configured as URL_FETCH_TIMEOUT_MS in packages/shared/src/constants.ts.
  2. If users frequently hit this timeout, consider increasing the value. The default is generous for most use cases.
  3. Monitor which remote domains trigger timeouts most frequently. If a specific domain is consistently slow, consider adding guidance to users about downloading from that source manually.
  4. Check if the Worker’s outbound fetch is being throttled or limited by Cloudflare. Workers have a generous fetch timeout but it is not unlimited.