basicly fetch also has a cache by default (in future versions it will be not default), so also add [export const fetchCache = "default-no-store"](https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config#fetchcache) or change the fetch cache options in the actual fetch req function

So by adding export const fetchCache = "default-no-store" the revalidate will actually revalidate the data after 30 seconds?

yeah it should, as the page level cache should exist and fetch should also stop caching

looks like it's not revalidating actually, data stays the same even after some minutes. does revalidation affects data that is passed as prop to a client component?

ok maybe fetch with revalidate: 0 is better?

but revalidate is kinda sus, it still shows stale data (just refreshes it in background for next visit to be accurate)

the cause here is that OP is fetching from a local route handler which is static by default, so although the fetch is made every x seconds, they all return the same build-time value. @OP: [Don't do that](https://nextjs-faq.com/fetch-api-in-rsc)

yeah mb i didnt see the localfetch part

okay got it, thanks a lot.
i updated the fetch with an async function that queries the db (if it's the correct way).
all of this was on the server side, which approach should I use to get updated data on the client?
should i query the local api because i'm inside a client component or just import the same function that queries the db?

i'm asking this because in the client component I'm trying to periodically update the data displayed, the update occurs once every 60 seconds inside a setTimeout that queries the local api to then update the data with react's setState.
This looks like it's working but it creates a ton of promises on the client, i can see that every 60 seconds it doesn't send just 3 requests, it sends like 10~20 of them

just make sure to put that in a useEffect

Got it, thanks a lot 👍