-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clear cache required for resolveReferences to work after adding new object and document type #152
Comments
I believe we are also experiencing this issue which is requiring us to run a |
I've been looking into this exact issue too and have found the following within the When there is no cache, ALL documents and objects are downloaded into cache with their IDs. Once a cache has been generated, the second time around a separate procedure is run where documents are "touched" using Therefore the start up procedure and run from cache procedures are caching two different datasets, with the latter deleting much more from cache than it should, causing the references to break. |
Thanks for highlighting! |
Could this issue be the root of https://www.reddit.com/r/gatsbyjs/comments/uw8jq7/cache_issue_in_netlify/ as well? |
Thank you! We're looking into it. |
newPage
)newObject.newPageReferences
)oldPage.portableTextContent
)_rawPortableTextContent(resolveReferences: { maxDepth: 10 })
(in a page or via graphiql)Actual result:
newPageReferences
) returnsnull
resolveReferences
starts working again, andnewPageReferences
will contain the properties of the linked page.Expected result:
resolveReferences
should result in the page properties being returned without a manualgatsby clean
.gatsby@^4.4.0 (4.4.0)
gatsby-source-sanity@^7.3.2 (7.3.2)
The text was updated successfully, but these errors were encountered: