Document_uid_conflict - Slug update not working even if slug is available - Cache issue?

Developing with Prismic
1

Hello,

I am getting an error when trying to updating my menu page:

Oops! We were unable to save your document.

We encountered an error while trying to save your document. Please contact our support team if this issue persists.

{"error":"document_uid_conflict","details":{"version_id":"aBVtXxEAACYAmsi5"}}

While I know for a fact that there is no page with the same slug anymore. Even in archive, I have changed there slug too.

Is there a caching issue happening here that is making Prismic not being aware of the fact that this particular slug is not available?

PS: I know we are not supposed to change the slug of a page.. We are not really changing it per se. We are just rotating different version of a menu page and publishing one at the time on /menu while having the other versions as /menu-winter /menu-autumn etc... And rotating the correct one back to /menu item when time is due as we lack budget to pay dev to do this.

Thanks for the help

2

Hi @claudia.r.murray,

Thank you for reaching out! UIDs are kept "attached" to a document even after it's been changed. This is to prevent broken links, so if you use uid1 on a document, then change that document's UID to uid2, you won't be able to re-use uid1 right away. You need to find the document that used to have the UID you're trying to re-use, duplicate it, and delete the original to free up the UID history. Does that make sense?

You can do that following the instructions on this page: Edit a Document's Unique Identifier - Documentation - Prismic.

Let me know if I can help further!