Managing Report and Scheduler Retention in WebReports

Retention settings control how long WebReports keeps completed report output and scheduler execution history. These are separate records with different uses: output lets users reopen a result, while scheduler history helps administrators investigate executions.

Review retention when storage grows, users need more time to retrieve completed reports, or troubleshooting requires a longer scheduler history. Choose values that meet your organization’s requirements.

Open Settings

1. Sign in to WebReports with an administrator account.
2. Expand Configuration in the left navigation.
3. Select Settings.

Scroll to Reports options.

Screenshots use fictional demo data. Example settings are not recommended values or a statement of the defaults. Select an image to view its full size.

Reports options showing the demo Report Default Retention of 3 days and Remove Scheduler History Days of 60 days.

Choose the retention setting

Changing one setting does not change the type of data controlled by the other. These settings also differ from the Visualize cache lifetime, inactive in-memory report cleanup, statistics retention, and log cleanup.

Change and verify retention

1. Record the current values and review the required reporting and troubleshooting history.
2. Change Report Default Retention, Remove Scheduler History Days, or both.
3. Select Save. Changes apply immediately to the current instance and within approximately 60 seconds on other instances.
4. For a completed report, review its stored expiration on Reports > Completed. Do not assume that changing the default recalculates every existing report’s expiration.
5. Review scheduler history through Schedule and confirm that the retention window meets the investigation requirement.

Automatic cleanup removes eligible records. Preserve information you must keep before shortening retention; increasing retention does not recover data already removed.

For the full Settings reference, see Configuring Application Settings in WebReports.