Currently there is no cleanup of data accumulated in the camundabpmn database. Over time the growing data set will have an impact on the database performance, specifically the ACT_GE_BYTEARRAY table which holds values for all process variables. We have observed intermittent lock timeouts (attached logs) when camunda tries to commit larger transactions.

Camunda does have a mechanism for database cleanup. A history time-to-live can be configured for each process, which will allow a cleanup job to remove expired data.

reference: https://docs.camunda.org/manual/7.10/user-guide/process-engine/history/#history-cleanup