if there is any component-level exception and the errorMesaage is not actively mapped in Default mapping, the warning will be shown
does not apply to different levels of exceptions (e.g. failed connection, no response) - OK
1 RCPTT test keeps failing in custom test - checkHttpConnection.test. This is not directly relevant to the cope of this issue, but should probably be checked. It also fails in master custom RCPTT, will not consider this a blocker for the issue.
When the API root URL contains a leading space, the graph executes successfully, but no calls are made.
There are two main issues:
How to handle the API root URL when it contains a leading space.
Why the graph did not fail when an exception occurred during the call.
The problem was that I had defined a default mapping. It might be a good idea that if an error mapping is not mapped, the component should fail.