Bug: on-demand revalidation showing one step old stale data

[surjithctly]

I'm using the api/revalidate to update content. But each time it updates, it returns one step old data. Not fresh.

I'm tried using bothuseCdn: true & false, but same result. Here, the webhook fires immediately after publishing, but apicdn takes upto 60 sec to update the content. Thus Next.js getting old data each time.

See below video.

Video transcription:

Starts next production builds
change “first post” to “Our first post”
Simulate “webhook” requests
Data do not change

[next attempt]
change “Our first post” to “Next first post”
Data change to Stale “Our First post” this time
but new data is “Next First Post” (edited)

CleanShot.2022-12-12.at.20.07.48-converted.mp4

[surjithctly]

Are you able to reproduce this bug? @stipsan

[stipsan]

The revalidate function isn't designed to be used with useCdn. It should be false 🤔

[surjithctly]

Tried with both true & false. But same result.

[stipsan]

If you can share a link to the repo I could give it a look?

[surjithctly]

Sure. here it is: https://github.com/surjithctly/jamstack-starter

[stipsan]

Thnx, I'm on the go right now and couldn't see anything out of the ordinary when browsing your code saw. Back home I'll investigate on my laptop and see what's going on

[surjithctly]

Thank you, I even tried adding a delay of 5 seconds in revalidate.ts, but that also did not help.

[surjithctly]

Damn! just realized I still had useCdn true for frontend, false was only applied for revalidate. 🤦‍♂️

It does seems to work now. ✅

Thanks a lot for the help. You may close this issue.

[stipsan]

Great to hear you figured it out @surjithctly! 😌 There's some more information on how the revalidation works in this thread: #97 (comment)