gatsbyjs/gatsby · error

${error}

Error message

${error}

What it means

After a media-item fetch promise was re-queued five times without succeeding, pushPromiseOntoRetryQueue gives up and panics with the accumulated error. The log suggests lowering GATSBY_CONCURRENT_DOWNLOAD; the root error is the embedded fetch failure for that media item.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js:104

        previouslyRetriedPromises[retryKey] = timesRetried + 1

        pushPromiseOntoRetryQueue({
          node,
          helpers,
          createContentDigest,
          actions,
          queue,
          retryKey,
          retryPromise,
        })
      } else {
        helpers.reporter.info(
          `\n\nalready re-queued ${retryKey} 5 times :( sorry.\nTry lowering process.env.GATSBY_CONCURRENT_DOWNLOAD.\nIt's currently set to ${process.env.GATSBY_CONCURRENT_DOWNLOAD}\n\n`
        )
        // we already tried this earlier in the queue
        // no choice but to give up :(
        helpers.reporter.panic(error)
      }
    }
  })
}

export const addImageCDNFieldsToNode = (node, pluginOptions) => {
  if (!node?.__typename?.includes(`MediaItem`)) {
    return node
  }

  const placeholderUrl = getPlaceholderUrlFromMediaItemNode(node, pluginOptions)

  const url = node.sourceUrl || node.mediaItemUrl

  const filename =
    node?.mediaDetails?.file?.split(`/`)?.pop() ||
    path.basename(urlUtil.parse(url).pathname)

View on GitHub (pinned to e85d62f177)

Solutions

1. Lower GATSBY_CONCURRENT_DOWNLOAD (e.g. 20) to reduce server pressure
2. Fix the underlying fetch error for the listed media item
3. Increase server capacity/timeouts if the WP host is rate limiting

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/fetch-nodes/fetch-referenced-media-items.js:104 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of gatsbyjs/gatsby@e85d62f177 (2026-08-26). Data as JSON: /api/errors/8c364057dc50fcc2. Report an issue: GitHub.