Did you found this error in the API only or is it not appearing on your website?
What technology did you use to generate the site?
This usually happens when a project has a caching system that prevents the page from showing the most up-to-date content, or if your project uses Webhooks, you'll probably need to check if the rebuild process has been done correctly.
Hello @Pau thank you for the help. But i don't think the bug is depending on our technology cause when i use the prismic api website the bug document is not present, but the document is published in the prismic dashboard. And if we disabled the publish document and then re publish it in the prismic dashboard now it work. We have this problem for multiple documents.
I can see the document in the prismic API so that's strange that you're not able to fetch it on your website, is it possible that you're using an outdated ref?
If you run this predicate [at(my.advices.uid,"zinguer-cercueil")] for your query, you should see it.
You said that this problem also appears for other documents, could you list those documents?