Disable History Clean Up

Hello everyone,

I am currently working with Camunda 7, and we are facing an issue: we are unable to delete historical records. I have read that the Time to Live (TTL) can be configured from the diagram and set to null, but we want to be cautious. Even if a TTL value is set, we want to ensure that the information is not deleted from our historical tables.

To achieve this, I understand that I need to adjust the yml file to disable periodic cleanup. I believe I have configured it correctly, but I would like to confirm if the clean-up settings are correct. Could someone review it and give me their opinion?

camunda.bpm:
  webapp:
    csrf:
      enable-same-site-cookie: true
      same-site-cookie-option: STRICT
    header-security:
      hsts-disabled: false

  authorization.enabled: true

  generic-properties.properties:
    deserialization-type-validation-enabled: true
    deserialization-allowed-packages:
    deserialization-allowed-classes:
    enable-password-policy: true
    historyCleanupEnabled: false

  run:
    auth.enabled: false
    example:
      enabled: true
    webapps:
      enabled: true
server:
  ssl:
    # key-store: classpath: /*Your_Certificate*/
    # key-store-password: /*Your_Certificate_Password*/
    # key-store-type: pkcs12
  # port: /*Your_Port*/

  servlet.session.cookie:
    secure: true
    http-only: true

logging:
   level.root: INFO
   file.name: logs/camunda-bpm-run.log

# datasource configuration is required
# spring.datasource:
#   url: jdbc:sqlserver://proxy-host:1433;databaseName=/*Your_Database*/
#   driver-class-name: com.microsoft.sqlserver.jdbc.SQLServerDriver
#   username: /*Your_Username*/
#   password: /*Your_Password*/

spring.web.resources:
  static-locations: NULL

# camunda.bpm.run.process-engine-plugins:
#   - plugin-class: org.camunda.bpm.example.parselistener.InformAssigneeParseListenerPlugin

Thanks in advance!

Hi @nicolasgg

By default , history cleanup is not performed automatically (as no batch cleanup window is configured)

For automated history cleanup on a regular basis, a batch window must be configured.