Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" is a real answer.
1Clean up the duplicate person records a merge race left in three customer companies?
In plain terms. A bug sometimes made two or three profiles for one renter. It's fixed now, but about 10 renters across three customers still have extra profiles. Should we check which ones are real duplicates and then merge them?
Why, and what was tried
The session raising this recommends: Dry-run merge first A read-only count found 10 groups, 21 records, in three customer companies. Some may be real co-tenants or cosigners, so the repo's merge script should run its dry run with the name check first and show which ones are true duplicates before anything changes. Tried first, unsuccessfully: Counted read-only in prod: org_jpco 7 groups/14 records, a third customer org 2/4, western slope 1/3. Upper bound: shared phone can be legitimate. The race that created them is fixed (#17652, follow-up #17710). No prod rows were touched.