Builder.io example "next-js-on-demand-isr" not working (probably due to caching)
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 1.2k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 17
Description
Hi Builder Team 👋
**Describe the bug**
I used and set up the **[next-js-on-demand-isr](https://github.com/BuilderIO/builder/tree/main/examples/next-js-on-demand-isr)** example from your repository. For this, I followed exactly all the steps listed in the README.
Unfortunately, I am currently running into a problem. The problem is that "on-Demand ISR" is not working properly in production. The revalidate endpoint in Next.js must be called several times before the changes are visible.
I have a feeling this is due to caching within Builder.io's API.
**To Reproduce**
Follow the steps in the README from the example **[next-js-on-demand-isr](https://github.com/BuilderIO/builder/tree/main/examples/next-js-on-demand-isr)**.
**Expected behavior**
When the webhook calls the revalidation endpoint, the new content should be visible on the production environment.
**Video**
I uploaded a screen recording with the issue.
[buillder-nextjs-on-demand-ISR.webm](https://user-images.githubusercontent.com/17295145/199985188-43a36505-b0fc-4046-9fc3-a23dbe945e8a.webm)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.