History Cleanup - There is not executed cleanup job in table ACT_HI_JOB_LOG

Camunda 7 Topics
1

I got no information that the cleanup job was being executed. I figured it out, as it removed all entries that have passed REMOVAL_TIME_ timestamp.

Camunda version: 7.20
Cleanup strategy: removalTimeBased

2

Hi @boromijovic
Welcome to the forum!
Could you please clarify the issue? I’m a bit confused because in the issue summary, you mention that ‘no job was executed,’ but later in the description, you say that ‘the cleanup job was being executed.’

Could you please elaborate on the problem?

Thanks,
Alex

1 Like
3

Hi @Alex_Voloshyn I was not clear enough :smiley:

The history cleanup job was executed, cleaning up all the history data as it should. The strategy I used is removalTimeBased with Camunda 7.20.
It’s all ok from that side.

I expect to have some information in the act-hi-job-log table about the executed cleanup job. That cleanup job at the end removed a lot of data from the database.

4

Hi @Alex_Voloshyn, I figured it out, cause I bumped into several other issues regarding history data and cleanup, like not persisting assignee_ for UserTasks in act_hi_actinst table, etc.

I’m using the custom history level, with full I do not have issues, so the ball is on my side of the court now :smiley:

Possibly there were some changes in Camunda 7.18 to 7.20 that affected my custom history level.

Best regards

5

Hi @boromijovic
Thanks a lot for sharing the update.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.