Camunda 7 History Cleanup Strategy – Keep Production Fast & Stable
Introduction In long-running production systems using Camunda 7 , one of the most common hidden performance killers is uncontrolled history data growth . Symptoms you may already have seen: Cockpit and Tasklist becoming very slow Database CPU usage increasing month by month Simple queries on ACT_HI_* tables taking seconds or minutes Production incidents after a few months of go-live 👉 The root cause is almost always the same: no proper history cleanup strategy . This blog explains: How Camunda 7 history works Why cleanup is mandatory in production Available cleanup strategies Step-by-step configuration Best practices from real projects How History Data Works in Camunda 7 Camunda 7 stores runtime and audit data in relational database tables . Main history tables ACT_HI_PROCINST – Process instances ACT_HI_ACTINST – Activity instances ACT_HI_TASKINST – User tasks ACT_HI_VARINST – Variables ACT_HI_DETAIL – Variable updates Every completed process instance adds rows to these ...