Skip to main content
Step Replays are the fastest way to reproduce, debug, and share UI failures with full context. This guide walks through capture, playback, and export workflows, plus tips for getting the most signal from every replay.

​
What you need

  • A project in Samelogic
  • The Chrome Extension installed
  • At least one captured element in your Element Library

​
Create a replay

  1. Start a new capture session in the Chrome Extension.
  2. Perform the interaction you want to record.
  3. Save the session to your project.
  4. Open the replay from the project activity feed or element detail page.
Use the playback controls and timeline to locate the exact moment an issue occurs.
  • Timeline: scrub to a timestamp or click an event chip.
  • Step list: jump to key events (clicks, scrolls, mutations).
  • Playback speed: slow down for precision, speed up for scanning.

​
Inspect context

Step Replays are valuable because they preserve the environment and evidence around each step.
  • Console logs: filter by severity to find errors quickly.
  • Network: review failed requests and response timing.
  • DOM snapshot: see the element state at each step.
  • Selectors: confirm the selector used during playback.

​
Share and export

When you’ve found the issue, share the replay with the right level of detail.

​
Share internally

  • Copy the replay link and attach it to a ticket or Slack thread.
  • Add notes and tags to flag key moments.

​
Export to tools

  • Jira: include reproduction steps and environment metadata.
  • Linear: send a concise issue summary with timestamps.
  • Playwright: generate a test scaffold based on the replay steps.

​
Run a replay in CI (GitHub Actions)

Use CI when you want PR-native evidence (check status, logs, and comment) tied to a replay.
  1. Open a replay and go to its CI Workspace.
  2. Confirm your project’s GitHub CI mapping is configured in Project Settings → GitHub CI.
  3. Pick a run profile (smoke, regression, or auth).
  4. Click Run in CI.
  5. If multiple pull requests are detected, select the correct PR candidate.
  6. Watch status updates in the run history and open links to CI logs or PR checks.

​
Optional: Download a CI artifact bundle

Use CI Bundle if you want a portable package of replay evidence. The bundle includes:
  • Replay Playwright spec scaffold
  • Replay metadata and step metadata
  • Comments log and step log
  • Screenshot manifest and available screenshot files
  • Optional rrweb events export
  • PR comment draft markdown

​
Best practices

  • Capture on the most representative environment (prod, staging, or a stable test env).
  • Use clear names for replays so they’re easy to search later.
  • Add tags for features, teams, or release versions.
  • Keep replay length focused (shorter clips are easier to scan).

​
Troubleshooting

  • If the replay is missing frames, check for cross-origin content or strict CSP rules.
  • If playback is slow, reduce the recording length or replay at 1x.
  • If exports look incomplete, verify console/network capture is enabled.