Capturing a clean, performant demo replay starts with a solid setup and awareness of what might interfere with the process. Below are best practices and troubleshooting tips to ensure your capture is as accurate and efficient as possible.
Before You Capture
1. Avoid Corporate Laptops and Networks When Possible
Corporate devices and networks (especially when using a VPN) may introduce added security layers or network routing logic. This can interfere with accurate request capture—either by preventing some requests from being captured or by injecting unnecessary ones. If possible, use a personal or non-restricted device on an open network.
2. Disable Unnecessary Browser Extensions
Browser extensions often modify pages by injecting code (e.g., <script>, <div>). These additions can corrupt your capture or introduce objects that aren't part of your application. We recommend disabling all non-essential extensions before starting your capture session.
3. Define Your Talk Track and Click Path Upfront
A clear, pre-planned flow ensures your capture stays focused and consistent. Deviating mid-capture can introduce extra elements, increase maintenance complexity, and—even worse—impact performance. Stick to a predefined script to ensure reliability and repeatability.
4. Capture High-Level Part of your Application First
Start with broad overviews or dashboard pages before diving into deeper workflows. This helps identify any cross-domain issues early and avoids wasting time capturing flows that may ultimately be unworkable.
5. Use the Same Login Credentials Throughout
Different users often have different permissions or access levels, which can result in varying captured requests. Stick with a single login session for the entire capture to maintain consistency and prevent unexpected behavior in playback.
6. Monitor the Extension Icon Counter
Keep an eye on the number that appears in the Clone Environment extension icon during capture. This number indicates requests being queued and captured. Give the extension time to process before moving to the next screen to ensure all items are captured properly.
What the Extension Can’t Capture — and What to Do About It
In some cases, internet security standards prevent the extension from capturing certain web requests—especially across different domains. If your flow spans multiple domains or you're noticing missing requests, consider the following workarounds:
Option 1: Create Separate Demos for Each Domain
Break your demo into smaller segments, each focused on a single domain. Use Reprise’s GUI linking feature to stitch them together into one cohesive experience.
Option 2: Upload HAR Files for Uncaptured Requests
Generate and upload HAR (HTTP Archive) files to manually include missed requests:
-
In Chrome, open DevTools and navigate to the Network tab.
-
Reproduce the flow and then click the download icon to export the HAR file.
-
In Reprise, go to the Configure screen of your draft replay and upload the HAR file via the Web Request panel.
🚨 When to Pull in your SA
Some capture issues are best handled by your technical team. Here’s when to escalate:
1. Demo Doesn’t Load in Preview
Symptoms:
-
The demo redirects to a login screen.
-
The screen is partially rendered or shows an infinite spinner.
-
The page appears blank.
What to Check:
-
Are cookies or session/local storage items missing?
-
Is the user authenticated correctly?
-
Are all key requests present?
2. Missing Data or Data Errors
If you see:
-
Empty fields or missing records
-
Errors related to data dependencies
-
URLs that appear encoded or malformed
…it’s likely the issue lies in incomplete or mismatched request capture. An engineer can resolve this using the replay-backend SDK to simulate the correct behavior.
3. Complex Workflows Involving Dynamic Data
If your demo includes user inputs that influence downstream screens (e.g., form entries, filters, or conditional logic), this dynamic behavior often requires backend support. In these cases, engage an engineer early to ensure smooth playback and data consistency.
By following these best practices and knowing when to escalate, you'll set yourself up for a smoother and more reliable Clone Environment capture experience.