Common Errors and Solutions During Agent Development
Common Workflow Error Codes and Solutions
Table 1 lists common errors that occur at each node of the workflow, along with their corresponding solutions.
Module Name |
Error Code |
Description |
Solution |
---|---|---|---|
Start node |
101501 |
No value is transferred in the global configuration of the start node. |
An error occurred on the start node. Contact customer service. |
End node |
101531 |
Failed to initialize the end node. |
Check the configuration on the end node. The possible cause is that the verification failed. |
101532 |
Template concatenation failed on the end node. |
Check whether the template placeholder matches the input. Contact customer service. |
|
101533 |
Streaming processing on the end node failed. |
Contact customer service. |
|
LLM node |
101561 |
Failed to initialize the LLM node. |
Check the configuration of the LLM node. The possible cause is that the verification failed. |
Code node |
101591 |
Failed to initialize the code component. |
Check the configuration on the code node. The possible cause is that the verification failed. |
101592 |
Failed to request the security sandbox on the code node. |
Contact customer service. |
|
101593 |
Failed to execute the security sandbox on the code node. |
Check whether the code syntax is correct and whether unreferenced variables are used. |
|
101594 |
Other errors are reported on the security sandbox of the code component. |
Contact customer service. |
|
101595 |
Unknown error occurred during the execution on the code node. |
Contact customer service. |
|
Message node |
101651 |
Failed to initialize the message component. |
Check the configuration on the message node. The possible cause is that the verification failed. |
101652 |
The template information is missing on the message node. |
Configure the prompt template of the message node. |
|
101653 |
The message node template is incorrectly concatenated. |
Check whether the template placeholder matches the input. If the error persists, contact customer service. |
|
101654 |
The message component failed to be executed. |
Contact customer service. |
|
101655 |
The message component fails to be executed asynchronously. |
Contact customer service. |
|
Intent recognition node |
101098 |
Failed to request the intent recognition prompt template. |
Check whether the template placeholder matches the input. |
101097 |
The prompt for the intent recognition component to call the LLM does not comply with the model input specifications. |
Check the format of the prompt, and the role and content of the message. |
|
101096 |
The intent recognition component failed to call the LLM. |
Check whether the format and content of the message and the LLM service are normal. |
|
101095 |
The intent recognition component failed to parse the input or reference in the user query. |
Check the format and content of the user query. |
|
101094 |
Failed to create the intent recognition prompt template. |
Check the built-in template and the format and content of the system prompt. |
|
Questioner node |
101043 |
The number of dialog rounds in a single questioner exceeds the preset upper limit. The dialog status returns to the start node status. |
You can increase the maximum number of dialog rounds. |
101047 |
Failed to initialize the in-depth customization pre-processing and post-processing module. |
Check whether the guardrail configuration meets the requirements. |
|
101048 |
The in-depth customization user reply rewriting (preprocessing) failed. |
You can check the preprocessing guardrail code. |
|
101049 |
Failed to rewrite (post-process) parameter values generated by the in-depth customization model. |
Check the post-processing guardrail code. |
|
101050 |
The default guardrail (time parameter parsing) fails to be executed. |
Check whether the time type that can be processed exceeds the supported range. |
|
102053 |
The prompt template is incorrect. |
Check whether the format of the prompt template is correct. |
|
103004 |
Model inference failed. |
Check whether the model service is running properly. |
|
Plug-ins |
101741 |
Failed to initialize the plug-in engine. |
Check the plug-in component configuration. The possible cause is that an error is reported during verification. |
101742 |
An error occurred when converting the parameter type of the workflow plug-in node. |
Determine the name of the parameter that fails to be converted based on the error message and check whether the parameter type is correct. |
|
101743 |
The input of the workflow plug-in node does not exist in the plug-in definition. |
Check whether the plug-in definition matches the corresponding component definition. |
|
101744 |
The plug-in defines a response, but the actual plug-in execution result is inconsistent with the defined response. |
Check whether the plug-in response definition matches the actual plug-in execution result. |
|
101745 |
An error occurs when the workflow plug-in node is executed. |
If an error occurs during plug-in execution, locate the fault based on the error message. If the message does not contain valid information, the error is not captured. |
|
105001 |
An exception that cannot be captured occurs during plug-in execution. |
Check whether the service is available. |
|
105004 |
Check param error during plug-in definition. |
Determine the error parameter definition based on the error message. |
|
105005 |
The plug-in definition is invalid. |
The data defined by the plug-in is invalid. For example, the field length exceeds the maximum. Check the error message. |
|
105008 |
The plug-in content is incorrect. |
Contact customer service. |
|
105010 |
An authentication error occurs when the plug-in is running. |
You can locate the authentication problem based on the error message and check whether the authentication information transfer and plug-in authentication definition are correct. |
|
105011 |
The response code returned during plug-in running is not 200. |
You can view the actual HTTP return code based on the reported information. |
|
105012 |
The plug-in request times out. |
The plug-in request times out. Check the plug-in service. |
|
105013 |
The result returned by the plug-in is too large. |
Currently, 10 MB is supported. If the size exceeds 10 MB, an error is reported. |
|
105014 |
Plug-in request proxy error. |
Check whether the plug-in service is faulty. |
|
Performing Authentication |
110000 |
Authentication failed. |
Check the authentication configuration. |
110001 |
Get users in domain in IAM failed |
Check whether the user information is correctly configured. |
|
Workflow |
112501 |
Workflow authentication failed. |
Check the authentication configuration. |
112502 |
Some required parameters are missing. |
You can view the missing parameters in the printed logs. |
|
112503 |
The workflow fails to connect to the database. |
Contact customer service. |
|
112504 |
Necessary permissions are missing. |
Viewing the profile of the current user |
|
112513 |
An infinite loop occurs in the workflow. |
Check the workflow canvas. |
|
112514 |
The workflow is referenced and cannot be deleted. |
Check whether the workflow is referenced by the knowledge-based application. |
|
112600 |
Failed to convert the workflow IR. |
Check whether the workflow configuration is correct. |
|
112941 |
Failed to obtain the workflow dialog history. |
Contact customer service. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot