A statuschangeevent might be incorrectly published when restoring a suspended workflow instance from db

[fjtirado]

If the latest known stated before the JVM crasch was suspend, when that instance is restored in a restart, a phantopm status change event (from pending to suspend) will be thrown when restoring the suspend status
Formally speaking, the status has not changed, so this should be avoided.