@AliW16577900This error usually happens when the SOAP request is missing or has a wrong security header. The system expects a security token like UsernameToken, Signature, or Timestamp in the SOAP header, but it’s not found or is in the wrong format. Because of that, it fails to authenticate the request and throws the NOT_FOUND_ERR. To fix this, check if the request includes all required WS-Security headers. Make sure the headers are correctly placed inside the SOAP envelope and all IDs or references are valid. Also, verify that the request format matches what the service expects. If using tools like SoapUI, compare with a working request. Enable debug logs if more details are needed. ​​​​​​​