Steps to reproduce:
1. Create an event, publish it.
2. Remove the event snapshot(s) from the data base, keeping the ElasticSearch index as is. This might happen if ActiveMQ is not working while somebody depublishes (we have a production system with this inconsistent state).
3. Try to remove the event using the admin-ui.
The "depublish" dialog is shown. You can select publication channels and create the depublication task. Internally, nothing is created, and the event state stays the same. The event cannot be removed.
The event can be removed.
Workaround (if any):