# Flight Recorder

When an exception occurs the first thing developer needs to do is to diagnose and reproduce the erroneous scenario.  Such reproduction is time-consuming and often even impossible due to the specificity of the client’s environment. \
With RevDeBug you can cut this step completely! \
Simply go to Flight Recorder and replay the recorded code execution of exception with variable values just like in regular debugging.<br>

![Flight recorded exception](/files/gXAujPSk3YOZkN8xW0LJ)

You can search for values ​​and variable names recorded on the server side - even from production.

![](/files/Vd12MprrXAYOYlaiiZPb)


---

# Agent Instructions: 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:

```
GET https://revdebug.gitbook.io/revdebug/revdebug-features/flight-recorder.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.