Error Codes
If an error code starting with APIGW is returned after you call an API, rectify the fault by referring to the instructions provided in API Gateway Error Codes.
Status Code |
Error Codes |
Error Message |
Description |
Solution |
|---|---|---|---|---|
400 |
SecMaster.11061001 |
alert process status error. |
-- |
-- |
400 |
SecMaster.11061002 |
alert rule count out of range. |
-- |
-- |
400 |
SecMaster.11061003 |
alert rule schedule out of range. |
-- |
-- |
400 |
SecMaster.11061004 |
alert rule name already exist. |
-- |
-- |
400 |
SecMaster.20010001 |
Invalid workspace ID. |
-- |
-- |
400 |
SecMaster.20030001 |
Invalid parameters. |
-- |
-- |
400 |
SecMaster.20030002 |
Invalid project ID. |
-- |
-- |
400 |
SecMaster.20030003 |
Invalid name. |
-- |
-- |
400 |
SecMaster.20030004 |
Failed to create the data object. |
-- |
-- |
400 |
SecMaster.20030005 |
Failed to obtain the data object. |
-- |
-- |
400 |
SecMaster.20030009 |
Invalid sorting field. |
-- |
-- |
400 |
SecMaster.20030010 |
Invalid sorting. |
-- |
-- |
400 |
SecMaster.20030011 |
Data object update error. |
-- |
-- |
400 |
SecMaster.20030012 |
Data object deletion error. |
-- |
-- |
400 |
SecMaster.20030013 |
Data object search error. |
-- |
-- |
400 |
SecMaster.20030022 |
Failed to find one dataclass. |
-- |
-- |
400 |
SecMaster.20030025 |
Failed to valid data object. |
-- |
-- |
400 |
SecMaster.20039999 |
Unknown errors |
-- |
-- |
400 |
SecMaster.20040000 |
Unknown Error. |
-- |
-- |
400 |
SecMaster.20040402 |
Failed to query the data class. |
-- |
-- |
400 |
SecMaster.20040516 |
The number of fields exceeds the maximum. |
-- |
-- |
400 |
SecMaster.20041001 |
Invalid workspace ID. |
-- |
-- |
400 |
SecMaster.20041002 |
Invalid parameters. |
-- |
-- |
400 |
SecMaster.20041003 |
Invalid project ID. |
-- |
-- |
400 |
SecMaster.20041031 |
Fail to get data object. |
-- |
-- |
400 |
SecMaster.20041033 |
No associated data object is selected. |
-- |
-- |
400 |
SecMaster.20041504 |
Failed to create the incident. |
-- |
-- |
400 |
SecMaster.20041507 |
Failed to update the incident. |
-- |
-- |
400 |
SecMaster.20041508 |
Failed to delete the incident. |
-- |
-- |
400 |
SecMaster.20041509 |
The number of incidents created per day exceeds the upper limit. |
-- |
-- |
400 |
SecMaster.20041804 |
Incorrect content included in the request for converting an alert to an incident. |
-- |
-- |
400 |
SecMaster.20041805 |
Failed to create the alert. |
-- |
-- |
400 |
SecMaster.20041808 |
Failed to update alert. |
-- |
-- |
400 |
SecMaster.20041809 |
Failed to delete the alert. |
-- |
-- |
400 |
SecMaster.20041810 |
The number of alerts created per day exceeds the upper limit. |
-- |
-- |
400 |
SecMaster.20041811 |
The number of incidents transferred by alerts per day exceeds the upper limit. |
-- |
-- |
400 |
SecMaster.20041903 |
Failed to find dataclass. |
-- |
-- |
400 |
SecMaster.20041904 |
The indicator is not exist. |
-- |
-- |
400 |
SecMaster.20041905 |
Failed to create indicator. |
-- |
-- |
400 |
SecMaster.20041906 |
Failed to update indicator. |
-- |
-- |
400 |
SecMaster.20041907 |
Failed to delete indicator. |
-- |
-- |
400 |
SecMaster.20042501 |
The number of indicators created per day exceeds the upper limit. |
-- |
-- |
400 |
SecMaster.20048001 |
The playbook cannot be deleted because it has a running instance or an activated version. |
-- |
-- |
400 |
SecMaster.20048002 |
The playbook cannot be enabled because it does not have an activated version. |
-- |
-- |
400 |
SecMaster.20048003 |
The playbook cannot be reviewed because it is in an incorrect state. |
-- |
-- |
400 |
SecMaster.20048004 |
The resource does not exist. |
-- |
-- |
400 |
SecMaster.20048005 |
The draft cannot be activated before it passes the review. |
-- |
-- |
400 |
SecMaster.20048006 |
Incorrect playbook ID. |
-- |
-- |
400 |
SecMaster.20048007 |
Incorrect playbook version ID. |
-- |
-- |
400 |
SecMaster.20048008 |
Incorrect playbook action ID. |
-- |
-- |
400 |
SecMaster.20048009 |
Incorrect playbook rule ID. |
-- |
-- |
400 |
SecMaster.20048013 |
The playbook is being enabled. You cannot deactivate the version. |
-- |
-- |
400 |
SecMaster.20048014 |
The playbook has been released and cannot be edited. |
-- |
-- |
400 |
SecMaster.20048015 |
The playbook name must be unique. |
-- |
-- |
400 |
SecMaster.20048016 |
Incorrect time range of the scheduled task. |
-- |
-- |
400 |
SecMaster.20048017 |
Incorrect Corn expression of the scheduled task. |
-- |
-- |
400 |
SecMaster.20048018 |
The number of versions has reached the upper limit. |
-- |
-- |
400 |
SecMaster.20048019 |
A new version cannot be created because there is a version being reviewed. |
-- |
-- |
400 |
SecMaster.20048020 |
Incorrect data object ID. |
-- |
-- |
400 |
SecMaster.20048021 |
Invalid playbook search text. |
-- |
-- |
400 |
SecMaster.20048022 |
The end time must be later than the start time. |
-- |
-- |
400 |
SecMaster.20048023 |
Failed to register schedule job of playbook. |
-- |
-- |
400 |
SecMaster.20048024 |
Failed to disable schedule job of playbook. |
-- |
-- |
400 |
SecMaster.20048025 |
End time of the schedule playbook must be larger than start time. |
-- |
-- |
400 |
SecMaster.20048026 |
End time of the schedule playbook is invalid. |
-- |
-- |
400 |
SecMaster.20048027 |
The data class id of playbook is empty. |
-- |
-- |
400 |
SecMaster.20048028 |
The matching process of playbook is not enabled. You cannot submit the version |
-- |
-- |
400 |
SecMaster.20048029 |
Failed to convert data of playbook |
-- |
-- |
400 |
SecMaster.20048030 |
The number of playbooks exceeds the limit. |
-- |
-- |
400 |
SecMaster.20048031 |
The number of matching process exceeds the limit. |
-- |
-- |
400 |
SecMaster.20048032 |
The scheduled interval of playbook is invalid. |
-- |
-- |
400 |
SecMaster.20048033 |
The matching process of playbook can not be empty. |
-- |
-- |
400 |
SecMaster.20048034 |
The dataclass of matching process is inconsistent with the dataclass of playbook. |
-- |
-- |
400 |
SecMaster.20048035 |
The built-in playbook cannot be modified. |
-- |
-- |
400 |
SecMaster.20048036 |
The built-in playbook cannot be deleted. |
-- |
-- |
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
