Session Replay error descriptions

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

Error

Advice

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 Session Replay’s time limit for storing recordings. Data is stored for 15 days, including the current day.

The 15-day storage time limit has been exceeded.

Session processing timed out. Try refreshing the page.

Try replaying the session later.

Chat with us

Write an email

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. This will make the file name change every time you update its contents. For example, style.390b32d4d49d5e7d.css will become 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 the browser cookies.
  • Check the firewall settings. It’s possible that the firewall is blocking the Yandex Metrica tag script. The tag could also be blocked by the Adblock Plus extension.
I followed the recommendations, but the error persists

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

Useful links

Online training
Previous
Setting up iframe content recording
Next
FAQ for Session Replay