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?
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:
1. Fix Your Implementation: Update your code to only call reset() when there is a definite intent to change users on the same device (e.g., when a new user signs up, not just on every logout). This will prevent further unnecessary ID generation and merging, helping you avoid hitting the cluster limit again in the future. More details on best practices can be found here and here.
2. Existing Cluster Limit Issue: Unfortunately, the knowledge sources do not describe a self-service way to recover or merge clusters once the 500 ID limit has been reached. When this happens, any new IDs will be orphaned, and you will see duplicate user profiles in Mixpanel. The documentation suggests that if you are running into this limit, you should revisit your implementation and consider removing unnecessary reset() calls, but it does not provide a direct remediation for clusters that have already hit the limit.
3. Contact Mixpanel Support: If you have already exceeded the cluster limit and need to remediate historical data or merge orphaned profiles, the recommended approach is to reach out to the Mixpanel support team. They may be able to assist with advanced remediation steps, such as deleting problematic events or providing guidance on data cleanup and re-import strategies. This is especially relevant if you need to fix historical data or recover from a "hot shard" scenario, as described in the hot shard recovery documentation.
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
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.
