Capture a recording before the problem
Start a review session on the intended environment and version
In the extension, ensure Record Session Replays and the needed diagnostic capabilities are allowed for the device/project.
Perform a short test action, then open Session replay in the review toolbar to confirm recorded activity is available.
Reproduce the problem and submit the annotation
End the session normally and allow the final save to finish rather than immediately closing the browser.
Open Dashboard → Replays and locate the session by project/date/source, or open the report's replay window.
Inspect the recorded activity
Use the timeline to seek and change playback speed. Open the recorded clicks, console, and request panels to inspect the context at that point. Selecting a recorded click can seek to it; the DOM inspector examines the captured element rather than your current application DOM.
Use the player's displayed shortcut help; controls depend on focus and the installed player version. Console/network entries only exist when those capabilities were captured.
Portal, Console, and Guest describe recording sources, not a new permission grant. Filters help locate a source; they do not let a guest read staff-only diagnostics.
Replay reconstructs recorded events. Cross-origin frames, unavailable assets, canvas content, sampled activity, and changed application state can limit fidelity. It does not guarantee perfect visuals or re-run the original server requests.
Export and open a local replay
Open the replay player and choose Download replay
Save the exported recording file and keep it private.
To inspect a supported exported .json or .json.gz recording, open Replays → Upload Replay and select that file
Compressed recordings require browser support for gzip decompression. The local player reads it in your browser without creating a new cloud recording.
Confirm that the imported file belongs to the session/version you intend to inspect
An arbitrary JSON file or incompatible export is not a valid replay.
Exporting or importing does not delete the original cloud recording or reduce its storage usage
Manage retained data separately.
Privacy, access, and availability
Recordings and diagnostics can contain application text and data. Review with dedicated test accounts and avoid sensitive values. Input protection does not guarantee that the same data is absent from a page, console message, or request body.
Project diagnostic permissions control cloud evidence access; a downloaded file is a separate copy that can be opened outside those permissions. Share exports only with authorized recipients.
Active review sessions expire after 24 hours of inactivity. Cleanup of expired sessions can remove their replay data after the cleanup grace period; a replay is not a permanent archive. Export any recording you must retain while it is still available.
For unavailable playback, check the project and filters, capture permission, session save state, access, and expiry. Legacy records may not distinguish never-recorded from expired. Start a new capture if the old activity was never recorded.
