/
Notification Cleanup Scheduled Task

Notification Cleanup Scheduled Task

To prevent unlimited growth of notifications stored in FIXICC H2 databases (HSQL, PostgreSQL), which degrades performance over time, a Scheduled Task deletes notifications older than seven days and is enabled by default.

Scope and prerequisites

  • Applies to FIXICC H2 installations using HSQL or PostgreSQL.

  • You need permissions to view and edit Scheduled Tasks in the Administration section.

  • For concepts and field descriptions used below, see Administration section — Creating a scheduled task: Administration section | Creating a scheduled task

Default configuration (as shipped)

The automatic cleanup is provided as a Scheduled Task with the following defaults:

Field

Value (default)

Field

Value (default)

Defined by

Bean

Bean Name

fixicch2TasksService

Method Name

clearNotificationsOlderThan(String days)

Method Parameters

  • String days: 7

Scheduling Type

Cron

Cron Expression

0 0 0 * * * — runs daily at 00:00 server time

User Name

admin

Log start / Log finish

  • Log start: enabled

  • Log finish: enabled

Other fields

  • Singleton, Permitted Servers, Timeout, Time Frame, Start Delay, Description: not set by default

Reference UI: See the attached screenshot for the default Scheduled Task configuration screen.

screenshot-1.png

What the task does

  • On each run, the task removes notifications with a creation timestamp older than the configured number of days (7 by default).

  • Deleting old notifications helps keep the database compact and improves application responsiveness.

How to view the task

  1. Go to Administration → Scheduled Task.

  2. Locate the task with:

  3. Bean Name: fixicch2TasksService

  4. Method Name: clearNotificationsOlderThan(String days)

How to change retention or schedule

Change retention period

  1. Open the task, set Method Parameters → String days to the desired number (for example, 14 to keep two weeks).

  2. Save.

Change run time/frequency

  1. Update Cron Expression (for example, 0 0 3 * * * to run daily at 03:00).

  2. Save.

For Cron syntax and field meanings, see: Administration section | Creating a scheduled task

How to verify execution

  • Open the Executions tab for the task to see the history of runs.

  • With Log start and Log finish enabled, you will see entries for each run.

  • In the Notifications screen, filter by date to confirm that notifications older than the retention threshold are no longer present.

Operational notes

Deletion is irreversible. If you require longer history for audit/reporting, increase the String days parameter before the next run.

Troubleshooting

Task does not run

  • Confirm the Cron Expression is valid and the server time/time zone is correct.

  • Verify the task is saved and visible in Administration → Scheduled Task.

  • Check the Executions tab and server logs for errors.

No records are deleted

  • Ensure String days is set to the intended value.

  • Verify that notifications older than the specified threshold actually exist.