<aside> 💡 The HAR of all steps can be found under the incident screenshot to help your developers understand where the incidents came from.

</aside>

How to view the incident screenshot ?

The best way to determine the anomaly is to check the screenshot taken at the time of the error, which is available by clicking on the red area above the scenario and selecting "Incident Details":

When Quanta probes detect an incident on your web scenario, they attempt to record a screenshot of the returned page to make it easier for you to diagnose.

You can view this screenshot by clicking on the graph in the red area and selecting the "view screenshot" option.

A window will then open showing the page that was returned during the incident.

Why don't I have a screenshot in the details of one of my incidents?

Types of errors

Expected string / item not found

At each stage of the scenario, it is possible to set a character string expected on the page, this allows to check that it is indeed the expected page that is opened by the scenario.

The "Expected string not found" error occurs when the parameterised string is not found on the page.

Some possible reasons:

• The page has been modified and the string being checked no longer exists on it, in which case the expected string must be modified to match an element on the page.
• The page no longer exists and the scenario has been redirected to a different page (e.g. a product that no longer exists). In this case, the scenario must be updated so that it calls an existing page, and the expected string must be updated so that it corresponds to an element on the new page
• More rarely, the page may not have fully loaded.

User journey timeout

This means that the user journey took longer than the time allowed. A scenario that passes every 3 minutes has a maximum of 3 minutes to complete the entire journey.

So there is not necessarily a mistake in the actions, just not enough time.