What can happens (sometimes)

• Create a content with name "article-a"
• Publish it
• Delete it (assume there is a problem on deletion from the "live" workspace for any reason)
• Create a new content with name "article-a", this content has a new id
• Publish it, it fails

I don't have the stack trace right now but I'm able to explain.

The SynchronizeComponent which is used to copy the content from "default" to "live" workspace (synchronzeContent method) first checks if the content with the same id exists in live.
If yes, it continues.
If not, it tries to create the content in the "live" workspace, but a content with the same path but another id already exists.

It should first suppress the node with the same path if there is one, then creates the content in "live" workspace".
But be careful, we should take in account repeater cases like in CMS-11635.