> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/record-replay/policy-execution-record-and-replay-using-ui.md).

# Policy execution record and replay using UI

## 1. Record

The recording starts on the press of the ‘Record’ button.

{% hint style="info" %}
Note: It is strongly recommended to initiate recording at the very beginning of the policy execution, otherwise issues may be encountered at the ‘Replay’ stage.
{% endhint %}

<figure><img src="/files/txDA13XWuLFc6kn4nZRo" alt=""><figcaption></figcaption></figure>

### 1.1 Menu

<figure><img src="/files/JueZdDX3QzIBqKfo65ae" alt=""><figcaption></figcaption></figure>

1. “Stop” - ends the recording and downloads the capture file.

<figure><img src="/files/VdvoP0LsV3gqXilrRbPD" alt=""><figcaption></figcaption></figure>

2. Actions - shows/hides the list of recorded steps/events.

<figure><img src="/files/nAIGKpbuN19gnnuKCtH0" alt=""><figcaption></figcaption></figure>

## 2. Replay

Pressing the ‘Run’ button will initiate replay of the previously recorded file.

<figure><img src="/files/asjpYuGjNwihyVMUHXzQ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/NYySSvyHiF0nQgrIcRs6" alt=""><figcaption></figcaption></figure>

### 2.1 Menu

<figure><img src="/files/x4sbs6BOy0U0ftg1EIjq" alt=""><figcaption></figcaption></figure>

1. Fast Forward - quick transition to the next step (skipping the replay of the recorded pause).

<figure><img src="/files/e7vCCoaXkYc5ZQQAMEUh" alt=""><figcaption></figcaption></figure>

2. Stop - ends the replay

<figure><img src="/files/Qd9nGVmPe60RBbvWKlzz" alt=""><figcaption></figcaption></figure>

3. Actions - shows/hides the list of replayed steps/events

<figure><img src="/files/nAoprzJQ8LMHBB21nWII" alt=""><figcaption></figcaption></figure>

### 2.2 Error

<figure><img src="/files/ddv7s1zWfH2MrFUUXFyo" alt=""><figcaption></figcaption></figure>

In the case of an error the following actions are possible

1. Retry - attempts to repeat the errored step/event

<figure><img src="/files/FIpoZC2JwznkAVICHMrv" alt=""><figcaption></figcaption></figure>

2. Skip - skips the errored step/event and execute the next one

<figure><img src="/files/CqTggCSJHQFgH6qzRhBE" alt=""><figcaption></figcaption></figure>

### 2.3 Results

A summary dialogue is shown at the end of the replay. This dialogue contains the information about the tokens and document created during the policy execution, and the extend to which these artifacts are similar to those produced during the original execution (when the ‘records’ file was created).

<figure><img src="/files/y6lJXHGXYBs7sfZRkDJ7" alt=""><figcaption></figcaption></figure>

The ‘details’ page shows detailed breakdown of differences between the corresponding documents or tokens.

<figure><img src="/files/rbmDSR6M2o0KgizxqTGe" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guardianservice.app/technical-information/users/standard-registry-users-schemas-and-policies/policies/record-replay/policy-execution-record-and-replay-using-ui.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.