User guide
Quick Start Guide
Dashboard
Overviews
Case detail (Caseoverview)
Case - event
Tasks
Case notes
Documents
User settings
Favorites
Table component
FAQ
News/Announcements in Team assistant
Mobile app settings
Administrator Guide
Platform guide
Administration
Crons
Authentication and Synchronization
Mobile App Setup for Your Environment
Scheme
Dynamic tables
Archiving
Scripts
Service console
Scheduled Tasks
HR Agenda
Sequences
CSP Headers
Logs
Access Token Settings & Session Expiration
Template
Roles
Planning
Users
Organizational structure
Events
Translations
NFC Integration
AXIOS API
Calculations & Functions
Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Product
Technical Changelog
Business Changelog
Version Upgrade Guide
Upgrading to 5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Highlighting variables in Read-only status (>v5.7.58)
Using validation functions
Upgrading to 5.3
Dynamic conditions migration
PDF printing adjustment
Editing Task Description vs Task Instructions
Transpiling forEach to a for loop
Rendering HTML on Caseoverview
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Technical details
News / Important information
Getting Started
- All Categories /
- Administrator Guide
- Platform guide
- Administration
- Crons /
- CleanupCron
CleanupCron
The CleanupCron deletes old data from the database and cleans up the application's temporary files. It iterates over a list of tables defined in its parameters and, for each table, deletes records older than a configured number of days.
Overview
Property | Value |
Purpose | Deletes old data from the database and cleans up the application's temporary files |
Default schedule |
|
Timeout | 60 minutes |
The schedule can be changed in the cron administration.
What the cron deletes
The cron iterates over the list of tables defined in its parameters. For each table it deletes records older than keepDays days, up to a maximum of limit records per run.
Table | Default | Default | Note |
| 730 | 1,000 | Performance logs |
| 730 | 1,000 | Event parameters |
| 730 | 1,000 | Cron run history (only records in |
| 730 | 1,000 | DMS file access logs |
| 730 | 1,000 | E-mail queue (only e-mails in state |
| 180 | 5,000 | AI tool call records |
| 180 | 5,000 | LLM run records |
| 180 | 5,000 | AI user action requests |
| 360 | 5,000 | AI conversation memory |
| 360 | 5,000 | AI conversation messages |
| 360 | 1,000 | AI agentic workflows |
| 360 | 1,000 | AI conversations |
In addition to the database tables, the cron also clears and recreates the application's temporary folders (tmp subdirectories). This behavior is controlled by the cleanupTmp parameter.
Parameter configuration
The cron parameters are provided as a JSON object. Example of the default configuration:
{
"tables": [
{ "name": "PERFORMANCE_LOGS", "keepDays": 730, "limit": 1000 },
{ "name": "MAIL_QUEUE", "keepDays": 730, "limit": 1000, "processStatuses": ["D"] },
{ "name": "AI_LLM_RUN", "keepDays": 180, "limit": 5000 }
],
"cleanupTmp": true
}Table parameters
Parameter | Required | Description |
| Yes | Table name (see the list above) |
| Yes | Records older than this number of days will be deleted |
| Yes | Maximum number of rows deleted per run |
| No | Record status filter (for |
The cleanupTmp parameter
Value | Behavior |
| The application's temporary folders are cleared and recreated |
| The temporary folders are skipped |
Editing the configuration in administration
- Go to Administration → Crons.
- Find the cron
Cleanup old data from Database and from other parts of app. - Edit the JSON in the Parameters field as needed (change
keepDays,limit, or remove/add tables from the list). - Save and optionally run it manually.
Updated
by Frantisek Brych