How to Reproduce "Can't Reproduce" Bugs With Session Replay

"Works on my machine." "Cannot reproduce." "Need more info." These are the most expensive phrases in software development. Every round of back-and-forth with a user costs hours, and many real bugs get closed because nobody could see what happened.

Session replay ends that loop. You watch the exact session—clicks, inputs, network requests, console errors—and reproduce the bug on the first try.

Table of Contents

1. Why Bugs Are Hard to Reproduce
2. What a Replay Gives You
3. The Workflow
4. Finding the Right Session
5. Reading the Timeline
6. Common Bug Patterns Replay Reveals
7. Key Takeaways

Why Bugs Are Hard to Reproduce

• Users can't describe what they did.
• The bug depends on a specific browser, viewport, or extension.
• It depends on data state (a specific account, cart, or project).
• It depends on timing (slow network, double clicks).
• The error message was never shown—the UI just froze.

What a Replay Gives You

The Workflow

1. Identify users in your app so you can search by user ID or email (SDK API).
2. When a ticket arrives, search sessions for that user around the reported time.
3. Jump to the moment of the error or rage click on the timeline.
4. Read the console and network around that moment.
5. Reproduce locally with the same browser, viewport, and steps.
6. Link the replay in the ticket for whoever fixes it.
7. After deploying, check that the error group stops occurring.

Finding the Right Session

• By user: search by identified user ID or email.
• By error: open JavaScript Errors, pick the group, open a session where it occurred.
• By frustration: filter sessions with rage clicks on a specific URL.
• By page and time: filter by URL and date range.

Session filters cover all of these.

Reading the Timeline

Look for this sequence:

1. User action (click, submit)
2. Network request fires
3. Response returns an error status or unexpected payload
4. Console error
5. UI doesn't update, or shows a broken state
6. User repeats the action (rage click) or leaves

That sequence usually points straight to the bug.

Common Bug Patterns Replay Reveals

• Unhandled API errors — spinner forever.
• Race conditions — double submit creates duplicates.
• Stale cache after deploy — chunk load errors on navigation.
• Third-party script failures — payment or chat widgets blocked by ad blockers.
• Browser-specific CSS — buttons off-screen on Safari.
• Extension conflicts — translation or password manager extensions mutating the DOM.

Key Takeaways

• Replay turns "cannot reproduce" into "here's exactly what happened."
• Identify users so support and engineering can find sessions fast.
• Read the action → request → error → UI sequence.
• Link replays in tickets.

Conclusion

The fastest bug fix is the one you can see. Give your engineers replays and watch "cannot reproduce" disappear from your tracker.

Start free · JavaScript error tracking guide