Retention
Monitoring → Retention gathers in one place everything the server keeps and lets grow, with what is kept, where that is set, how much it takes, and a way to clean up now. Only superusers see it.
At a glance
The stores
| Store | What goes | Set in |
|---|---|---|
| Job runs | Finished runs with their steps and logs, beyond the days kept or the cap per job. | Nomaflow — Run history retention. |
| Job files | Uploaded files, rejects reports, reports, exports, watched-folder archives. | Nomaflow — Files kept (days) in the same panel. |
| Notifications | Read notifications older than the days set. | Settings → App → Notifications — Keep read notifications. |
| Config versions | The configuration snapshots beyond the number kept per file, or too old; the newest of each file always stays. | The config-versions-purge job, else 20 per file and 90 days. |
| Change packages | Exported or promoted packages and import logs older than the days set. Drafts are never touched. | Kept by default. |
| Saved views | The users' own views and analyses. | Never purged — shown for their size. |
| Server log | Rotated by size: 10 MB per file, five older files. | — |
Job runs and job files show when Nomaflow runs on the server.
Preview and Run now
| Button | Effect |
|---|---|
| Preview | A dry run: Would delete N item(s), with the size. Nothing is deleted. |
| Run now | After a confirmation, applies the policy at once: Deleted N item(s). |
The buttons show only where there is something to purge: not for saved views and the server log, nor for notifications and change packages while they are kept without limit. The automatic clean-ups keep running on their own schedule.
Related
- Server log — search what the server wrote.
- Nomaflow administration — the jobs' retention policy.