gatsbyjs/gatsby · error

111007

111007

Error message

Your WordPress server at ${bold(url)} appears to be overloaded.

${getLowerRequestConcurrencyOptionMessage()}

What it means

handleFetchErrors detected an ECONN-aborted/overload-style response from the WPGraphQL endpoint: the server at url is responding but appears overloaded. The message points at lowering request concurrency (via the documented option message) as the remedy before failing the build.

Solutions

  1. Lower options.schema.requestConcurrency in gatsby-config.js to reduce load on the WordPress server.
  2. Increase server resources or enable response caching for WPGraphQL.
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:358 when the library encounters an invalid state.

Common situations: Occurs when the WordPress server responds too slowly or with overload errors. Lower request concurrency in the plugin's schema options and/or increase server resources.


AI-assisted analysis of gatsbyjs/gatsby@8b06340921 (2026-08-13). Data as JSON: /api/errors/74a69ea2d31ad640. Report an issue: GitHub.

Appendix: source

Thrown at packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:358

        sourceMessage: formatLogMessage(
          `It took too long for ${url} to respond (longer than ${
            timeout / 1000
          } seconds).\n\nEither your URL is wrong, you need to increase server resources, or you need to decrease the amount of resources each request takes.\n\nYou can configure how much resources each request takes by lowering your \`options.schema.perPage\` value from the default of 100 nodes per request.\nAlternatively you can increase the request timeout by setting a value in milliseconds to \`options.schema.timeout\`, the current setting is ${timeout}.\n\n${genericError(
            { url }
          )}`,
          { useVerboseStyle: true }
        ),
      },
    })
    return
  }

  if (errorIs500ish(e) && !e.message.includes(`500`)) {
    if (`message` in e) {
      console.error(formatLogMessage(new Error(e.message).stack))
    }

    reporter.panic({
      id: CODES.WordPress500ishError,
      context: {
        sourceMessage: formatLogMessage(
          `Your WordPress server at ${bold(url)} appears to be overloaded.

${getLowerRequestConcurrencyOptionMessage()}`,
          { useVerboseStyle: true }
        ),
      },
    })

    return
  } else if (e.message.includes(`Request failed with status code 500`)) {
    reporter.panic({
      id: CODES.WordPress500ishError,
      context: {
        sourceMessage: formatLogMessage(
          `${e.message}

View on GitHub (pinned to 8b06340921)