---
title: Cleanup Sandbox
slug: tv-toolbox/dI48-cleanup-sandbox
icon: {"lucideIcon":"Wrench"}
createdAt: 2026-10-13T09:14:58.273Z
---

*Our Adobe Experience Platform sandboxes get reused constantly. We share them within our teams, lend them to other teams during projects, and hand them to customers during hands-on engagements. Each reuse leaves clutter behind, and that is especially painful in sandboxes with templated content, where the setups people depend on get buried or broken. A full reset throws everything away, and deleting and recreating a sandbox means starting from scratch.&#x20;*

## The solution

The **Cleanup Sandbox** feature cleans a sandbox the way a reset would, but you choose which objects to keep. Cleanup becomes fast, consistent, and reviewable, so handovers are predictable, accidental deletions are avoided, and every removal is recorded. It works best on templated-content sandboxes, but it also helps in custom-content ones when you want to clear out the clutter and keep only the objects worth having.



## Benefits

::::VerticalSplit{layout="left"}
:::VerticalSplitItem
::Image[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/S6F0KbcOlX_8UWCXrGpKy_image.png" size="60" isUploading="false" width="144" height="146" darkWidth="144" darkHeight="146" showCaption="false"}
:::

:::VerticalSplitItem
### Sandbox reliability

*Keep long‑running and heavily used demo sandboxes stable by clearing clutter and conflicts without disrupting the core setups teams depend on.*
:::
::::

::::VerticalSplit{layout="left"}
:::VerticalSplitItem
::Image[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/BmqAMASMUYIk3xfMGXYhB_image.png" size="60" isUploading="false" width="144" height="146" darkWidth="144" darkHeight="146" showCaption="false"}
:::

:::VerticalSplitItem
### Boost productivity

*Provide teams a fast and consistent reset process so they spend less time on manual cleanup and more time delivering value.*
:::
::::

::::VerticalSplit{layout="left"}
:::VerticalSplitItem
::Image[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/hwqqCxM9TiswC3s4zSeXk_image.png" size="60" isUploading="false" width="144" height="146" darkWidth="144" darkHeight="146" showCaption="false"}
:::

:::VerticalSplitItem
### Smooth handovers

*Provide a predictable and standardized cleanup process when sandboxes move between team members, making shared sandboxes easier to reuse.*
:::
::::

::::VerticalSplit{layout="left"}
:::VerticalSplitItem
::Image[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/WrTqcr6BPbkO3z5WmWsUo_image.png" size="60" isUploading="false" width="144" height="146" darkWidth="144" darkHeight="146" showCaption="false"}
:::

:::VerticalSplitItem
### Cleanup governance

*Offer transparent oversight of what’s removed and why, supporting audit needs and reinforcing responsible use of sandbox tooling.*
:::
::::

::::VerticalSplit{layout="left"}
:::VerticalSplitItem
::Image[]{src="https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/jFGVVXyq_Or3VC1w2g_66_image.png" size="60" isUploading="false" width="144" height="146" darkWidth="144" darkHeight="146" showCaption="false"}
:::

:::VerticalSplitItem
### Reduce risk

*Prevent accidental deletions and conflicting cleanup attempts by centralizing cleanup logic into a controlled and reviewable workflow.*
:::
::::





## Apps and categories

You choose which apps to include in each cleanup. Each app has categories of objects.

- **RTCDP** (Real-Time Customer Data Platform): Audiences, Datasets, Field Groups, Schemas.
- **AJO** (Adobe Journey Optimizer): Journeys, Campaigns, Custom Events, Custom Actions, Content Fragments, Content Templates, Offer Decisioning Engine (ODE), Decisioning (new), Data Sources.
- **CJA** (Customer Journey Analytics): Data Views, Connections, Projects.
- **Data**: Dataset Batches.

The ODE category groups Placement, Collection, Decision, Offer, Collection Qualifier, Rule, and Ranking Formula. The Decisioning (new) category groups Offer, Collection, Rule, Strategy, Placement, and Ranking Formula.

Only the 100 most recent dataset batches are included, because of API limits, and a count of 100 is shown as 100+. Removing batches removes the data from the Data Lake only. It does not remove data from the Real-Time Customer Profile store or the Identity Service. For personal data, use the Privacy Service or set pseudonymous profile data expiration on your sandbox.

## Methods

The method you choose decides which items the tool suggests removing. You can change any suggestion before you run the cleanup. Your admin decides which methods are available.

### User group(s)

Items created by users who are not in the user groups you choose are suggested for removal. You can only choose from the groups your admin allows. Items without creator information are kept, and so are schemas and field groups, because they don't return creator information. An item that was created by someone in your groups but last modified by someone outside them is marked **Keep** and flagged for manual review. Click **View items** in the alert to see these items.

### Age

Items last modified before a cutoff are suggested for removal. The cutoff is a number of days, weeks, months, or years counted back from now. Items without a last-modified date are kept.

### Keyword(s)

Items whose name contains any of your keywords are suggested for removal. Matching ignores upper and lower case.

### Manual

Available only if your admin turns it on. <font color="#EF4444">TODO(user)\: confirm the behavior</font>. In the code, every item is suggested as **Keep** and you choose what to remove.

## Rules that always apply

These rules override the method you choose.

- Items created by technical (API) accounts, whose creator ends in `@techacct.adobe.com`, are always **Keep**.
- Out-of-the-box (OOTB) items, whose creator ends in `@adobeid` or `@adobeservice`, are always **Keep**. They can't be changed and are hidden unless you turn on **Show OOTB Items**.
- Only custom schemas and custom field groups can be removed.
- A schema that still has datasets associated with it isn't removed and shows an error.
- Datasets and schemas that are enabled for profile are marked with an **Enabled for profile** icon.

## The wizard

A cleanup runs in five steps: **Configure** (sandbox, reason, method, apps), **Curate** (review what the tool suggests and change **Keep** or **Remove** per item), **Review** (check the final list), **Execute** (run the cleanup and follow its progress), and **Recap** (see the results, including errors).

## Order of removal

The server removes categories in an order that respects dependencies between them. A single item that fails to be removed doesn't stop the cleanup, and the error is recorded.

1. CJA: Projects, Data Views, Connections
2. Data: Dataset Batches
3. AJO: Campaigns, Journeys, Custom Events, Custom Actions, Content Templates, Content Fragments, Offer Decisioning Engine (ODE), Decisioning (new), Data Sources
4. RTCDP: Audiences, Datasets, Schemas, Field Groups

## Statuses, locking, and history

Every cleanup has a status: **Preparing** (being configured, curated, or reviewed), **Executing** (running on the server, and it can't be aborted), or **Completed**. The Cleanup Sandbox page lists every cleanup with its status, sandbox, apps, number of items removed, and who started it.

Starting a cleanup locks the sandbox for other users until the cleanup is completed or aborted. Unfinished cleanups are aborted automatically between 24 and 48 hours after they start.

:::hint{type="danger"}
Once you click **Execute Cleanup**, the cleanup can't be aborted or undone.
:::

## Permissions

The permissions belong to the **Sandbox Tooling** permission resource. **View Cleanup Sandbox** shows the page and the history. **Execute Cleanup Sandbox** starts and runs cleanups. **View Configurations** and **Manage Configurations** show and change the Sandbox Tooling settings, which control the available methods, defaults, and blocked sandboxes.
