---
title: doctl signals deletion
description: |-
    The subcommands of `doctl signals deletion` permanently delete Signals conversation data on demand.

    Deletion cannot be undone. When you create a …
product: Reference
url: https://docs.digitalocean.com/reference/doctl/reference/signals/deletion/
last_updated: "2026-11-19"
---

> **For AI agents:** The documentation index is at [https://docs.digitalocean.com/llms.txt](https://docs.digitalocean.com/llms.txt). Markdown versions of pages use the same URL with `index.html.md` in place of the HTML page (for example, append `index.html.md` to the directory path instead of opening the HTML document).

# doctl signals deletion

Generated on 19 Nov 2026 from `doctl` version [`v2.7.0`](https://github.com/digitalocean/doctl/releases/tag/v2.7.0)

## Usage

```shell
doctl signals deletion [flags]
```

## Aliases

```shell
deletions
```

## Description

The subcommands of `doctl signals deletion` permanently delete Signals conversation data on demand.

Deletion cannot be undone. When you create a deletion for a Harness Runtime agent (`--type agent`) or for Serverless Inference (`--type inference`), Signals turns collection off for that scope immediately, hides matching conversations from Signals reads immediately, and deletes that conversation data asynchronously in the background. Poll `doctl signals deletion get <deletion-id>` until the status is `complete`.

For `--type agent`, set `--environment-id` to the agent’s Environment Config ID (the agent UUID). For `--type inference`, Signals deletes Serverless Inference conversations for your whole team (team-wide; not limited to one endpoint or model) that were collected at or before the deletion request. Do not pass `--environment-id` for inference.

For an agent deletion, wait until the job is `complete` before enabling Signals for that agent again. Earlier export files are not deleted and remain available until they expire.

Status values: queued, running, complete, failed. DigitalOcean may retry transient processing errors while a job is still active. If a job ends as `failed`, matching conversations stay hidden and collection stays off; run `create` again to retry, and use `--format DeletionID,Status,ErrorMessage` to see why it failed.

Note: Deletion removes Signals conversation data for the requested scope. Aggregated Insights or metrics charts may still show historical summary datapoints after deletion. Those summaries are not the same as recoverable conversation content.

## Flags

| Option | Description |
|---|---|
| `--help`, `-h` | Help for this command |

## Related Commands

| Command | Description |
|---|---|
| [doctl signals](https://docs.digitalocean.com/reference/doctl/reference/signals) | Display commands for Signals consent, export, and data deletion management |
| [doctl signals deletion create](https://docs.digitalocean.com/reference/doctl/reference/signals/deletion/create) | Permanently delete Signals data |
| [doctl signals deletion get](https://docs.digitalocean.com/reference/doctl/reference/signals/deletion/get) | Get a Signals deletion job |
| [doctl signals deletion list](https://docs.digitalocean.com/reference/doctl/reference/signals/deletion/list) | List Signals deletion jobs |

## Global Flags

Option Description

`--access-token`, `-t` API V2 access token

`--api-url`, `-u` Override default API endpoint

`--config`, `-c` Specify a custom config file, Default:

`--context` Specify a custom authentication context name

`--http-retry-max` Set maximum number of retries for requests that fail with a 429 or 500-level error , Default: `5`

`--http-retry-wait-max` Set the minimum number of seconds to wait before retrying a failed request , Default: `30`

`--http-retry-wait-min` Set the maximum number of seconds to wait before retrying a failed request , Default: `1`

`--interactive` Enable interactive behavior. Defaults to true if the terminal supports it (default false) , Default: `false`

`--output`, `-o` Desired output format \[text|json], Default: `text`

`--show` Reveal masked values, such as secrets, instead of hiding them. Values are unmasked automatically in CI , Default: `false`

`--trace` Show a log of network activity while performing a command, Default: `false`

`--verbose`, `-v` Enable verbose output, Default: `false`