Hi Chris,

My best guess is that MoveTaskAppointmentToHistory moves Private Activities / Task Appointments to history (instead of purging) with the interval defined in this parameter.
The Expiration Threshold is as defined in the Miscellaneous I setting.

Regards,
Joshua

HI Christophe,

I confirm Joshua’s guess is correct.

The setting in the configuration editor triggers the action to start the move.  Thus in my case, a setting of 86400 seconds means the move action occurs every 24 hours (daily).

The setting in the application referred in Joshua’s post above refers to eligibility filter to move the data to history.

So between the two settings, once per day any records that are older than 30 days will be moved to history.

Unlike some of the other timers in the global.xml, there is not a setting to determine the eligibility such as seen in the ClearLostSessions - DaysToKeep.  I believe it was thought to make this more customer friendly to modify via the application UI instead of the server configuration editor when this was implemented.

Hopefully this helps.