Managing System Housekeeping
About System Housekeeping
The volume of stored historical and operational data generated by Max applications can grow rapidly over time. This not only consumes storage unnecessarily, but also causes increased query latency and degrades overall system performance. Much of this data, such as logs, notifications, or session traces, is useful only for short-term auditing, debugging, or analysis. To clear data storage space, you can configure and use the Housekeeping system job.
The Housekeeping job is designed to:
• Reduce storage bloat by removing stale or unused records.
• Improve system responsiveness by ensuring tables are compact, so that queries run efficiently.
• Maintain data hygiene to avoid the need to manually purge old entries.
• Ensure predictable resource utilization by preventing uncontrolled log and history growth.
• Support operation compliance by retaining only the necessary amounts of historical activity.
Housekeeping System Job Capabilities
The Housekeeping system job keeps the system healthy by cleansing up configurable and system-mandated objects.
The following configurable default objects are eligible for cleanup:
• Application Log
• Blocked IP
• Blocked User
• Data Scan History
• Deferred Operation Result
• Email Notification
• HTTP Notification
• Login Log
• Navigation History
• Phone Notification
• Push Notification
• User Authentication Request
• User Push Notification
• User Session
You can adjust this list based on your data-retention needs. Cleanup for these objects is time-based, and relies on a specified cutoff time. For example, you can configure cleanup to delete records that were created before a certain date, and also choose whether to evaluate record age by creation time or update time, which is the default. Optionally, you can define filtering criteria to determine which records are to be deleted.
 |
Records of configurable objects are permanently deleted by using SQL, and no change logs are generated.
|
The following system-mandated objects are always cleaned and cannot be modified or filtered:
• Package Import
• Package Export
• Data Import
• Documents and Versions related to these objects.
Cleanup for these objects is based on a retention-count model. You can specify how many of the most recent records you want to retain based on their creation time. All older records are deleted. This prevents operational log volume and disk usage from increasing indefinitely and ensures that the most relevant recent entries are retained.