Mohammed MohsinFounding EngineerOmi
Omi's account deletion flow, which removes each user's screen-activity vectors keyed by user id from Pinecone.
GitHub, BasedHardware/omi, published Read the pull request (opens GitHub, BasedHardware/omi in a new tab)
Observation
In a production incident at Omi, account deletions failed on one step because one call site sent Pinecone deletes of more than 1,000 ids, which Pinecone rejects with a 400.
- Takeaway
- Chunk every bulk delete and upsert to Pinecone's per-request limits, and test deletion on accounts with more than 1,000 records.
- What happened
- Omi's pull request, opened Aug 31, 2026, says account deletions had been failing in production on one step: Pinecone rejects a delete carrying more than 1,000 ids with a 400, so an account with more than 1,000 screenshots could not be deleted at all. Omi's own diagnosis is that this one call site was missed when deletes were chunked elsewhere. The fix chunks the call and was merged Sep 1, 2026.
- Public engineering write-up (Omi's own pull request)
- Cause stated by the team
- Opened Aug 31, 2026
Deployment details
Omi's account deletion flow, which removes each user's screen-activity vectors keyed by user id from Pinecone.
- Public engineering write-up (Omi's own pull request)
- Cause stated by the team
- Opened Aug 31, 2026
- Team
- Omi
- Duration
- Fixed Sep 1, 2026
- Workload
- Deleting a user's screen-activity vectors keyed by user id
- Measurement
- Deletes above 1,000 ids rejected with a 400



