gatsbyjs/gatsby · error

BadResponse

BadResponse

Error message

Encountered errors. See above for details.

What it means

Error "Encountered errors. See above for details." thrown in gatsbyjs/gatsby.

Source

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

  errorContext,
}: IHandleErrors): Promise<void> => {
  await handleErrorOptions({
    variables,
    query,
    pluginOptions,
    reporter,
  })

  if (!responseJSON) {
    return
  }

  if (
    !responseJSON.data ||
    panicOnError ||
    pluginOptions.debug.graphql.panicOnError
  ) {
    reporter.panic({
      id: CODES.BadResponse,
      context: {
        sourceMessage: formatLogMessage(
          errorContext || `Encountered errors. See above for details.`
        ),
      },
    })
  }
}

interface IHandleGraphQLErrorsInput {
  query: string
  variables: IJSON
  response: AxiosResponse
  errorMap: IErrorMap
  panicOnError: boolean
  reporter: GatsbyReporter
  errorContext: string

View on GitHub (pinned to 8b06340921)

Solutions

1. Read the errors logged above this message; they contain the actual failure details.
2. Fix each reported error (usually a WordPress connectivity or plugin option problem) and rebuild.

When it happens

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

Common situations: Occurs at the end of a step when earlier errors were already reported. Review the errors logged above this message and fix the first root cause.

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