# 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](https://1776828725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MTk4m0D_HMejz7b-sEi%2Fuploads%2F0dVXLHmzO9NKR2DSFOqP%2FFlightRecording10.gif?alt=media\&token=cb3ac08e-b17c-4c41-bac3-5c4ba44f6bcf)

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

![](https://1776828725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MTk4m0D_HMejz7b-sEi%2Fuploads%2FxLqwLkaWfpU1sxE1TXtD%2FFlightRecording2.png?alt=media\&token=aea0d9b2-88e2-4e7c-b137-a2f3c6fb6b91)