See us at ProductCon in SF on Oct. 8th! Check out #03_resources-and-events channel for more info.
just initialized web script, certain user has 180 "Session Recording Checkpoint" events at a same time. how can I troubleshoot this?
If you are seeing 180 "Session Recording Checkpoint" ($mp_session_record) events for a single user at the same time, this likely indicates that the session recording is being started multiple times in quick succession. Here are steps to troubleshoot this issue: 1. Check Your Initialization Logic
Ensure that mixpanel.start_session_recording() is not being called multiple times unintentionally. This can happen if the initialization code is placed in a part of your app that runs repeatedly (e.g., inside a component that re-renders or a function that is called multiple times). The $mp_session_record event is triggered each time a session recording starts, so repeated calls will generate multiple events at the same timestamp.2. Manual Triggering
If you are using manual capture, verify that you are not calling start_session_recording() in response to multiple triggers or user actions that could overlap. The documentation notes that calling start_session_recording() has no effect if a recording is already in progress, but if your code is re-initializing the SDK or not properly checking state, you may still see multiple events logged Implement Session Replay (Web) - Debugging.3. Sampling Configuration
Review your sampling configuration. If you are using a very high sampling rate or have logic that overrides the sampling with repeated manual starts, this could also contribute to excessive checkpoint events.4. Debugging Steps
- Use the browser console to inspect when and how often start_session_recording() is called.
- Check your app’s event flow to ensure the Mixpanel SDK is initialized only once per session.
- Look for any loops or repeated renders that might be causing the SDK or session recording to re-initialize.5. Validate in Mixpanel
Use the Events view in Mixpanel to filter by the affected user's distinct_id and inspect the raw event payloads and timestamps. This can help confirm if the events are truly simultaneous and if any properties indicate the source of the repeated triggers Debugging: Validate your data and troubleshoot your implementation.If after these checks you are still seeing unexpected behavior, consider reaching out to Mixpanel Support for further assistance, as recommended in the documentation Implement Session Replay (Web) - Debugging.---Summary:
Multiple "Session Recording Checkpoint" events at the same time usually point to repeated or unintended calls to start session recording. Review your initialization and event triggering logic to ensure session recording is only started once per session. Use Mixpanel’s debugging tools to trace the source of the issue.
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.
Hi Eliott C., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
