History Cleaning for Multi Schema Multi Tenant setup

We are using flowable 6.5.0

We are trying to use Shared Engine/Multi Schema process engine configuration based on this link:
https://blog.flowable.org/2018/09/11/multitenancy-in-flowable/

We have have more than one tenant, how the history configuration will work?

We tried to do this:

MultiSchemaMultiTenantProcessEngineConfiguration config
= (MultiSchemaMultiTenantProcessEngineConfiguration)processEngine.getProcessEngineConfiguration();
config.setEnableHistoryCleaning(true);
config.setHistoryCleaningTimeCycleConfig(“0 30 * * * ?”);
config.setCleanInstancesEndedAfterNumberOfDays(Integer.valueOf(1));

But the ACT_RU_TIMER_JOB table is empty after starting the server.
Not sure where flowable stores the details about the history timer configuration?

Also, the above configuration will be applied for all the tenants?
Is it possible to have different history cleaning setting for different tables?

Any guidance will be greatly appreciated.

1 Like

We upgraded to Flowable version 6.7.2. The issue persists.
Still the table ACT_RU_TIMER_JOB is empty in all the tenants schemas.

Any help on this will be greatly appreciated.

Thanks