Skip to main content
Use this page to resolve the most common issues teams encounter with captures, selectors, and replays.

​
Extension issues

Capture highlight is missing
  • Refresh the page and retry capture.
  • Check for cross-origin iframes that block the overlay.
Selectors look unstable
  • Prefer data-test attributes when available.
  • Capture from a stable environment to reduce dynamic DOM changes.
Iframe re-open fails with a reason code
  • frame_mismatch: The saved iframe chain no longer matches this page layout. Refresh and retry; if the app layout changed, re-capture the element.
  • selector_miss: The target selector did not resolve in the routed frame or fallback scan. Re-capture the element from the current UI state.
  • permission_blocked: The extension cannot access one or more iframe origins. Grant runtime iframe origin access when prompted, then retry without restarting.

​
Element Library issues

Search is slow or noisy
  • Narrow filters by project and tags.
  • Sort by stability score to triage risky elements first.
Element context looks outdated
  • Re-capture the element to refresh metadata.

​
Step Replay issues

Missing frames or gaps
  • Cross-origin frames and strict CSP can reduce recording detail.
  • Shorter recordings are more reliable.
Playback is slow
  • Reduce the replay length or open at 1x speed.

​
FAQ

Can I export replays to my issue tracker? Yes. Replays can be shared as links or exported to common tools. How long are replays retained? Retention varies by plan. See Limits & Quotas for details.