[Interpreter]Nonexistent node in the failureXpath is not handled correctly

Orchestrator: nightly 13/01/2025

While testing the new failureXpath argument in the interpreter configuration file:

Feedback

When the component fails to find the failure message, I couldn’t find any logs related to this issue. This makes it difficult to understand the problem. For example, I tried searching for name instead of hello:

This is not a major issue, but it can be confusing.

Main issue:

If I attempt to specify a node that does not exist (e.g., in my previous example, replacing owl with something else), the orchestrator generates the following errors in the logs:

Here the related testResult