Overview

This marketplace component is now deprecated. Mendix provided a runtime setting to execute this cleanup since Mendix 9.9.0. See https://docs.mendix.com/refguide/scheduled-events-legacy/#cleanup

--------------

Executes a daily cleanup of scheduled event logs to prevent the database from filling up. Works as-is, no setup required. Every scheduled event in Mendix creates entries in the "ScheduledEventInfomation" entity in the database. Without cleanup, the logs will fill up the database over time. Configuration is not required. If you wish, you can set the number of days to retain logs, the batch size, the max number of batches and some more.

Documentation

Description
Every scheduled event in Mendix creates entries in the "ScheduledEventInfomation" entity in the database. The scheduled event cleanup module runs a daily scheduled event to clean up these entries.

Typical useage scenario
Use this in any app that runs scheduled events. This module will automatically prevent the database from filling up with scheduled event logs.

Features

• Scheduled event logs are cleaned daily at nighttime
• The deletes are done in batches to support large numbers of records
• The number of days to retain the records is configurable
• Sorting of records is optional

Limitations

None

Dependencies

• Community Commons

Configuration
Just make sure scheduled event "SE_ScheduledEventInformation_Cleanup" is enabled in your enviroment.

You can finetune behaviour via several constants, but under normal circumstances the default values will do fine.

• BatchSize; The number of scheduled event logs to remove in each batch. The default is 1000.
• MaxNumberOfBatchesPerDay; This setting prevents the cleanup from delaying other processes in case of very high numers of scheduled event log entries to clean. The default is 100 batches per day.
• RetainRecordsForXDays; Scheduled event information will be retained for this number of days. The default is 32 days.
• RemoveOldestFirst; If set to true, it will guarantee that the oldest records are deleted first. This requires sorting, which has some performance impact. The default value is true.