Production problems with dataset not updating correctly in Sanity API

15 replies
Last updated: Dec 12, 2022
This is a bit of a shot in the dark, we have some production problems we can't get to the bottom with.

We have a dataset with ~7000 documents, and some of the documents stops working when we add certain data to them.

The problem looks like this:
1. We have a working document
2. Add some data
3. Publish, all looks good in Sanity studio
4. Fetch the document from the API, the changes you made do not appear in the API. The _updateAt date do not change.
5. You can publish how many changes you want and they look like they succeed in the Studio, you get revision history and everything in the Studio. But fetching it from the API returns the version from before the "problematic data" was added.
6. Remove the problematic data, now you get the latest version from the API and everything is fine.

However, the "problematic data" seems to be random.

When we have this unwanted behavior, we discovered that different endpoints gives different data.

Works, we get latest version:

Broken, we get old version until we remove the "problematic data":
https://&lt;project-id&gt;.<*[_id|*[_id> == "&lt;doc-id&gt;"]

(Tested different api versions and it's the same thing)

Anyone experience similar issues that can give some hints?
Nov 22, 2022, 2:42 PM
Could you share some actual query urls with us?
Nov 22, 2022, 5:40 PM
Hi, here is one example:*[_id%20==%20%22891b828d-fc8c-44a7-bf35-7fbd64d66a3b%22]
The first one gets the latest version:
The second one gets an old version:
Nov 23, 2022, 6:11 AM
Here is one more example:*[_id%20==%20%22e830fa8f-aa23-422f-b668-ee203b8159f0%22]
Response from first endpoint:
Response from second endpoint:

Although it's the same document we fetch from the same dataset.

sanity dataset export ...
also returns the correct data, it seems to be just the api that we use to query data that returns old data.
Nov 24, 2022, 8:47 AM
do these things also behave the same in vision (the query playground in the studio)?
Nov 24, 2022, 6:06 PM
Yes, that broken url:
Is copied from vision
Nov 25, 2022, 6:40 AM
We made an export yesterday and restored it to a new dataset, and the new dataset works as expected. But we would like to know what caused it because the export and import is not a sustainable solution since it removes the revision history, and takes time.
The dataset I linked to with this unwanted behavior still exists for debug purposes.
Nov 25, 2022, 8:16 AM
Did you save the other dataset?
Nov 28, 2022, 7:32 PM
Did you find anything we did wrong with that dataset?

The new dataset that we imported to still works I think, at least no more cases of this behavior has been reported yet.
Dec 5, 2022, 7:36 AM
user K
sorry for the late reply, we have been super busy with the v3 release and are getting back on track now. I do not have news for you yet, but I am still on it!
Dec 9, 2022, 2:58 PM
Hi Felix - we're checking in with our backend team as it seems like something odd might be going on here indeed. Thank you for providing the details to help us progress this internally. We'll get back to you here on Monday if not earlier.
Dec 9, 2022, 3:23 PM
Great, thank you!
Dec 12, 2022, 6:21 AM
Good morning
user K
- we've implemented a potential fix for this in the backend. May we ask you to check if you are getting more consistent results between the two different endpoints now?
Dec 12, 2022, 8:34 AM
Yes now it seems to be working! I also see new validation errors as well, which I assumes points out the cause of the issue, which is great!
Thank you much!
Dec 12, 2022, 9:10 AM
That's great, thanks for confirming!
Dec 12, 2022, 10:18 AM

Sanity– build remarkable experiences at scale

The Sanity Composable Content Cloud is the headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?