[Retrospective] Gatsby project build failures caused by missing records in GraphQL responses

What to do

• Check whether your product depends on DatoCMS. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2025-08-05 12:28 UTC and 2025-08-05 12:28 UTC may need a replay.

• Subscribe to DatoCMS's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=datocms works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from DatoCMS 1

1. resolvedAug 5, 2025, 12:28 PM UTC

   Resolved — On August 4th, 2025, starting from 14:00 UTC, some customers reported issues building their Gatsby projects that use our gatsby-source-datocms plugin due to records being missing from their GraphQL responses, despite being present in the CMS admin area. The issue was related to a recent change in our code that caused pagination issues with the records fetched by our gatsby-source-datocms plugin. This prevented some records from being visible in the Gatsby GraphQL responses. A rollback of that change was deployed on August 5th at 7:15 UTC. A regression test has been added to ensure that this particular issue with pagination won't happen again.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.