Gatsby couldn't find a page for this node

[cruzlutor]

Since this morning we are getting this error after running gatsby project for development

warn Plugin gatsby-source-sanity called unstable_createNodeManifest() for node id "-aa5c661d-8306-5176-a37d-aa253333da33" with a manifest id of
"dc11f5c4-7e63-4f77-8883-a0d95862b54a-2020-06-16T17:53:29.000Z" but Gatsby couldn't find a page for this node.
If you want a manifest to be created for this node (for previews or other purposes), ensure that a page was created (and that a ownerNodeId is added to createPage() if you're
 not using the Filesystem Route API).

Yesterday everything was working well but suddenly this error started appearing today in the terminal, and the error appears multiple times with a different node id

Does anyone know why is this happening?

node version: 14.17.0
gatsby version: 3.13.0
gatsby-source-sanity version 7.3.2

UPDATED: we realized that this is happening after deleting the .cache folder and running the build command again

[djavco]

I am getting this warning too @cruzlutor Did you find a solution?

warn Plugin gatsby-source-sanity called unstable_createNodeManifest() for node id "-46d3b2ff-1af6-5a5b-abbe-b85559c47de4" with a manifest id of
"18656c02-55a9-47a8-95cc-7062e555d60c-2021-06-02T16:12:33.000Z" but Gatsby couldn't find a page for this node.
      If you want a manifest to be created for this node (for previews or other purposes), ensure that a page was created (and that a ownerNodeId is
added to createPage() if you're not using the Filesystem Route API).

[chandlervdw]

Same here

[dev-searchengineunity]

We are getting the same issues. The manifest id all points to document nodes that don't form a page (like an instance of a testimonial under our document type 'testimonials'). The fact that Gatsby cannot find a page is expected for these nodes... not sure what to do to resolve this for us.

[taitsengstock]

Did anyone manage to find the cause of this?