---
title: "Clean up the ECM+ change log history"
slug: "clean-up-the-ecm-change-log-history"
description: "Clean up ECM+ change log history by scope, retention period, or date range, then schedule recurring batch jobs to automate deletion."
tags: ["ECM plus"]
status: "new"
updated: 2026-10-21T07:58:24Z
published: 2026-10-21T07:58:24Z
canonical: "docs.staedean.com/clean-up-the-ecm-change-log-history"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clean up the ECM+ change log history

Change log records add up over time. Use **Clean up ECM+ change log history** to delete the records you no longer need. You can run the cleanup once, or schedule it as a recurring batch job.

## Steps

1. Open the Impact workspace for the ECO, and then select **Change log**.

For more information, see [Track actions in the change log](/manufacturing/docs/track-actions-in-the-change-log-impact-workspace).
2. On the Action Pane, select **Clean up ECM+ change log history**.

The **Clean up ECM+ change log history** dialog opens.
3. In the **Parameters** section, in the **Scope** field, select which records to delete.

Options:

> [!NOTE]
> Note
> 
> Only the fields for the selected scope are available. The other fields are disabled.
  - **Retention period**: Deletes records older than the period in the **Retention period days** field.
  - **Custom days**: Deletes records older than the number of days in the **Custom days** field.
  - **Date range**: Deletes records created between the **From date** and the **To date**.
  - **Current ECO only**: Deletes all change log records for the current ECO.
4. Complete the fields for the selected scope.
  - **Retention period days**: Select **30 days**, **60 days**, or **90 days**. The default is **90 days**.
  - **Custom days**: Enter a number of days. Days are counted in calendar dates, not 24-hour periods. For example, **1** deletes all records before today and keeps today's records.
  - **From date** and **To date**: Enter the first and last date of the range. Records on both dates are included.
5. Optional: To run the cleanup as a batch job, complete the **Run in the background** section.

For more information, see [Schedule a recurring cleanup](/manufacturing/docs/clean-up-the-ecm-change-log-history#schedule-a-recurring-cleanup).
6. Select **OK**.

The records in the selected scope are deleted from the change log.

> [!NOTE]
> Note
> 
> You can't undo a deletion. Check the scope and dates before you select **OK**.

## Schedule a recurring cleanup

You can run the cleanup as a batch job with any scope.

1. In the **Clean up ECM+ change log history** dialog, select the **Scope** and complete its fields.
2. In the **Run in the background** section, set **Batch processing** to **Yes**.
3. Optional: Enter a **Task description**. Select a **Batch group**, and set **Private**, **Critical Job**, and **Monitoring category** as needed.
4. Select **Recurrence**.

The **Define recurrence** dialog opens.
5. Set when the job starts, how often it runs, and when it ends.
  - **Start date**, **Start time**, and **Time zone**: When the first run starts.
  - **No end date**: The job keeps running until you stop it.
  - **End after**: The job stops after the number of runs you enter.
  - **End by**: The job stops on the date you enter.
  - **Recurrence pattern**: Select **Minutes**, **Hours**, **Days**, **Weeks**, **Months**, or **Years**, and enter a **Count**. For example, **Days** with count **1** runs the job every day.
6. Select **OK** to close the **Define recurrence** dialog.
7. Optional: Select **Alerts** to choose when you're notified about the batch job.

The **Batch job alerts** dialog opens.

Select **OK** to close the dialog.
  - **Ended**: Notify when the job ends.
  - **Error**: Notify when the job ends with an error.
  - **Canceled**: Notify when the job is canceled.
  - **Show pop-ups**: Show the alerts as pop-ups as well.
8. Select **OK**.

Result: The cleanup runs as a batch job on the schedule you set.

> [!NOTE]
> Note
> 
> For ongoing housekeeping, use **Retention period** with a daily recurrence. This keeps a rolling 30, 60, or 90 days of history. A **Date range** uses fixed dates, so every run uses the same range.

## Related

- [Track actions in the change log - Impact workspace](/track-actions-in-the-change-log-impact-workspace.md)