Affects
Teams that import reconciliation files, configure Matcher sources, or operate aggregator connections.
What changed
A source can define
duplicate_key as an ordered list of mapped fields when external_id alone is not sufficient. Aggregator-bound sources cannot use a custom key. The default duplicate policy is FLAG_AS_EXCEPTION, not KEEP_FIRST, and changing a duplicate key affects later imports only.
The aggregator connection guide now also requires clients to use the list response’s testable field before offering a connectivity test.
This is a documentation correction that aligns with the implemented contract. It does not announce a runtime release.
Impact
Classification: Action required. Existing import controls that assume silent duplicate drops can produce or handle exceptions differently from the documented default.
What you need to do
1
Review each source’s duplicate policy and exception handling before the next import.
2
Set
duplicate_key only when every selected field is mapped; do not configure it for aggregator-bound sources.3
Use
testable before exposing an aggregator connectivity test in your workflow.