Things that trip people up
- 1
“My exclusion returns almost nothing.”
Most of your records are unknown on that field. Check
unknown_safety_fieldson a plain search and work the review queue. - 2
“The rules are not matching anything.”
Your synonyms are probably examples rather than words. Check them against a record you have never read, and check that sourceColumns actually includes the column with the text in it.
- 3
“Everything is going to review.”
Either minConfidence is too high for the field, or the field is one a record genuinely cannot answer. A difficulty rating is not usually written down in a catalog; equipment is.
- 4
“I get a 406 from the MCP endpoint.”
Add
Accept: application/json, text/event-stream. Both values, on every POST. - 5
“My PDF only matched a few records.”
A line is matched by the value in the column you chose, as whole words. Pick the column the sheet actually uses (a product code rather than a display name, say), and check *Preview the match*: it lists what it couldn't place, and lines that named two products, which go to neither on purpose.
- 6
“Records went to review saying the sources disagree.”
The record's own words give a safety value the PDF doesn't list. Often the PDF uses a word the contract doesn't have (it says “milk” and dairy's words are butter and cheese): add it to the value's words and run again.
- 7
“I edited a contract and nothing changed.”
Editing bumps the version but does not re-tag anything. Start a run. Values a person locked stay locked regardless, which is usually what you wanted.