Check-ins | No person ID

[michaelhvisser]

Affected Product
Which product does this bug affect?
Check-Ins

Describe the bug
There are people in the database with no Person ID.

Org ID: 106138

To Reproduce
Used postman to find this record.

Expected behavior
All people should have a Person ID

Can you please ensure that there are no other people that are missing a Person ID. Thanks!

[github-actions]

Potentially Related Issues

I found some existing issues that may be related to this one. Please check if any of them address your question before waiting for a response:

🟣 #1423 — Check-ins - No Person ID (Closed)

Summary: Nearly identical issue where a Check-Ins person record lacked a person ID in Org 57001. Initially resolved by removing a duplicate, but follow-up comment indicates the problem recurred months later, suggesting an underlying root cause that wasn't addressed.

Key discussion points:

• Initial duplicate person record without ID was found and removed
• User reported the issue recurring months later (May 2026) with person records still appearing without IDs
• User requested a more holistic investigation into the root cause rather than just removing individual duplicates
• Problem appears to be systemic rather than a one-time data issue

Resolution: Initially resolved by removing the specific duplicate record, but user's follow-up comment indicates this was only a temporary fix and the underlying issue persists. The root cause appears unaddressed, as new person records without IDs continue to appear.

🟣 #1373 — Person without a Person ID (Closed)

Summary: Same issue where the Check-Ins API returned a person record without a person ID in Org 27471. Discovered to be an unused duplicate person record created in 2019 that was never used for any Check-Ins activities.

Key discussion points:

• Issue discovered when fetching people via the /check-ins/v2/people endpoint
• Duplicate person record was created in 2019 alongside a legitimate record that the org has been using
• The duplicate had no Check-Ins activities associated with it
• Problem was resolved by removing the unused duplicate record

Resolution: Resolved by identifying and removing an unused duplicate person record from 2019. The org had a legitimate person record they were using, and the duplicate was safely removed.

---

This comment was generated automatically. If none of these match your issue, no action is needed — a team member will review your issue soon.

[michaelhvisser]

Hey @tlrobrn — any chance you can clean up the issue for the affected org ID and keep working toward the full solution? I'd rather avoid a temporary patch we'd just need to revert once the real fix lands.

[jbiakcin]

Hi @michaelhvisser! We've cleaned up the data for the mentioned org. I'm going to keep this issue open since we're still working on finding the root cause.