Verify and complete the upgrade
- Latest Dynatrace
- How-to guide
- 2-min read
- Published Nov 03, 2026
After you turn on Session Replay and set up access, verify that recordings are available, that they look right, and that the right people can replay them. Then decide what to do with your Classic configuration.
Verify your setup
Check that replays are available
- Go to
Users & Sessions and open the list of completed sessions of that frontend. A session is completed after 35 minutes of user inactivity. Then it appears in the list of completed sessions. To check a session earlier, find it on Recent. - Check the replay availability indicator. It shows whether Session Replay data is available for the session.
- Replay the session.
For details about the app, see Users & Sessions.
If no replays are available, check the following:
- The frontend has both Real User Monitoring and Session Replay turned on, and the capture rate isn't
0. The capture rate applies to the sessions that RUM analyzes, so with a low value it can take a while until you see a recorded session. - Your agents meet the minimum versions in Upgrade Session Replay data capturing.
- Your account has the permissions to replay sessions. See Upgrade Session Replay permissions and segmentation.
Check the session quality
Open several replays and check that they look like the real user experience and are comparable to replays in Session Replay Classic:
- Pages render correctly: Layout, colors, and fonts match what users see. If pages look broken or unstyled, the stylesheets might be missing. Make sure that resource capture is on and that no URL exclusion rule matches the affected pages. For details, see Configure resource capture.
- Content is complete: Content that is rendered by techniques that Session Replay doesn't support, such as canvas, WebGL, or frames, doesn't appear in the replay. For details, see Technical restrictions for Session Replay for web frontends.
- iFrames are shown: For iFrames, the RUM JavaScript must be injected into each iFrame, and the same frontend must monitor the parent page and the iFrame.
- Mobile screens are complete: For mobile apps, check the screens that use custom views or animations, because a replay is a reconstruction and can differ from the actual screen.
Check masking and access
- Check that sensitive fields, such as input fields for personal data, are masked in the replay. For details, see Configure masking.
- Check that a user with the Read User Replays policy can replay sessions with masking applied, and that only users with the
session-replay:sessions:replay-without-maskingpermission can replay without masking.
Complete the upgrade
After you verified your setup for a frontend, Session Replay Classic stays active next to Session Replay.
At this time, you can't deactivate Session Replay Classic.
Session Replay Classic and Session Replay use different permissions. As long as you use Session Replay Classic, keep the Classic permissions Replay session data with masking and Replay session data without masking for your user groups, in addition to the IAM permissions for Session Replay.
Existing Session Replay Classic recordings keep the Classic retention. They are deleted when their retention period ends.
Known limitations
A replay is a reconstruction of the session from captured events and data, so it can differ from the actual user experience. For the restrictions of web frontends, see Technical restrictions for Session Replay for web frontends.