Mixpanel Community Icon

Home
Groups
Members

Announcements
Community Questions
Mixpanel Bot
Product Ideas
Resources

Community Guidelines

Docs & Guides
Events & Webinars
Contact Us

Powered by Tightknit

Resolving Mixpanel Identity Cluster Limit Issues | Mixpanel Community

Resolving Mixpanel Identity Cluster Limit Issues

·Aug 07, 2025 01:15 AM·

kapa.ai I think I’ve exceeded the identity cluster limit in Mixpanel due to misusing the reset() logic. I’m planning to fix the reset logic moving forward, but in the meantime—what can I do to resolve or recover from the cluster limit issue?

2 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Please stand by 김태수 (. as I search the knowledge base. I normally take about 15 seconds or so. 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
If you have exceeded the identity cluster limit in Mixpanel (500 distinct IDs per cluster for projects using the Original ID Merge API), this typically happens when reset() is called too frequently—often in scenarios where multiple users share a device. Once this limit is reached, new distinct IDs can no longer be merged into the same cluster, resulting in orphaned (duplicate) user profiles and a fragmented view of the user journey.Immediate Steps:Summary: - Fix your reset() logic to prevent further issues. - There is no automated way to recover clusters that have already hit the 500 ID limit. - Contact Mixpanel support for help with remediation of existing data and to discuss possible solutions for your specific case.For more details, see: - Migrating to Simplified ID Merge: On Original ID Merge
- Best Practices: Identifying Users (Original) - Hot Shard Limits: Fix historical data
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.