# Brinqa 11.34.71 rejects duplicate unique identifiers on manual entry

NEWS, 29 Sep 2026, read 10 Nov 2026

**The short answer.** Brinqa released platform patch 11.34.71 on September 29, 2026. One fix rejects a manually created record whose unique identifier value already exists, instead of leaving a partial record that slowed consolidation. The change bears on asset identity matching in any migration that loads records by hand.

Brinqa's documentation lists 11.34.71 as a patch update to the 11.34 release. The data consolidation entry says a guardrail now rejects manual creation of a record with a unique identifier value that already exists, where previously it left a partial record behind that slowed consolidation and left it at partial success.

The same release repeats a fix from 11.34.24 that keeps the record identifier of ad hoc remediation requests stable after creation, to prevent duplicate or inconsistent records.

A migration that loads assets or findings through files or the API depends on stable identifiers. The notes do not say whether the guardrail applies to connector-loaded records, so test the load path you plan to use.

## Sources

- Brinqa 11.34.71 rejects duplicate unique identifiers on manual entry: https://docs.brinqa.com/docs/v11/releases/platform/11-34-71 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-platform-11-34-71-identifier-guardrail/
