# Issue with revalidating the content in live site URL?

**URL:** <https://forum.builder.io/t/issue-with-revalidating-the-content-in-live-site-url/6318>\
**Category:** Technical Questions\
**Created:** [September 4, 2024, 3:54pm UTC](https://forum.builder.io/t/issue-with-revalidating-the-content-in-live-site-url/6318 "2024-09-04T15:54:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehan](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@Mehan](https://forum.builder.io/u/Mehan)\
**Post date:** [September 4, 2024, 3:54pm UTC](https://forum.builder.io/t/issue-with-revalidating-the-content-in-live-site-url/6318/1 "2024-09-04T15:54:54Z")

</div>

Hello, i have a question.

We have application with **builder io** and **next.js** and in our pages with have set the revalidate to 10 second so every time a page gets published a change is reflected with a little delay.

But in our live page (on production) it breaks sometimes and refuses to revalidate the pages, however time we refresh, empty cache and refresh… even after minutes or even hours.

So we assume it is from the fact that the revalidate is set to **10 seconds** and we make too many requests for invalidating the cache and that may be the cause of the issue not reflecting the changes.

**Mind you, cachebust is set to true as well in the request to get the page content.**

So, is there a recommended amount to set the revalidate to ?  
And what may be the cause of the content not reflecting sometimes, if not the low revalidate time.

---

<div class="post-metadata">

**Author:** ![manish-sharma](https://avatars.discourse-cdn.com/v4/letter/m/8797f3/32.png) [@manish-sharma](https://forum.builder.io/u/manish-sharma)\
**Post date:** [September 5, 2024, 10:27am UTC](https://forum.builder.io/t/issue-with-revalidating-the-content-in-live-site-url/6318/2 "2024-09-05T10:27:52Z")

</div>

Hey @Mehan,

It looks like our content API is returning updated data. However, the revalidation is connected to Next.js. So, I need you to check the Next.js cache and the deployment server’s caching mechanism to gather more details about the issue.

If those checks don’t help, kindly share the live page URL where we can test the issue to provide further assistance.

> **[Content API - Builder.io](https://www.builder.io/c/docs/content-api#code-cachebust-code)**
>
> Learn how to use Builder's Content API to make requests to retrieve data about any of your models. Write queries with dot notation and MongoDB style operators.

> **[Building Your Application: Caching | Next.js](https://nextjs.org/docs/app/building-your-application/caching)**
>
> An overview of caching mechanisms in Next.js.

> **[next.config.js Options: headers | Next.js](https://nextjs.org/docs/pages/api-reference/next-config-js/headers#cache-control)**
>
> Add custom HTTP headers to your Next.js app.

Thanks,