gatsbyjs/gatsby · error

If the schema change includes a data change you'll need to r

Error message

If the schema change includes a data change
you'll need to run `gatsby clean && gatsby develop` to see the data update.

What it means

A follow-up warning in checkIfSchemaHasChanged, shown in development when verbose is on and the remote schema changed. It explains a caching nuance: schema changes that also carry data changes can leave stale cached node data behind, so a clean cache is required to observe the update. Purely informational.

Source

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

  }

  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(
        `\n\n\tThis is either your first build or the cache was cleared.\n\tPlease wait while your WordPress data is synced to your Gatsby cache.\n\n\tMaybe now's a good time to get up and stretch? :D\n`
      )
    )
  }

View on GitHub (pinned to e85d62f177)

Solutions

1. Run gatsby clean followed by gatsby develop to discard the hard cache and see updated data.
2. Or delete .cache/wordpress-{...} hard cache files manually.
3. If only the schema (not data) changed, no action is needed.

When it happens

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