# Delete Inactive Anomalies

Source: https://userguide.qualytics.io/flows/actions/how-tos/anomaly/delete-inactive-anomalies/

Add a **Delete** action to a Flow to permanently remove anomalies after they have been inactive for a set amount of time. This fits cases where you don't need to keep a record of the anomaly, for example short-lived data or noise you just want to clear out. For the evaluation mechanics behind the action, see [Anomaly](https://userguide.qualytics.io/flows/actions/deep-dive/anomaly/).

> **Warning: Delete is permanent**
>
> A Delete action removes the anomaly record, its comments, and its links to tags, assignees, and external tickets, and it cannot be undone. To keep the history, use [Archive](https://userguide.qualytics.io/flows/actions/how-tos/anomaly/archive-inactive-anomalies/) instead. Review [What a Delete Removes](https://userguide.qualytics.io/flows/actions/deep-dive/anomaly/#what-a-delete-removes) before setting one up.

> **Note: Permission Required**
>
> To edit and publish a Flow, you need the **Editor** team permission on every datastore it relates to. Admins are exempt. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/) for details.

## Field reference

The settings panel is split into two sections, **Configuration** and **Filter Conditions**.

### Configuration

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Inactivity Period** | Yes | Number | How long an anomaly must remain untouched (no updates or comments) before it's deleted. Defaults to **Quarter**. Pick a preset or type a custom number of days, from 1 to 3,650: - **Week**: 7 days. - **Month**: 30 days. - **Quarter**: 90 days. - **Year**: 365 days. |

### Filter Conditions

All filters are optional, and **all filled-in filters must match** (AND logic). They add on top of the **Inactivity Period**, not in place of it.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Source Datastores** | Conditional | List | Delete only anomalies originating from the selected datastores. Leave empty to consider all datastores. Lists only the datastores you hold the **Editor** team permission on, and is required unless you are an Admin or hold that permission on every datastore. |
| **Anomaly Statuses** | No | List | Restrict deletion to anomalies in specific statuses. Every status appears, including already-archived ones. Leave empty to target every status. |
| **Anomaly Tags** | No | List | Delete only anomalies labeled with the selected tags. |

## Steps

**Step 1**: Navigate to the Flows page by clicking **Flows**  on the left side panel.

**Step 2**: On the **Definitions** tab, click the Flow. On its canvas, click the dashed **Action** placeholder after the trigger, or the **+** handle at the bottom edge of a node.

**Step 3**: In the **List of Actions** panel, pick the **Anomaly** category, then click **Delete**. The **Delete Settings** panel opens on the right-hand side.

**Step 4**: Fill in the fields.

**Step 5**: Click **Save**. The node shows a **CHANGED** badge and the **You have unpublished changes** banner appears on the canvas.

**Step 6**: Click **Publish**  to make the action live.

*Last updated: October 15, 2026.*
