gatsbyjs/gatsby · error

112001

112001

Error message

${errorMap.to}

What it means

Fires in handleGraphQLErrors when a fetched GraphQL error's message exactly equals the user-configured errorMap.from string and panicOnError is set: the panic reports the friendly errorMap.to mapping instead of the raw upstream error. It is a message-matching guard on the plugin options, not a new failure.

Source

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

    json.data &&
    pluginOptions.debug.graphql.onlyReportCriticalErrors &&
    // only return if we're not force disabling this.
    // this is used when we make GraphQL requests intentionally rather than programmatically
    // for ex during the Preview process
    !forceReportCriticalErrors
  ) {
    return
  }

  for (const error of errors) {
    const errorWasMapped =
      errorMap &&
      errorMap.from &&
      errorMap.to &&
      error.message === errorMap.from

    if (errorWasMapped && panicOnError) {
      reporter.panic({
        id: CODES.RemoteGraphQLError,
        context: {
          sourceMessage: formatLogMessage(errorMap.to),
        },
      })
    } else if (errorWasMapped) {
      reporter.error({
        id: CODES.RemoteGraphQLError,
        context: {
          sourceMessage: formatLogMessage(errorMap.to),
        },
      })
    }

    // convert the error path array into a string like "mediaItems.nodes[55].mediaDetails.meta.focalLength"
    let errorPath = error?.path
      ?.map((field, index) => {
        // if this is a number it's the index of a node

View on GitHub (pinned to e85d62f177)

Solutions

1. Fix the underlying remote WPGraphQL error described by errorMap.to
2. Update or correct the errorMap.from/errorMap.to entry in plugin options if the mapping is wrong
3. Set panicOnError to false (or rely on debug.graphql.onlyReportCriticalErrors) so the error is logged instead of halting the build

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/utils/fetch-graphql.ts:182 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/1ff38da34da1d27e. Report an issue: GitHub.