# Recorded actions and user steps Canonical: https://fairleadhq.com/docs/recorder/steps-and-events/ Updated: 2026-10-10 Publication state: published Product version: Recorder source f6ed5b96 Agent summary: Inspect individual recorded actions and generate user steps. Both generation modes send the report to the project Data Plane; action associations do not prove causation. ## Prerequisites - A recorded session open in the viewer ## Inputs - Retained actions and related evidence ## Outputs - An interpreted action sequence ## Limitations - Generated steps need review; action associations do not prove causation ## Permissions - Access to the session ## Privacy - Review the report before generating user steps; both modes send it to the project Data Plane Read actions and inspect the evidence around them. Use **Recorded Actions** to understand a retained sequence, then **Event Log** to inspect the underlying action detail. ## Read the steps [Open the viewer](https://fairleadhq.com/docs/recorder/session-viewer/), select **Actions**, then **Recorded Actions**. Begin with the starting page, then compare the narrated actions with the check you performed. Recorded Actions lists individual recorded actions in sequence. It is not a complete transcript of every physical input. The starting-page row provides context for the retained interval. ## Inspect an action Select an action to inspect its target, label, selectors, and available related evidence. Accessible names and roles help identify controls; selector alternatives help developers review generated tests. A label can be missing or ambiguous. Compare the target with the application before treating a generated locator as reliable. Redacted or unavailable values do not mean a field was empty. ## Filter, rename, or remove an action Search for a target or use **Key actions only**, **Has evidence**, or **Needs attention** to focus the list. **Group by page** helps follow page transitions. These filters change the view, not the report or downloads. Open an action and use **Rename** to make its narrative clearer. This does not change the captured input or generated test commands. **Delete** asks for permanent confirmation and removes the action from the report and exports; it cannot be undone. Actions linked to requests or logs cannot be deleted. Preserve the original evidence before removing anything you may need. ## Read the event log Use **Event Log** when you need individual recorded events and timing. Compare it with Recorded Actions to inspect navigation or state changes around an interaction. Review available URL changes and DOM/state changes in action details. These are diagnostic observations, not a complete DOM replay or a screenshot of every state. ## Generate user steps To generate reproduction instructions, you need to be signed in with a configured project Data Plane and **Save recorded data in Data Plane** enabled. This feature is separate from the locally displayed Recorded Actions. 1. Review the report and its [data destination](https://fairleadhq.com/docs/recorder/privacy/). 2. Open **Description**. For a current local recording, the same editor is used whether or not an issue is selected. 3. Open **Add** and choose **Steps to reproduce** for deterministic generation or **Steps written by AI**. 4. Review the inserted text against the evidence, correct it, and check that your edits saved. Use **Undo** to reverse an insertion. Both modes contact the project's Data Plane. **Steps to reproduce** sends a reduced report with actions and metadata, retaining request URLs, status, timing, and identifiers but removing network headers, bodies, cookies, stream messages, logs, performance events, attachments, and annotations. **Steps written by AI** sends the full report. Review authored metadata as well as captured values before either operation. For a local alternative, choose **Add → Recorded actions**. This inserts the starting page and action sequence without contacting a service. **Add → Notes** inserts saved observations. These insertions use the full retained sequence regardless of Actions filters and are available without an account. The description editor and its insertion menu are not available in stored-session review. ## Follow related evidence Open related requests or console entries from an action to investigate the result. A timing-based association suggests where to look; it does not prove that the action caused the request or error. Add a [note](https://fairleadhq.com/docs/recorder/notes/) to an action to state what was expected and what you observed. ## Explain gaps The [retained-timeline limit](https://fairleadhq.com/docs/recorder/developers/capture-support/#recording-retention) determines which actions remain at Stop. Earlier actions may be absent, and frame or component boundaries can limit target details. Describe missing steps in your execution record. Use [navigation and frame guidance](https://fairleadhq.com/docs/recorder/navigation-and-frames/) when the gap occurs across pages or embedded content.