Unexpected error returned. Server message: CONFLICT: {{slice}} already exists

Has anyone else ran into this error when trying to push an updated slice model to Prismic? I added a field and changed 2 labels, if that helps pinpoint whats going on.

A few hours later, I have a second slice which was a slice under active development also now in this state where I can't push it to Prismic.

Hi Karl,

Welcome to the Prismic community,

To investigate this, may I have the repository name (in a private message if necessary) to which you are trying to push your Slice?

And it would also be useful to have a code snippet of the custom type you are trying to push.

Looking forward to your reply,
Fares

Well one solution can be to change the local project you are working with, if that is not a solution then you can use the new custom types API to delete the Slice.

I'm still not sure what has provoked the issue, so I will try to gather some more information and get back to you?

The slier is being used for 100+ pages, so deleting it or changing the local project isn't really an option for us right now.

Please let me know if you need any more information from us and we'll get it to you.

Hey @kfite, can you give me your api endpoint, the id of the slice you're trying to update and copy paste its local model here ?

Hi @kfite,
Have you been able to resolve this issue? if not I would need to create an issue for this so that our devops team work on it.

An issue in our tracker has been created to better track this issue.

This thread is being monitored as an open ticket in the issue tracker. We will update this post as we get more information. If you have a similar use-case, you can ‘Flag’ this topic to reopen.

I have the same problem and I'm not able to fix it.

Hi @prismic20,

Thanks for letting us know, there is already an open issue related to this, and I have followed up with our dev team to see if there are any updates.

I will let you know in case of any updates,
Fares

@Fares is there any update on this issue? Or how can we avoid that?

Hi @aleksandar.basara1

Thanks for reaching out. It will really help if you can provide some extra information such as your repository name, the exact error you are getting, and the name of the slice that you are trying to push to try to reproduce the issue; that makes fixing the issue quicker.

1 Like

Hey @Fares I've sent you the details in a DM.

1 Like

I've received the info and forwarded the request to our Slice Machine team, and we will let you know in case of any updates.

Hi @aleksandar.basara1 @kfite @prismic20

Updating Slice machine dependency to the latest version (Now it is 0.4.2) should resolve the issue.