gatsbyjs/gatsby · error

The remote schema has changed, updating local schema.

Error message

The remote schema has changed, updating local schema.

What it means

Emitted (only when pluginOptions.verbose) in checkIfSchemaHasChanged when the remote WPGraphQL schema MD5 differs from the cached one and an incremental source has run before. It marks that the plugin will refresh its cached remote schema so new/changed fields become available; no action is required — it's an informational trace of why a full re-ingestion is happening.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:135

  if (shouldClearHardCache && foundUsableHardCachedData) {
    await clearHardCache()

    foundUsableHardCachedData = false
  }

  await setPersistentCache({
    key: pluginOptionsMD5Key,
    value: pluginOptionsMD5,
  })

  if (
    lastCompletedSourceTime &&
    schemaWasChanged &&
    pluginOptions &&
    pluginOptions.verbose
  ) {
    helpers.reporter.log(``)
    helpers.reporter.warn(
      formatLogMessage(`The remote schema has changed, updating local schema.`)
    )
    if (process.env.NODE_ENV === `development`) {
      helpers.reporter.warn(
        formatLogMessage(
          `If the schema change includes a data change\nyou'll need to run \`gatsby clean && gatsby develop\` to see the data update.`
        )
      )
    }
    helpers.reporter.info(
      formatLogMessage(`Cached schema md5: ${cachedSchemaMd5}`)
    )
    helpers.reporter.info(formatLogMessage(`Remote schema md5: ${schemaMd5}`))
    helpers.reporter.log(``)
  } else if (!lastCompletedSourceTime && pluginOptions.verbose) {
    helpers.reporter.log(``)
    helpers.reporter.info(
      formatLogMessage(

View on GitHub (pinned to e85d62f177)

Solutions

1. No action needed; the plugin refreshes the local schema automatically.
2. If unexpected, check which WordPress plugins changed the WPGraphQL schema between builds.
3. Set verbose: false in plugin options to silence this informational warning.

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/ingest-remote-schema/diff-schemas.js:135 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/492330d0f740f4ce. Report an issue: GitHub.