{"command":{"effect":"write","timeoutSeconds":30,"inputSchema":{"type":"object","description":"To permanently delete Signals conversation data, send a POST request to\n`/v1/signals/deletions`. Deletion cannot be undone.\n\nTwo deletion types are supported:\n\n- `agent` — deletes Signals conversations for one Harness Runtime environment and\n  turns off collection for that environment. Requires `environment_id` (the\n  environment's Environment Config ID). Deprecated `agent_id` is still accepted;\n  both set and equal is accepted, both set and different returns 400. On create,\n  matching conversations are hidden from Signals reads immediately. Wait until the\n  job is `complete` before enabling Signals for the environment again.\n- `inference` — deletes Serverless Inference Signals conversations for your\n  whole team (team-wide; not limited to one endpoint or model) that were\n  collected at or before the deletion request, and turns off team inference\n  collection (`source=inference`). Do not send `environment_id` or `agent_id`.\n  On create, matching conversations are hidden from Signals reads immediately.\n\nThe job runs asynchronously; poll the get endpoint until `status` is\n`complete` or `failed`. DigitalOcean may retry transient processing errors\nwhile a job is still active. If a job ends as `failed`, matching\nconversations stay hidden and collection stays off; send the same create\nrequest again to retry. Earlier export files are not deleted and remain\navailable until they expire.\n\nNote: Deletion removes Signals conversation data for the requested scope.\nAggregated Insights or metrics charts may still show historical summary\ndatapoints after deletion. Those summaries are not the same as recoverable\nconversation content.\n\nThe endpoint is idempotent: if a queued or running job already exists for\nthe same target, it is returned with `200 OK`. A new job returns\n`202 Accepted`. Each team can have a limited number of active jobs;\nrequests beyond that limit return `429 Too Many Requests`.\n","properties":{"body":{"$ref":"#/definitions/create_deletion_request","examples":[{"type":"agent","team_id":12345678,"environment_id":"01a10d3f-2c09-764f-99f8-458e521627f3"}]}},"required":["body"],"additionalProperties":false,"definitions":{"create_deletion_request":{"type":"object","description":"Request body to create a new signals data deletion job.","properties":{"type":{"type":"string","description":"The scope of the deletion. `agent` deletes Signals conversations for one Harness Runtime environment and requires `environment_id` (or deprecated `agent_id`). `inference` deletes Serverless Inference Signals conversations for the whole team (team-wide; omit `environment_id` and `agent_id`).","enum":["agent","inference"],"examples":["agent"]},"team_id":{"type":"integer","description":"The team whose data should be deleted. Must match the authenticated team.","examples":[12345678]},"environment_id":{"type":"string","format":"uuid","description":"The Harness Runtime Environment Config ID of the environment whose conversations should be deleted. Required when `type` is `agent` if `agent_id` is omitted; must be omitted when `type` is `inference`. Prefer this over `agent_id`.","examples":["01a10d3f-2c09-764f-99f8-458e521627f3"]},"agent_id":{"type":"string","format":"uuid","description":"Deprecated alias for `environment_id`. Accepted for backward compatibility; must equal `environment_id` when both are set. Both set and different returns 400. Required when `type` is `agent` if `environment_id` is omitted; must be omitted when `type` is `inference`.","examples":["01a10d3f-2c09-764f-99f8-458e521627f3"]}},"required":["type","team_id"],"additionalProperties":false}}},"name":"Create a Data Deletion Job","id":"digitalocean.signals_create_deletion","example":{"body":{"type":"agent","team_id":12345678}},"maxRequests":1,"summary":false}}