When a persistent, typed actor fails during recovery (for example because a breaking change in the serialization format), it throws a JournalFailureException.
I’m watching this actor from another one and get the Terminated signal but its failure is set to None so there is no way to determine if the actor stopped because of the journal failure or in a normal way.
The exception is thrown here:
which is then captured by a supervisor behavior here:
which logs the exception and stops the actor.
Is this behavior intentional? I could not find a way to customize the behavior so it propagates the failure to the watchers.