I am using camunda 7.13 community edition and would like to clear out any history older than 30 days. I have configured historyTimeToLive property as follows:
When I deploy a new process the process definitions all have a 30 day TTL set:
but the decision definition’s TTL are all still null
After 30 days there are still history traces from variables created during the decision definitions. I had a look and cannot see any other specific property to set the default TTL specifically for decision definitions.
Thanks I have noticed this but what I would like to do is apply a default TTL for them system wide without manually configuring it for each decision table similar to how the historyTimeToLive property does it for the process definitions.
if I am not mistaken, the historyTimeToLive handles this for process/decision/case definitions that do not define a TTL themselves. This is also documented in the History Cleanup Configuration.
Please note that this will not be applied to already deployed decision definitions.
There is a REST API endpoint that allows to change the TTL for deployed decision definitions:
Thanks for the reply. What I am noticing is even if I deploy a new decision table without a TTL it has no effect, almost as if the logic does not apply to decision tables. If I upload a process definition without a TTL it does however get set. Could this possibly be a bug? I am deploying my decision tables and process definitions within the same .war file but the decision tables TTL doesn’t get set at all, only the process definitions TTL get set.
I am not aware of an issue with the TTL in decision tables like this.
Could you upload a simple example that reliably reproduces this (either a ZIP, WAR, or a link to a project that is hosted somewhere publicly accessible)?
Download camunda 7.13.0 from camunda’s website: https://downloads.camunda.cloud/release/camunda-bpm/tomcat/7.13/camunda-bpm-tomcat-7.13.0.zip
Replace the server/apache-tomcat-9.0.33/conf/bpm-platform.xml with the one in the zip file below.
Either build the maven project using mvn clean install from the root of the extracted zip file contents to create a new .war deployment or use the existing pre-built test-1.0.0.war from the target folder from the zip.
Copy the test-1.0.0.war file to the webapps directory of camunda: /server/apache-tomcat-9.0.33/webapps
Start camunda, I normally use ./catalina.sh run command from tomcat’s server/apache-tomcat-9.0.33/bin directoryso I can monitor the logs for a successful deployment.
The deployment contains 1 process definition and 1 decision definition (test_process.bpmn and test_decision.dmn) stored under the resources directory.
Login to camunda’s cockpit using the default demo:demo credentials and navigate to the process definition:
I did a very quick test (using Camunda Run with a configured historyTimeToLive and a simple BPMN and DMN definition) to see if it is a general issue.
I can confirm that this is not picked up by the decision definition. I would classify this as a bug.
If you don’t mind, you can file a bug report at our Issue Tracker. You could reuse the description of the scenario you have here and maybe also hint at my minimal setup. Please also share a link to the forum topic, this will help in making progress faster.
Thanks again for identifying this issue and moving it forward, this will help to improve the product a lot!
