# Changes are not applied straight away **URL:** \ **Category:** Prismic Administrative Support\ **Created:** [February 10, 2025, 2:28pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391 "2025-02-10T14:28:00Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![celine.hervouet](https://avatars.discourse-cdn.com/v4/letter/c/6bbea6/32.png) [@celine.hervouet](https://community.prismic.io/u/celine.hervouet)\ **Post date:** [February 10, 2025, 2:28pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/1 "2025-02-10T14:28:00Z")
Hello Prismic ![Capture d’écran 2025-02-10 à 14.28.07](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/f/f2ced1d0dcea341dee7b9e188e3fda0ee46405f4.png) For some time now the data we are recovering has not been updating as quickly as before, we have deactivated the cache we have on our side and the problem persists, do you have any idea why we have this data lag? I updated the text of the cta of this banner "cta\_text" by adding the word "TEST" but the field is not updated in my response to the request on prismic... Please find attached the problem I am facing. Thank you in advance ---
**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\ **Post date:** [February 11, 2025, 2:27pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/2 "2025-02-11T14:27:56Z")
Hi Celine, This FAQ should help you debug the issue: > [@Changes in Prismic not appearing on your website](https://community.prismic.io/t/changes-in-prismic-not-appearing-on-your-website/5461): > > Have you published changes in Prismic that aren't appearing on your website? Or maybe it takes a certain amount of time before you see the changes? Here we discuss the most usual causes of something like this. How long does it take for changes in Prismic to appear in the API? The Prismic API will immediately refresh with new content as soon as you publish it. You can verify that the changes are coming through by viewing the document in your API explorer. The API explorer is a graphical user in… Confirm what steps you've tried here, then if that doesn't work we can dig more into you project deployment setup. Thanks. ---
**Author:** ![celine.hervouet](https://avatars.discourse-cdn.com/v4/letter/c/6bbea6/32.png) [@celine.hervouet](https://community.prismic.io/u/celine.hervouet)\ **Post date:** [February 20, 2025, 2:57pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/3 "2025-02-20T14:57:37Z")
It is not that we don't understand, we didn't change anything. on the implementation. Is it the new version slow down the update on prod ? ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [February 20, 2025, 3:34pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/5 "2025-02-20T15:34:15Z")
Hi @celine.hervouet, We're trying to investigate an issue where some users have noticed a very small delay between the masterRef in the webhook payload of their repository and the one on their repository API, which caused outdated content being in the site. This sounds like it could be a similar issue here - are you able to check or confirm whether this is what's happening to you as well? You're updating the content on your repository, and then it isn't appearing live on your website at the same speed as usual? Or is it that you _are_ querying the latest ref directly, but the content is not the most recent? Can you clarify your process for noticing the difference between your document and the API? I may have follow-up questions once this is cleared up! Thank you for your help 🙂 ---
**Author:** ![celine.hervouet](https://avatars.discourse-cdn.com/v4/letter/c/6bbea6/32.png) [@celine.hervouet](https://community.prismic.io/u/celine.hervouet)\ **Post date:** [February 25, 2025, 11:13am UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/6 "2025-02-25T11:13:38Z")
Hello, here to complete a bit. Yes we query the last reference and we can notice the difference between the data returned by the API and that recorded in the documents ![Capture d’écran 2025-02-25 à 12.07.14](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/1/1effabba8ab35ad257c6254f757fb83ba32c7bd8.png) Thank you in advance Regards Céline ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [February 25, 2025, 6:30pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/7 "2025-02-25T18:30:05Z")
Hello @celine.hervouet, Thank you for the details! Here's a few follow-up questions from our team to better understand the situation. Every little bit helps understand our investigation 🙂 - Are you using the Prismic client SDK? If not, how are you querying our API? - Do you ever get any error codes at any point related to an outdated ref or anything else, or have you just noticed content updates are slower than usual? - You mentioned this has been happening for a little while, could you let us know when it first started? Thank you again for your help! ---
**Author:** ![celine.hervouet](https://avatars.discourse-cdn.com/v4/letter/c/6bbea6/32.png) [@celine.hervouet](https://community.prismic.io/u/celine.hervouet)\ **Post date:** [February 27, 2025, 9:32am UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/8 "2025-02-27T09:32:14Z")
Hey, We are using like this: [A 6-Minute Introduction to API Testing with Postman](https://prismic.io/blog/api-testing-using-postman-for-beginners#prismics-endpoint) Our webhook from Prismic is triggered. After we send it to Prismic. But the change appears really late after those changes. Is it cache on Prismic side ? Regards Céline ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [February 28, 2025, 10:56am UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/9 "2025-02-28T10:56:07Z")
Hi Céline, If you query the latest master ref, the data should not be outdated. Similarly, if the ref is new and part of the URL, it makes the cache inactive since the ref was not requested before. Can we have a little bit more information on how you are querying your data? Are you using URL/.cdn/something else, when are you doing it, is it strictly with your webhook? Any detail you can give us helps. Thank you! ---
**Author:** ![celine.hervouet](https://avatars.discourse-cdn.com/v4/letter/c/6bbea6/32.png) [@celine.hervouet](https://community.prismic.io/u/celine.hervouet)\ **Post date:** [March 5, 2025, 11:59am UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/10 "2025-03-05T11:59:39Z")
Hey Ezekiel, Here under our answers > how you are querying your data? We query Prismic API endpoint: [https://darjeeling-production.cdn.prismic.io/api/v2](https://darjeeling-production.cdn.prismic.io/api/v2) (with our API token) 1. Query root enpoint to get master ref 2. Query `/documents/search` API with the master ref (all pages) to get "uid", "type" and "data" for each entry 3. Refresh our website data (CDN files) with the data from API > is it strictly with your webhook? These API calls are triggered by every webhook Thank you Céline ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [March 7, 2025, 2:56pm UTC](https://community.prismic.io/t/changes-are-not-applied-straight-away/18391/14 "2025-03-07T14:56:39Z")
Hi @celine.hervouet, In order to figure out where the issue may lie and which way to continue troubleshooting this, here's what we'd recommend: when you update your repository's content (publish a new document, modify an existing one, etc.), you can have a look at your repository's API browser to verify the latest content is available there. If it is up to date and the master ref in the API matches the master ref in the webhook, then the issue would be located in your project's code or in whichever deployment service you use (for example it could be a cache issue there, as you've mentioned). As a next step I'd recommend making some changes, checking your API browser and comparing the master refs with the webhook. This should clear up where the problem is coming from! Let me know what your findings are, and I'll be happy to help further if needed 🙂