> ## Documentation Index
> Fetch the complete documentation index at: https://interfere.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Session replay

> Watch the steps leading up to an error.

Open a session from a [problem](/docs/product/problems.md) or [user profile](/docs/product/users.md) to review the pages visited, actions taken, and errors recorded during that session.

![Session events showing a page visit, an uncaught error, and a click on Submit.](https://mintcdn.com/interfere/mSSNkiftx7tEdU0l/images/session-events.png?fit=max\&auto=format\&n=mSSNkiftx7tEdU0l\&q=85\&s=7864307c18d08851224244bb8c9fd71e)

Use the event timeline to find an error and the actions around it.

## Start from a problem

Open the problem's sessions and select one to replay. Filter by visited URL when the issue involves a particular route, such as `/checkout`.

The session's other events stay available for context. Select an error to start playback up to seven seconds before it, where recording data exists. Use the event timeline to compare the user's actions with the error and its trace.

## Start from a user

Open a profile in **Users**, then select a recorded session. This is useful when a customer reports a failure but you do not yet know which problem caused it.

## Missing recordings

A session can have events without replay data. Replay must be enabled and the `replay` consent category must be allowed while the session is recorded. Enabling it later cannot recover an earlier recording.

Configure [consent](/docs/sdk/consent.md) and [replay masking](/docs/sdk/replay-privacy.md) in your app. Blocked elements appear as placeholders, and masked content stays masked during playback.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.