# Understanding the execution report
Once you execute one or more journeys, clicking on the resulting execution job will take you to its execution report. In this section, we look at different parts of this report and how to make the most out of it.
The execution report has four main sections:
- Goal name and job submit date;
- List of journeys;
- Overall test execution summary, including the current status of the execution, and any other attributes related to the execution (e.g., tags, custom starting variables or headers, users who launched/stopped the journey, etc.);
- List of failed tests (if any are present).
This view can be accessed even when the execution is running, and will update live as the execution progresses. Once the execution finishes the timer stops, and the details about tests that failed are presented.
# Journey execution report
Clicking on one of the journeys will open the journey execution report showing the associated checkpoints and test steps. When a test step is clicked, the screenshot taken by Virtuoso after performing the step will be displayed:
Clicking on a failed step will have a root cause analysis tab, which will help you get to the bottom of why the test failed.
# Journey execution times explained
We display the duration of the journey execution in each item from the list of executed journeys or after opening the report for a specific journey. This duration refers only to the time the journey was actively running test steps. To find out how long Virtuoso took to initiate the journey execution, hover over this duration. The tooltip reveals:
- Throttled: the throttling duration due to max parallelism;
- Queued: the time spent in the queue awaiting resources or to ensure fair usage across different organizations;
- Duration: the time the journey was actively running test steps;
- Total duration: the sum of the previous three values.
