# Fix the translation agent failing to set the memory match threshold at 100 percent

## TL;DR

The agent cannot find the 100 percent threshold setting because it is named differently or lives at a different level, so set it where your TMS actually keeps it. Exact matches at 100 percent usually mean confirmed or locked segments, and the control might be called penalty, leverage, or pre-translate settings. Find the real name, set it, and verify with a test string.

## The error

```text
Translation agent: failed to configure memory match threshold at 100 percent
no such setting found, agent gave up
```

## Fix it

### Step 1: Find what your TMS calls it

```bash
node -e "console.log('search the TMS docs and API for: pre-translate, leverage, match threshold, penalty settings')"
```

Expected: You learn the real setting name and level.

### Step 2: Check whether 100 percent is even configurable

```bash
node -e "console.log('some systems treat 100 percent as confirmed segments only, which is a workflow state not a threshold')"
```

Expected: You know whether to set a threshold or a workflow filter.

### Step 3: Set it at the right level

```bash
node -e "console.log('project vs template vs organization -- the setting must live where the agent job reads it')"
```

Expected: The value is where the job looks.

### Step 4: Verify with a known exact match

```bash
node -e "console.log('run the agent on a string with a known 100 percent match, confirm it applies automatically')"
```

Expected: Exact matches apply as expected.

## When to use this

- An agent cannot configure the 100 percent TM threshold
- The setting name does not match the docs

## When NOT to use this

- The threshold sets but matches are wrong, check the TM content
- You want fuzzy matches too, lower the threshold deliberately

## Tool and version compatibility

- TMS pre-translate and leverage settings
- Translation memory match bands

## Variant phrasings

### threshold applies per language pair

Set it for each pair the agent handles, not just the default.

### API lacks the setting the UI has

Set it in the UI on the template the agent uses, then have the agent reference that template.

## Why it happens

Every TMS names this differently, and some do not expose 100 percent as a threshold at all, treating exact matches as a workflow state. The agent looks for one name, finds nothing, and reports failure instead of adapting.

## Edge cases

- Document the real setting name for your TMS so the next agent finds it
- 100 percent matches still need review in some workflows, check yours
- Changing the threshold changes leverage numbers, warn finance if they watch those

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xybwbd-LsWfFiDaqdho1zA