Camunda internal usage of ACT_HI_JOB_LOG table

There’s a similar thread for ACT_HI_ACTINST but in my case I have an instance of Camunda database gone huge because of ACT_HI_JOB_LOG table.

Is it possible to simply truncate this table? Would this affect any current running instances / process history?
I’ve got these JOB_DEF_TYPE’s residing in the table:

  1. batch-monitor-job
  2. instance-deletion
  3. async-continuation
  4. history-cleanup
  5. timer-transition
  6. batch-seed-job
  7. historic-instance-deletion

Hi @vermauv,

These rows are append-only. The engine does not rely on their presence and it should cause no problems to truncate the table. That said, as with any direct database modification I recommend to make a backup before. Lastly, you may want to implement a custom history level that prevents these entries from being generated in the first place.


1 Like

Thanks @thorben :slight_smile: