When you have an Outscaling scenario/configuration of two (or more) cms instances and you use the Data Management action within the cms manager to purge one or more items, this change isn't synchronized to cms instance(s) which are listed as subscriber of the local cms instance.

Add the eventclass and -subtype ContentChange.PurgeItems to the EventClasses registry parameter of Outscaling's EventSubscriber on the local cms instance and on each cms instance which is listed as subscriber of the local cms instance.

More about Outscaling's EventSubscriber and which events are available and should be registered (especially when dealing with two or more cms instances) can be found on the support5 site: Outscaling Event Subscriber.

Note: The publication instance, which is configured separately as an Outscaling server instance, can be compared with an Smartsite 5 Outscaling server instance with a shared database and a shared filesystem. So, only events which have to do with state management are applicable for any publication instance. However, because an Smartsite 5 Outscaling server instance with a shared database and filesystem isn't quite the same as an publication instance, the list of applicable events is a bit shorter. It includes ContentChange.Activation and ContentTypes. Furthermore, within iXperion the Security and DataEditor events are used for state management as well.