According to docs https://docs.camunda.org/manual/7.13/user-guide/process-engine/history/#provide-a-custom-history-backend when implementing a custom HistoryEventHandler, the default DbHistoryEventHandler gets disabled.

In version 7.10, this was the behaviour. Only our own custom HistoryEventHandler was active.

Since upgrading to 7.13, our own handler automatically gets wrapped inside a CompositeDbHistoryEventHandler, causing the DbHistoryEventHandler to still be active.

This is unwanted behaviour, and in contradiction to the docs.

Observation:

Run processEngineConfiguration.getHistoryEventHandler()

7.10 result:

<our own historyEventHandler class>

7.13 result: 

org.camunda.bpm.engine.impl.history.handler.CompositeDbHistoryEventHandler