We recently implemented a custom history level in our Camunda 7 application, which makes sure that only specific items of interest to us are getting stored in history. After this change was deployed, Camunda Cockpit started failing to start with the following exception:
Is there an easy way to make the Cockpit start again, without adding our custom history class to the Cockpit binary and registering it in the configuration, as should be done for “regular” Camunda instances? Is there any place where something like this is documented?
Hi @Plukh
Can you share the value of historyLevel field in ACT_GE_PROPERTY table?
As I remember the value of the history level should be similar to the database record.
The value is 12 (as it is in our custom history level). I understand why the Cockpit wants to know the history level/implementation (as Cockpit actions also get logged in history, from what I know), but I’d like to find a way to continue using the Cockpit without modifying the app binary (by adding our custom history level implementation and wiring it in the engine config).
