-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
What/Where is the issue ?
Customer wants to know why when configuring Optimize history cleanup on a perProcessDefinition basis, cleanup fails if one of the process definitions does not yet have a process instance in Optimize. Seems like that should just be a warning or maybe just an INFO level message, it should not stop history cleanup from running at all.
Environment: C7/ C8SaaS/ C8SM
Optimize version : 3.10.3
Steps to reproduce:
Enable history cleanup
Configure it for perProcessDefinitionConfig
Configure two processes
only load instances for one of the processes
Wait for the cleanup to run
Observed behavior:
The cleanup fails with this error
01:00:00.140 [CleanupScheduler-1] ERROR o.c.o.s.cleanup.CleanupScheduler - Execution of cleanupService EngineDataProcessCleanupService failed
org.camunda.optimize.service.exceptions.OptimizeConfigurationException: History Cleanup Configuration contains definition keys for which there is no definition imported yet, aborting this cleanup run to avoid unintended data loss. The keys without a match in the database are: [Test2]
Expected behavior:
The cleanup should continue with no ERROR but maybe a warning would be better.