Support for on-Demand Revalidation

[kamerat]

I'm having issues using the on-demand revalidation when hosted on netlify.
When I test it locally by doing next build and next start it works. However, when I test it on a build-deploy or live, it does not seem to update the page.

I have validated that the API endpoint in netlify gets run, has the correct data and unstable_revalidate did not break. (in ___netlify-handler function log)

Does on-demand revalidation not work on netlify yet, or am I missing some config?

EDIT:

Also discussed in #1228

^{Originally posted by iankduffy February 18, 2022}
Hello, NextJS 12.1 has added On-demand Incremental Static Regeneration currently in Beta / Unstable, just wondering if in the future if we are looking to add this to netlify plugin?

[ascorbic]

Hi @kamerat
Currently on-demand revalidation is not supported. It is on our roadmap, but we cannot share a date for support yet.

[EddyVinck]

@ascorbic is unstable_revalidate unsupported still? I just tried it and it seems to not work, at least.

[yescine]

@ascorbic Still to this date with nextjs@12.2.3 res.revalidate(), it doesn' t update the page although the revalidate api endpoint handle the request.

[ascorbic]

@yescine @EddyVinck in progress!

[iurage]

Hi, any updates on progress for this?

[orinokai]

@iurage we are keen to support this as soon as possible and are working toward it as per our roadmap

[ChazUK]

Would be good to hear an update on this. It's been a much talked about feature in my team and we're really looking forward to selling this performance benefit to our clients!

[pm0u]

Really would like to see this for feature parity with other hosting providers. Any updates on timeline? This is bordering on dealbreaker for us as we have a massive blog that we can't realistically rebuild every time someone finds a typo.

[ascorbic]

I'm afraid I can't be any more specific than "this is being worked on". We're waiting on some new platform features that we need for this to work, but I think you'll be pleased with the results.

[elleryfamilia]

"this is being worked on"... i mean, seems like a trivial task given that you already support {revalidate: 60}. If you're concerned about resource use, then just paywall it. It wouldn't be so bad if we also didn't have to wait 60 seconds for revalidation... maybe bring that down to 10 seconds?

[ascorbic]

i mean, seems like a trivial task given that you already support

You know that they there say are the two hard problems in computer science?

[theooog]

@ascorbic Any updates?

[nickytonline]

It's actively been looked at at the moment, but I can't provide a timeline yet @theooog.

[BilegtGG]

?