This section describes only module-specific error codes. For details about universal error codes, please refer to Universal Error Codes.
Message
Route switching failed.
Description
Route switching failed.
Possible causes
The input parameters do not meet requirements, or the route switching is abnormal.
Solution
Check whether the input parameters meet the requirements of InteractiveLivenessConfig. Try again after a period of time and perform related logic judgment.
Message
Detection algorithm initialization.
Description
The detection algorithm is initialized, indicating that the API is successfully called (although no data is input for processing). Stay on the current screen. There is no need to jump to another screen.
Message
Detection timeout.
Description
The detection times out. As a result, the failure screen is displayed. If you have configured your own failure screen or back route redirection, you are advised to perform the detection again.
Possible causes
During the detection, related actions are not completed as prompted for a long time. As a result, the detection times out.
Solution
Perform related actions as prompted.
Message
Action mutual exclusion error.
Description
Actions are incorrect. As a result, the failure screen is displayed. If you have configured your own failure screen or back route redirection, you are advised to perform the detection again.
Possible causes
During the detection, related actions are not completed as prompted. As a result, the detection fails.
Solution
Perform related actions as prompted.
Message
Continuity Check Failure.
Description
The continuity check fails. As a result, the failure screen is displayed. If you have configured your own failure screen or back route redirection, you are advised to perform the detection again.
Possible causes
During check of multiple actions, related actions are not completed as prompted. As a result, the continuity check fails.
Solution
Perform related actions as prompted.
Message
The test is not complete.
Description
The detection is incomplete. If you have configured your own failure screen or back route redirection, you are advised to perform the detection again.
Possible causes
The user exits the detection before the detection is complete.
Solution
Perform related actions as prompted.