Memory and termbase deletion traces

When an entry disappears from a translation memory or termbase, deletion traces tell you who deleted it and when. Each entry deleted on its own or from a selection gets its own trace line. Operations that remove many entries at once, such as a purge, get one summary line.

Deletion traces are off by default. Contact Wordbee Support to turn them on for your platform. Once they are on, the text of each deleted entry is stored in its trace line. Any user with administrator access rights can read it until the trace is deleted, 45 days later.

READING DELETION TRACES

Deletion traces are written to the same log as all other traces. Read them with the existing methods, which all require administrator access rights:

All three return the same lines. To find every deletion, keep the lines where oc is "seg". Then use the op item in flds to tell the operations apart.

Traces are kept for 45 days. Download them regularly.

There are two kinds of line:

Kind

Written for

How to recognise it

Entry line

Each entry deleted on its own or from a selection

key contains sid

Summary line

A purge, a language removal, an import batch deletion or an undo

key contains only dsid. flds contains the operation and its counts

COMMON PROPERTIES

All deletion traces use the standard trace properties, with these values:

a

Always "d" (deletion).

string

oc

Always "seg".

string

key.dsid

ID of the translation memory or termbase.

int

key.sid

ID of the deleted entry. Entry lines only.

int

uid

The user who ran the deletion. Always set.

int

cid

The company the user belongs to.

int

dt

UTC date and time of the deletion.

datetime

ts

Operation ID. All lines written by one deletion share it. For example, deleting 100 selected entries gives 100 entry lines with the same ts.

string

tsc

Short English description of the operation (see each event below).

string

flds

The deletion details, described per event below. All values are strings. Items have no p (previous value).

object[]

ENTRY DELETED

Written once for each entry deleted in any of these ways:

  • Terminology Management: deleting a concept, or deleting the selected entries of a page.

  • Editor: deleting an entry from a memory or termbase grid, or from the translation finder.

  • API: resources/segments/view/delete.

op

"delete"

string

{locale}

The entry text in one language. The item name is the locale code, for example "en". See below for which language is used.

string

langs

Comma-separated locale codes of every language the entry had, for example "en,de,fr".

string

tsc: "Delete entry"

The entry text is recorded in one language only. Entries can have dozens of languages, so recording all of them is not practical:

  • Normally the resource's source language is used.

  • If the entry has no text in that language, the first language in the resource's language order that has text is used.

  • For a termbase entry with several terms in that language, only the first term is recorded.

  • Text longer than 500 characters is cut and ends with "…".

Example: termbase entry

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 4618, "sid": 987654 },
  "uid": 1234, "cid": 56, "dt": "2026-10-07T09:36:32.4119876Z",
  "ts": "3f2b9c1e-6a1d-4c55-9a0e-1b7f2d8e4c10", "tsc": "Delete entry",
  "flds": [ { "f": "op", "v": "delete" },
            { "f": "en", "v": "delivery note" },
            { "f": "langs", "v": "en,de,fr" } ] }

Example: memory entry with no text in the source language. The source language is English, but the entry only has German and French, so the German text is recorded.

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 5120, "sid": 1203344 },
  "uid": 1234, "cid": 56, "dt": "2026-10-07T09:41:05.1830211Z",
  "ts": "9a7d4e02-1f3b-47c8-b2a6-5c0e8f913d27", "tsc": "Delete entry",
  "flds": [ { "f": "op", "v": "delete" },
            { "f": "de", "v": "Der Lieferschein muss vor dem Versand vom Lager unterschrieben werden." },
            { "f": "langs", "v": "de,fr" } ] }

Volume limit. One deletion writes at most 200 entry lines. If it removes more entries, the rest are counted in one remainder line. That line has the same ts and no key.sid. Today, deletions from a selection are limited to 100 entries, so you will normally not see this line.

op

"delete"

string

detailed

Number of entries that got their own entry line ("200").

string

deleted

Number of further entries removed without an entry line.

string

tsc: "Delete entries (remainder)"

RESOURCE PURGED

Written once when a translation memory or termbase is emptied, either with Purge in Wordbee Translator or with resources/items/{dsid}/actions/purge. No entry lines are written.

op

"purge"

string

deleted

Number of entries removed.

string

cancelled

"true" if the purge was cancelled before it finished. deleted then counts the entries removed before the cancel. Absent otherwise.

string

