In Azure AD B2C custom policy, In a ValidationTechnicalProfile, while calling an external REST API, if the REST API returns HTTP error codes like 404 not found, or 401 unauthorized, the "ContinueOnError" attribute does not take effect. Instead the user journey ends abruptly throwing an error "Unable to validate the information provided" to the user interface in case of a self asserted technical profile. However the ContinueOnError attribute works as expected when the REST API returns error codes such as 400 Bad Request.
<ValidationTechnicalProfiles>
<ValidationTechnicalProfile ReferenceId="REST-API-PostUser" ContinueOnError="true" />
Why is the above not working for certain codes like 404 or 401? Is there any other ways in which we can handles these codes accordingly within the user journey?