This topic describes the error codes related to alerts.

Configuration errors

Level Type Details Description Solution
error AlertPolicyNotConfigured Alert xxx has no alert policy configured No alert policy is configured for the alert monitoring rule and alerts cannot be merged based on routes. Therefore, Log Service ignores the related alerts. Modify the alert monitoring rule and configure a valid alert policy.
AlertPolicyNotExist alert policy xxx does not exist The alert policy that is associated with the alert monitoring rule does not exist. Therefore, Log Service ignores the related alerts. Create an alert policy with the same name or specify another alert policy.
AlertPolicyInvalid alert policy xxx format is error The format of the alert policy is invalid and related alerts cannot be parsed. Therefore, Log Service ignores the related alerts. Modify the alert policy, or delete the alert policy and create an alert policy with the same name.
GroupPolicyEmpty Group policy of alert policy xxx is empty The route consolidation policy of the alert policy is not configured. Therefore, Log Service ignores the related alerts. Configure the route consolidation policy of the alert policy and make sure that the route consolidation policy is not empty.
ActionPolicyNotExist action policy xxx does not exist The action policy does not exist. Therefore, Log Service does not send alert notifications for the alerts that use the action policy. Create an action policy or specify another action policy.
ActionPolicyInvalid action policy xxx is invalid The format of the action policy is invalid. Therefore, Log Service does not send alert notifications for the alerts that use the action policy. Modify the action policy, or delete the action policy and create an action policy with the same name.
ActionPolicyEmpty Primary(Secondary) policy for action policy xxx is empty The primary and secondary action policies of the action policy are empty. Therefore, Log Service does not send alert notifications for the alerts that use the action policy. Modify the action policy and make sure that the primary and secondary action policies are not empty.
warn AlertPolicyInheritanceLoop alert policy xxx has inheritance loop with yyy An inheritance loop exists. For example, Alert Policy A inherits Alert Policy B and Alert Policy B inherits Alert Policy A.
  • If you associate Alert Policy A, Alert Policy B is executed, and then Alert Policy A is executed.
  • If you associate Alert Policy B, Alert Policy A is executed, and then Alert Policy B is executed.
The inheritance loop is not parsed. 		Modify the alert policy to prevent inheritance loops.
UserNotExist user xxx does not exist The specified user does not exist. Therefore, Log Service does not send alert notifications to the user. Create a user or configure the action policy to specify another user.
UserGroupNotExist group xxx does not exist The specified user group does not exist. Therefore, Log Service does not send alert notifications to the user group. Create a user group or configure the action policy to specify another user group.
UserGroupEmpty group xxx is empty The specified user group does not contain users. Therefore, Log Service does not send alert notifications to the user group. Add users to the user group.
OncallGroupNotExist oncall group xxx does not exist The specified on-duty group does not exist. Therefore, Log Service does not send alert notifications to the on-duty group. Create an on-duty group or configure the action policy to specify another on-duty group.
ContentTemplateNotExist content template xxx does not exist The specified alert template does not exist. Therefore, Log Service ignores the notification methods that use the alert template. Create an alert template or configure the action policy to specify another alert template.
CalendarNotExist calendar xxx does not exist The specified calendar does not exist. Therefore, Log Service ignores the on-duty group that uses the calendar. Create a calendar or configure the on-duty group to use another calendar.
ChannelQuotaNotExist channel quota does not exist The quota for the specified notification method does not exist. Therefore, the number of alert notifications that can be sent by using the notification method is unlimited. Configure a quota for the related notification method.
ChannelQuotaInvalid channel quota format is invalid The quota for the specified notification method is left empty. Therefore, the number of alert notifications that can be sent by using the notification method is unlimited. Change the quota for the notification method and make sure that the quota is not empty.

Error codes for DingTalk notifications

Error code Error message Description Solution
130101 send too fast, exceed 20 times per minute The error message returned because the number of messages sent by the chatbot within 1 minute exceeds 20. A DingTalk chatbot can send a maximum of 20 messages within 1 minute.
  • Create multiple chatbots to send messages. This prevents multiple alert messages from being sent by the same chatbot.
  • Use denoising methods such as merging alerts to denoise alerts.
310000 keywords not in content The error message returned because the notification content does not contain keywords. Set Security Settings of your DingTalk chatbot to Custom Keywords and enter Alert as a keyword.
310000 sign not match The error message returned because the signature does not match the signature that you specify.

Set Security Settings of your DingTalk chatbot to Custom Keywords and enter Alert as a keyword.

310000 ip X.X.X.X not in whitelist The error message returned because the IP address is not in the allowlist. Set Security Settings of your DingTalk chatbot to Custom Keywords and enter Alert as a keyword.
300001 token is not exist The error message returned because the webhook URL of the chatbot does not exist.
  • Check whether the webhook URL of the chatbot is valid.
  • Check whether the chatbot is deleted.
40035 access_token is not specified The error message returned because the access_token parameter is not specified in the webhook URL of the chatbot. Check whether the webhook URL of the chatbot is valid.
400102 bot is stopped The error message returned because the chatbot is disabled.
  • Check the status of the chatbot.
  • Specify the webhook URL of a chatbot that is running as expected.
450103 only group admin can @ All The error message returned because only group owners and group administrators can remind all members by using the at sign (@). In the action policy that is used, set Reminder Method to Specified Member or No Reminder.

Error codes for Enterprise WeChat notifications

Error code Error message Description Solution
45009 api freq out of limit The error message returned because the number of messages sent by the chatbot within 1 minute exceeds 20. An Enterprise WeChat chatbot can send a maximum of 20 messages within 1 minute.
  • Create multiple chatbots to send messages. This prevents multiple alert messages from being sent by the same chatbot.
  • Use denoising methods such as merging alerts to denoise alerts.
40058 markdown.content exceed max length 4096. invalid Request Parameter The error message returned because the length of the alert notification exceeds 4,096 bytes. The maximum length of an alert notification that an Enterprise WeChat chatbot can send is 4,096 bytes. Change the configuration of the alert template to reduce the length of a rendered alert notification.
93000 invalid webhook url The error message returned because the webhook URL of the chatbot is invalid. Check whether the webhook configuration of the chatbot is valid.

Error codes for Lark notifications

Error code Error message Description Solution
9499 too many request The error message returned because the number of messages sent by the chatbot within 1 minute exceeds 20. A Lark chatbot can send a maximum of 20 messages within 1 minute.
  • Create multiple chatbots to send messages. This prevents multiple alert messages from being sent by the same chatbot.
  • Use denoising methods such as merging alerts to denoise alerts.
11246 Variable. Examples: path: message-\u003ecard-\u003e1th block(markdown)-\u003e5th md(center), err_msg: unsupported type of html tag, and err_type: validation. In most cases, an error message returned because the format of the notification content is invalid. Troubleshoot the error based on the error message.
19001 param invalid: incoming webhook access token invalid The error message returned because the webhook URL of the chatbot is invalid. Check whether the webhook URL of the chatbot is valid.
19007 Bot Not Enabled The error message returned because the chatbot is disabled.
  • Check the status of the chatbot.
  • Specify the webhook URL of a chatbot that is running as expected.
19024 Key Words Not Found The error message returned because the notification content does not contain keywords. Set Security Settings of your Lark chatbot to Custom Keywords and enter Alert as a keyword.