Investigate with session replay

Session replay shows what happened in the browser. Use it to understand the customer-visible steps around an error, then follow the linked Issue and backend evidence instead of treating the recording as the complete explanation.

Find the right recording

Open Explore → Replays and search by customer or session ID. Check the start time and duration before opening a recording. When you begin from a customer timeline or Issue, prefer the replay linked there because it already preserves the relevant person and failure context.

The recording list belongs to the active project. If a known session is absent, confirm the project before changing replay capture settings.

Read the timeline

Play the session once to understand the journey, then use the timeline markers to revisit failed requests and captured errors. A marker is evidence that something happened at that time; it is not by itself proof of the cause.

Use the panels below the player deliberately:

• Console shows browser console entries only when console capture was enabled.
• Network shows captured request activity and failed-request markers only when network capture was enabled.
• Errors shows errors related to the session and links grouped failures back to their Issue.

Select an entry to seek to its point in the recording. Use the Person link to return to the customer story, and review Events in this session for meaningful application actions. On a narrow screen, the player and context panels stack vertically and the recording stays within the available page width, so use the same controls without horizontally scrolling the dashboard.

Follow the backend evidence

A replay becomes much more useful when browser requests propagate W3C traceparent and trusted identity context to an instrumented backend. From the related error or customer timeline, open the trace and logs for the same moment. Keep the project, environment, and time window unchanged while you compare them.

If the replay has missing chunks, treat the visible portion as incomplete. Network loss, page termination, blocked uploads, or retention can create gaps; do not infer that an action did not happen merely because it is not visible.

Protect customer data

Replay is intentionally opt-in. Input masking is enabled by default, while console and network capture can contain sensitive application data. Enable them only after reviewing what the application logs and sends. Anectico cannot reconstruct data that was masked in the browser.

If the player is empty, the wrong session is linked, or expected panels contain no data, see Replay or symbols are not working.

• Record session replay safely
• Understand one customer’s story