gatsbyjs/gatsby · error

${id} ${singleName} was updated, but no data was returned fo

Error message

${id} ${singleName} was updated, but no data was returned for this node.

What it means

Update-path warning in the preview/update flow: a single-node update (WPGatsby action) was received for the given id, but the GraphQL response contained no data for that singleName (data or the field was null/empty). The node therefore cannot be updated; the plugin logs this and continues with other updates.

Source

Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:83

      ? {
          WPGatsbyPreview: token,
          WPGatsbyPreviewUser: userDatabaseId,
        }
      : {}

  const { data } = await fetchGraphql({
    headers,
    query,
    variables: {
      id,
    },
    errorContext: `Error occurred while updating a single "${singleName}" node.`,
  })

  let remoteNode = data[singleName] || data[camelCase(singleName)]

  if (!data || !remoteNode) {
    reporter.warn(
      formatLogMessage(
        `${id} ${singleName} was updated, but no data was returned for this node.`
      )
    )

    reporter.info({
      singleName,
      id,
      actionType,
      cachedNodeIds,
      token,
      isPreview,
      userDatabaseId,
    })

    return { node: null }
  }

View on GitHub (pinned to e85d62f177)

Solutions

1. Check whether the content was deleted, unpublished or made private in WordPress right before the update webhook fired
2. Verify WPGraphQL returns the node for that id with the credentials configured in gatsby-source-wordpress
3. Test the single-item GraphQL query used by the plugin directly against your WPGraphQL endpoint
4. If it recurs, debounce/dedupe webhooks so delete and update events don't race

When it happens

Trigger: Thrown at packages/gatsby-source-wordpress/src/steps/source-nodes/update-nodes/wp-actions/update.js:83 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/4429ba4c3699a37c. Report an issue: GitHub.