Instance Cleaner settings
Set default dependency actions, Cruise Control folders, and the safety guards that decide what Instance Cleaner may delete.
Supported MAPEloqua
These settings live under Settings → Agent context → Instance Cleaner in the product (/settings/agents/adm). They decide how dependencies are handled by default and what Instance Cleaner may never delete.
Open settings
Open Settings
In Agent Studio, go to Settings, then Agent context → Instance Cleaner (
/settings/agents/adm).Select a connection
The screen is gated until an Eloqua connection is selected. Auto actions and Safety guards are stored per connection. Default actions apply across your org.
Configure and save
Each section has its own Save button, so saving one section never changes another. You can also make these changes in chat, for example “protect folder 1024”.
/images/agent-studio/instance-cleaner/settings-overview.pngSettings, Agent context, Instance Cleaner (/settings/agents/adm) with an Eloqua connection selected and the Default actions, Auto actions and Safety guards sections visible. Use a demo instance.
Sections
| Section | What you configure |
|---|---|
| Default actions | For each pair of asset types (the asset being deleted and the asset that depends on it), the action to apply by default: Remove, Replace, or Keep. Replace needs an alternate asset. Unset pairs are left for the user to decide in each Package. Select several rows to set Remove or Keep in bulk. |
| Auto actions | Which folders Cruise Control may pull Completed Campaigns and Programs from when they block a delete. Turn on Allow all folders, or pick folders from the tree or add them by ID. Parent folders include everything nested under them. Leave it empty to turn auto-include off. |
| Safety guards | Require approval before Clear & Delete (off by default; Clear-only runs are unaffected), the Live-asset guard for assets used by an active campaign (Off, Warn, or Block; Block by default), and asset exclusions. |
Asset exclusions
Exclusions are hard rules. Matching assets are never deleted, in any Package, Cruise Control run, or chat request.
- By folder: check folders in the tree, or add folder IDs one at a time or separated by commas. Assets in nested folders are protected too.
- By name: add a rule with a match type (Starts with, Ends with, Contains, or Exact name) and a pattern. Matching ignores case, so keep patterns specific.
/images/agent-studio/instance-cleaner/settings-asset-exclusions.pngThe Safety guards section scrolled to Asset exclusions, with at least one protected folder checked in the tree and one name rule (for example Starts with) added. Use a demo instance.
Approval in practice. When approval is required, no Package on that connection can run Clear & Delete until it has been submitted for review and approved. Ask the agent in chat to submit or approve a Package.
Related
Instance Cleaner
Connections
Agents