Error codes for alert notifications

Level

Type

Details

Description

Solution

error

AlertPolicyNotConfigured

Alert xxx has no alert policy configured

No alert policy is configured for the alert rule and alerts cannot be merged based on routes. Therefore, Simple Log Service ignores the related alerts.

Modify the alert rule and configure a valid alert policy.

AlertPolicyNotExist

alert policy xxx does not exist

The alert policy that is associated with the alert rule does not exist. Therefore, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple 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, Simple Log Service ignores the on-duty group that uses the calendar.

Create a calendar or configure the on-duty group to specify 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 specified 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 code

Error message

Description

Solution

130101

Message rate limit exceeded (more than 20 per minute).

DingTalk limits each chatbot to a maximum of 20 messages per minute.

• To avoid sending multiple alerts from a single chatbot simultaneously, create multiple chatbots to distribute the load.

• Use features like alert merging to reduce notification noise.

310000

Keywords not found in the content.

The notification content does not contain any of the required keywords.

In your DingTalk chatbot security settings, set one of the custom keywords to Alert.

310000

Signature does not match.

The signature does not match.

Set the security settings for your DingTalk chatbot to custom keywords, and set one of the keywords to Alert.

310000

IP address X.X.X.X not in allowlist

The IP address is not on the allowlist.

Set the security settings for your DingTalk chatbot to custom keywords, and set one of the keywords to Alert.

300001

The token does not exist.

The webhook URL is invalid or the chatbot was deleted.

• Verify that the chatbot's webhook URL is correct.

• Check if the corresponding chatbot has been removed.

40035

Missing parameter access_token

The chatbot's webhook URL is missing the access_token parameter.

Verify that the chatbot's webhook URL is correct.

400102

The chatbot is stopped.

The chatbot is disabled.

• Check the status of the chatbot.

• Use the webhook URL of an active chatbot.

450103

Only group administrators can use @all.

Only the group owner and group administrators can @all members.

In the action policy, set Reminder method to specific members or no reminder.

Error code

Error message

Description

Solution

45009

API frequency limit exceeded.

Enterprise WeChat limits each chatbot to a maximum of 20 messages per minute.

• To avoid sending multiple alerts from a single chatbot simultaneously, create multiple chatbots to distribute the load.

• Use features like alert merging to reduce notification noise.

40058

The Markdown content exceeds the maximum length of 4,096 bytes.

Enterprise WeChat limits the notification content to a maximum of 4,096 bytes.

Adjust the content template to reduce the length of the rendered notification.

93000

Invalid webhook URL.

The webhook URL for the chatbot is incorrect.

Verify that the chatbot's webhook URL is correct.

Error code

Error message

Description

Solution

9499

Too many requests.

Lark limits each chatbot to a maximum of 20 messages per minute.

• To avoid sending multiple alerts from a single chatbot simultaneously, create multiple chatbots to distribute the load.

• Use features like alert merging to reduce notification noise.

11246

Variable. For example: path: message->card->1th block(markdown)->5th md(center); err_msg: unsupported type of html tag; err_type: validation;

This error usually indicates that the notification content is in an invalid format.

Troubleshoot the issue based on the specific error message you receive.

19001

Invalid parameter: The incoming webhook access token is invalid.

The webhook URL for the chatbot is incorrect.

Verify that the chatbot's webhook URL is correct.

19007

The chatbot is not enabled.

The chatbot has been disabled.

• Check the status of the chatbot.

• Use the webhook URL of an active chatbot.

19024

Keywords not found.

The message content does not contain any of the required keywords.

In your Lark chatbot security settings, set one of the custom keywords to Alert.