Process and publish a video.
Use publish workflow.
The already published video will not be retracted and one ends up with two different versions in the mediapackage.
For more details, watch: https://youtu.be/SOQW5Wxpexk
Lars, our site, locally, added retract operations before all of the publish operations in our workflows, to protect against publishing over an existing publish. Is that enough to solve this problem?
[CORRECTION] FYI - our site had to stop automatically using the retract operation before the publish operation because it choked the admin with the huge number of retract & republish jobs. For example, when we just need to update the xacml file on a publication, just that file is retracted and republished to the engage server to the existing publication channel.
My guess: It would suffice.
This was one out of a series of different bugs I found today. I just wanted to make sure to not forget them. So I filed this ticket. I did not investigate it any further. Though a first glance at the publish workflow told me that it really needs some more changes. But that is another problem
At the technical meeting, Lukas has commented that this might be already implemented:
PublishWorkflowOperationHandler has an option: Republish only if it can be merged with or replace existing published data