# Archive Inactive Anomalies

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

Add an **Archive** action to a Flow to automatically move anomalies into an archived state after they have been inactive for a set amount of time. This keeps the active queue clean while preserving the historical record. For the evaluation mechanics behind the action, see [Anomaly](https://userguide.qualytics.io/flows/actions/deep-dive/anomaly/).

> **Tip: Why archive instead of delete?**
>
> Archiving lets you clean up the active queue without losing historical context. Need to remove anomalies completely? Use [Delete](https://userguide.qualytics.io/flows/actions/how-tos/anomaly/delete-inactive-anomalies/) instead.

> **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 archived. 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. |
| **Options** | Yes | Radio | The archive reason recorded on the anomaly, **Discarded** by default: - **Resolved**: a legitimate data quality concern that has been addressed. - **Invalid**: not a legitimate data quality concern. - **Discarded**: no longer being reviewed or considered relevant. `Duplicate` is not offered here because it requires manually linking a primary anomaly. |
| **Assign additional tags** | No | List | Tags applied automatically to every anomaly archived through this Flow, useful for labeling cleanup runs (e.g., `auto-archive-q4`). |
| **Comment** | No | Text | A free-text note added to every archived anomaly. Use `@mentions` to notify specific users. Plain text only, Markdown formatting is not supported. |

### Filter Conditions

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

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Source Datastores** | Conditional | List | Archive only anomalies 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 archiving to specific open statuses. Only open statuses appear; already-archived anomalies are excluded from the candidates by default. |
| **Anomaly Tags** | No | List | Archive 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 **Archive**. The **Archive 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.*