tsc: "Purge resource"

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 4618 },
  "uid": 1234, "cid": 56, "dt": "2026-10-07T10:02:11.0573348Z",
  "ts": "c81e0f4a-2b7d-4e93-8f16-7a5d2c9b0e44", "tsc": "Purge resource",
  "flds": [ { "f": "op", "v": "purge" },
            { "f": "deleted", "v": "12408" } ] }

LANGUAGE REMOVED

Written once when a language is removed from a translation memory or termbase. Entries that had only that language are deleted. Entries that had other languages lose that language's text and are kept. No entry lines are written.

op

"removelanguage"

string

locale

Locale code of the removed language.

string

deleted

Number of entries removed because they had only this language.

string

modified

Number of entries kept but stripped of this language.

string

tsc: "Remove language"

Changing the languages of a project does not delete entries and writes no line.

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 4618 },
  "uid": 1234, "cid": 56, "dt": "2026-10-07T10:15:48.7720915Z",
  "ts": "5d0b7c3e-91a4-4f2e-a6d8-0e3c7b1f5a92", "tsc": "Remove language",
  "flds": [ { "f": "op", "v": "removelanguage" },
            { "f": "locale", "v": "it" },
            { "f": "deleted", "v": "37" },
            { "f": "modified", "v": "2140" } ] }

IMPORT BATCH DELETED

Written once when an import batch is deleted, either from the resource's import history or with resources/documents/{did} (delete). No entry lines are written.

The existing import batch trace (oc "d") is still written. This line is added so that a filter on oc "seg" finds every deletion.

op

"deletebatch"

string

did

ID of the import batch.

string

batch

Name of the import batch. In rare cases the name cannot be read and this item is absent. did still identifies the batch.

string

deleted

Number of entries removed.

string

cancelled

"true" if the deletion was cancelled before it finished. deleted then counts the entries removed before the cancel. Absent otherwise.

string

tsc: "Delete import batch"

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 4618 },
  "uid": 1234, "cid": 56, "dt": "2026-10-07T11:20:03.3391604Z",
  "ts": "e4a91b07-3c6f-4d28-9b51-8f0d2a7c6e13", "tsc": "Delete import batch",
  "flds": [ { "f": "op", "v": "deletebatch" },
            { "f": "did", "v": "88231" },
            { "f": "batch", "v": "glossary-2026-10.tbx" },
            { "f": "deleted", "v": "3012" } ] }

CHANGES UNDONE

Written once when the changes to a translation memory or termbase are undone, either from a date onwards or for one transaction (API: POST /api/resources/segments/actions/undo). Entries left with no text are deleted. The other entries go back to their earlier text. No entry lines are written.

The line is written even if no entry was deleted. It is also written if the undo stopped early, with counts that cover what was done before it stopped. Undoing changes in a project or a job writes no line.

op

"undo"

string

after

For a date-based undo: changes made at or after this UTC date were undone.

string

transaction

For a transaction-based undo: the ID of the undone transaction. Replaces after.

string

examined

Number of entries checked.

string

modified

Number of entries restored to their earlier text.

string

deleted

Number of entries removed because no text was left.

string

cancelled

"true" if the undo stopped before it finished, whether it was cancelled or failed. Absent otherwise.

string

tsc: "Undo changes"

JSON
{ "v": 1, "m": 22358, "a": "d", "oc": "seg",
  "key": { "dsid": 4618 },
  "uid": 1234, "cid": 56, "dt": "2026-10-10T08:47:29.6602178Z",
  "ts": "1b6e3d90-7a2c-4f85-8e4b-d93c05a17f6e", "tsc": "Undo changes",
  "flds": [ { "f": "op", "v": "undo" },
            { "f": "after", "v": "2026-10-09T00:00:00Z" },
            { "f": "examined", "v": "5200" },
            { "f": "modified", "v": "1800" },
            { "f": "deleted", "v": "3000" } ] }

WHAT IS NOT TRACED

Action

Why

Editing an entry, or importing with overwrite

The entry is kept. Only its text changes.

Project memories

Their entries cannot be deleted one by one.

Deleting a whole translation memory or termbase

Already traced as a resource deletion (oc "ds").

Deletion traces are written on a best-effort basis. In rare cases a line can be missing: for example, if the trace log is unavailable at the time of the deletion, the deletion still succeeds but its line is lost. Two users who delete the same entry at the same moment can both appear in a line for it. Do not treat deletion traces as a guaranteed audit record.