AckdbDeleteEventsResponse

Response from DELETE /data/events. A committed delete returns `deleted` (per-table counts); a dry-run returns `resolved` + `wouldDelete` with the identical report. `retained` says what was deliberately left standing; `pendingRebuild` reports, per entity+source pair, the derived content removed now and the surviving payloads queued for re-embedding.

Properties

dataobjectrequired
dryRunbooleanrequired

Whether this was a preview (true) or a committed delete (false).

deletedobject

Per-table counts actually deleted (committed delete only).

eventsinteger
rawPayloadsinteger
filesinteger
contentChunksinteger

Embedding chunks deleted — the affected pairs' message-derived chunks plus the deleted files' chunks (chunks a surviving file references are kept).

conversationsinteger

Conversation rows deleted because they contained a deleted payload.

blobsinteger

File blobs deleted from the file store (best-effort, post-commit).

wouldDeleteobject

Per-table counts that WOULD be deleted (dry-run only). Same keys as `deleted`; `blobs` equals `files` (one stored blob per attached file).

eventsinteger
rawPayloadsinteger
filesinteger
contentChunksinteger
conversationsinteger
blobsinteger
resolvedarray of

Per-id resolution of the matched events (dry-run only).

idstring
entityIdstring
sourcestring
eventTypestring
summarystring
timestampstring <date-time>
linkedRawPayloadIdstring (nullable)
fileCountinteger
notFoundarray ofrequired

Requested ids that matched no event (reported, never fatal).

string
retainedarray ofrequired

What the delete deliberately left standing: `identity_links` are kept so a corrected re-ingest resolves to the same entity; an `entity` entry flags a company the delete left without source events/payloads (entity delete does not exist — the row stays, resolvable via its links).

kindstringrequired
"identity_links""entity"
entityIdstringrequired
countinteger

identity_links only — how many links the entity keeps.

reasonstringrequired
pendingRebuildarray ofrequired

Per affected entity+source pair: derived content removed in this transaction and the surviving payloads queued for re-embedding. Until the embed/conversations pipelines next run, semantic search and conversation answers for the pair are missing — deliberately (missing is honest; stale is not).

entityIdstringrequired
sourcestringrequired
contentChunksDeletedintegerrequired
conversationsDeletedintegerrequired
payloadsQueuedForReembedintegerrequired
rebuildNotestring

Present when pendingRebuild is non-empty — what is missing and how it comes back.

Example

AckdbDeleteEventsResponse example
{
  "data": {
    "dryRun": false,
    "deleted": {
      "events": 2,
      "rawPayloads": 2,
      "files": 1,
      "contentChunks": 3,
      "conversations": 1,
      "blobs": 1
    },
    "wouldDelete": {
      "events": 1,
      "rawPayloads": 1,
      "files": 0,
      "contentChunks": 2,
      "conversations": 1,
      "blobs": 0
    },
    "resolved": [
      {
        "id": "string",
        "entityId": "string",
        "source": "string",
        "eventType": "string",
        "summary": "string",
        "timestamp": "1970-01-01T00:00:00.000Z",
        "linkedRawPayloadId": "string",
        "fileCount": 0
      }
    ],
    "notFound": [
      "string"
    ],
    "retained": [
      {
        "kind": "identity_links",
        "entityId": "string",
        "count": 0,
        "reason": "string"
      }
    ],
    "pendingRebuild": [
      {
        "entityId": "string",
        "source": "string",
        "contentChunksDeleted": 0,
        "conversationsDeleted": 0,
        "payloadsQueuedForReembed": 0
      }
    ],
    "rebuildNote": "string"
  }
}