CNT_REG_RACE_LOS
Contact registration lost a race and could not recover
Two concurrent registrations of the same fresh e-mail (or phone-only) contact collided on the partial unique index. The losing transaction retried the lookup five times with exponential backoff (10–200 ms) but never saw the winning row commit on its pool connection, so it re-threw the original 23505 error to its caller. The caller decides whether to surface the failure (strict mode — order/invoice/payment) or fall back to the anonymous shell (lenient — cron / bulk imports).
What this code means
Two concurrent registrations of the same fresh e-mail (or phone-only) contact collided on the partial unique index. The losing transaction retried the lookup five times with exponential backoff (10–200 ms) but never saw the winning row commit on its pool connection, so it re-threw the original 23505 error to its caller. The caller decides whether to surface the failure (strict mode — order/invoice/payment) or fall back to the anonymous shell (lenient — cron / bulk imports).
Where you will see it
- In the subject line of technical-notification e-mails — for example
[CNT_REG_RACE_LOS] [cntHealthcheck] … - As a badge in the admin log viewer at
/log, where you can filter and drill into individual entries. - In the
core__system_logtable, stored against the code id fromcore__system_log_code.