What/Where is the issue ?
If a per-process definition key doesn't exist in the history cleanup configuration, the whole history cleanup will fail with a configuration exception. This means that correctly configured process definitions will also not be cleared up, resulting in data remaining that should not.
Environment: C7/ C8SaaS/ C8SM
Optimize version : All
ES version : All
OS + Browser version : All
Steps to reproduce:
- Preconditions:
- Steps:
- Add a per-process history cleanup config to Optimize for a definition key that does not exist in the engine
- Observe the logs
Observed behavior:
The logs contain an exception and the whole history cleanup has not been applied
Expected behavior:
The logs contain a warn message, but the rest of the cleanup is applied correctly