Session Replay 2.0 error descriptions

Errors that can occur in Session Replay 2.0 and their recommended solutions are given below.

Error Cause/Recommendation
The session can't be replayed. The session couldn't be recorded for technical reasons.
Session Replay was launched incorrectly. Session Replay couldn't record a session because the site contains invalid HTML code (such as the lack of a body element). Check the source code of the pages on your site.
The session couldn't be recorded.
You have exceeded the time limit for storing recordings in Session Replay. Data is stored for 15 days, including the current day. The 15-day storage limit is exceeded.
Session processing timed out. Try refreshing the page. Try replaying the session later.

Select a question to find a solution.

The page content in the recording may be different from the actual content. It's likely that the CSS on the site frequently changes. In this case, add the content hash to the style file names. Then, when you change the file's content, its name will change. For example: style.390b32d4d49d5e7d.css will be changed to style.0c573d460df87d4de5a4.css. This lets Session Replay use the style that the site visitor sees when it records a session.

Do the following:

  • Clear the browser cache.
  • Disable all plugins and browser extensions.
  • Delete browser cookies.
  • Check the firewall settings. The firewall may be blocking the Yandex.Metrica tag script. The tag could also be blocked by the extension Adblock Plus.

If you have more questions about Session Replay, submit them in the form below. Provide an example of the session where data was displayed incorrectly and specify the full version of your browser.