by route you actually mean a route or a page?

actually I think it's just that 43 600 is not a valid number, try 43600 instead

also,

The values of the config options currently need be statically analyzable. For example revalidate = 600 is valid, but revalidate = 60 * 10 is not.

Iam sure that iam using 43600

and what do you mean by "it doesn't work", given that 43600 is a pretty strange number to choose?

Btw I didn’t know this, good to know thanks 🙂

43200* actually, 12 hours

I spent one hole day and the data hasn’t been revalidated

did you try starting with something more approachable, like 10 minutes? it's hard to reason about what is happening without seeing the contex o the route you're talking about - is it a static route that you want to revalidate?

The thing is that im using an api that revalidate his data every 12 hours, and I am showing a time stamp with the last update

https://github.com/cmollinea/calcuplator/blob/main/src/app/page.tsx

This is the page.

Shorty for my code, iam learning by myself web development 😅

line 25, you're not awaiting that

oh you're passing a promise, never mind

but why? why not await that and pass just the data?

ok I think the issue might be that you're revalidating the page, but the service getRates that's fetching the data will have its own cache on the fetch itself

you probably want to revalidate the fetch, rather than the page, so use this in the getRates
fetch('https://...', { next: { revalidate: 43200 } })

but that strategy is flawed, you would have to time your fetch with the 12h update cycle of the API, so setting your fetch revalidate to 12h makes no sense IMO

if you revalidate a second before the API updates, you'll be waiting another 12h

Yes revaluation is not working in Next14 also

I also open an issue on it

That’s fine I pass the promise to the component and wait for it there

Mmm I think you got a good point here, maybe 6h will be fine, but it seems to be an issue, so I think I will just fetch in demand for now

I awaiting for the important ones, and then pass the less important, it make sense to me...

Ohhh thanks!!!

Thanks for your time time btw 😀

oh nice, old features are broken, new features aren't working too, good release 😅

I think this is broken since previous releases, I have one project that isn’t revalidating either in next 13.4

Same here