Marc Littlemore

Hey @kamalbennani. Yes - that's something we're going to look at shortly and it's on our radar. We've found some breaking issues with the changes in the latest Next version...

Hey @bentrynning. We really appreciate everyone's frustrations with this not working and we always appreciate community PRs if you've got fixes. We've had a lot of bugs to fix and...

This will be fixed in our next release, @elsonwx. 👍🏻

Hey @Polonco! We haven’t heard back for a while so we’re going to close this for now. If you’re still running into the issue, or have more details to share,...

@dtsoden - Thanks for spotting this issue. The example we have in the API docs is wrong and creates an incorrect workflow. I'll update the example so that it works...

@dtsoden - Sorry this took so long but it's fixed with #19170. Should be in the next release.

Hey @bradlc - I think this is the same issue as this: https://github.com/netlify/next-runtime/issues/2089 We're looking at various fixes at the moment that should encompass this too. See: https://github.com/netlify/next-runtime/issues/2089#issuecomment-1689892702

Hey @RohitRajendran. The team at Netlify have now released the new `v5` Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache...

Hi @dwillitzer We haven’t heard back for a while so we’re going to close this for now. If you’re still running into the issue, or have more details to share,...

Hi @jfelipesjc, I've just tried this on our internal instance (1.70.0) and it seems to work OK for me. Have you tried accessing it from the command line (or via...