Hey guys, does sanity have some kind of caching mechanism on request? im using the `@sanity/client` in a rn app; the issue is, when I edit a document in sanity and then attempt...

Hey guys, does sanity have some kind of caching mechanism on request?im using the

@sanity/client

in a rn app;the issue is, when I edit a document in sanity and then attempt to fetch that document again, I have to run the fetch exactly two times for it to update; any idea why it doesn't update the first time? (I tried waiting over 5 minutes and will not work on the first fetch)

If you use Nextjs getStaticProps with revalidate, the cache is in Nextjs. The first hit will always serve from cache and the next hit serves the updated response

as far as I understand nextjs is used on react web; I don't have a nextjs dependency in my project, neither does the sanity client; but I think you're definitely on the right track

Are you using the APICDN by any chance? Urls would be like projectid.apicdn.sanity.io/ ...

yes that was it, thank you

although I had this page opened https://www.sanity.io/docs/api-cdn I didn't see the configuration

usesCdn: true

it doesn't seem to be worth it though; will speak to my client and explain what's happening there

just out of curiosity, im assuming most of the users use the apicdn, the tradeoffs doesn't seem that big

It varies a lot actually. If you can live with slightly stale data we highly recommend it for robustness and latency. But it is a tradeoff against freshness.

Using the api will hit our document stores every time.

stale-while-revalidate

is set to 600 seconds, so that is how old content we serve while fetching fresh in the background. If it is older than 600s you will have to wait for fresh content.