Performance issues

• Why is normal text identified as abusive content? Why is abusive content not detected?
• Why is normal text identified as pornographic content? Why is pornographic content not detected?
• Why are keywords such as QR codes not detected during text moderation?
• Why are pornographic images not detected during image moderation?
• Why are whitelisted keywords still blocked?
• Why are images with national flags and emblems not blocked?
• How do I handle medical images of human bodies that are identified as pornographic?
• Why are Content Moderation detection results unstable, or why does content remain blocked after whitelisting or manual correction?

Why is normal text identified as abusive content? Why is abusive content not detected?

Abusive text is classified into three severity categories: severe abuse, minor abuse, and profanity. Adjust the machine-assisted moderation rules for text in the console to fit your scenario. If specific text is not detected or is misidentified, add it to a custom similar text library or keyword library, and then use an ignore list or a review list to resolve the issue.

For more information, see Customize machine-assisted moderation rules and Manage custom text libraries.

Why is normal text identified as pornographic content? Why is pornographic content not detected?

Pornographic text is classified into three severity categories: severe pornography, vulgar content, and sexual knowledge. Adjust the machine-assisted moderation rules for text in the console to fit your scenario. If specific text is not detected or is misidentified, add it to a custom similar text library or keyword library, and then use an ignore list or a whitelist to resolve the issue.

For more information, see Customize machine-assisted moderation rules and Manage custom text libraries.

Why are keywords such as QR codes not detected during text moderation?

The text advertisement detection scenario detects content such as phone numbers, WeChat, QQ, URLs, and ad slogans. Adjust the machine-assisted moderation rules for text in the console to suit your scenario. If specific text is not detected, add it to a custom similar text library or keyword library, and then use a blacklist or a review list to resolve the issue.

For more information, see Customize machine-assisted moderation rules and Manage custom text libraries.

Why are pornographic images not detected during image moderation?

The pornography detection scenario classifies images into three categories based on explicitness: explicit pornography, vulgarity, and suggestive exposure. Adjust the machine-assisted moderation rules for images in the console. If a specific image is not detected, add it to a custom image library, select the pornography detection scenario, and then use a blacklist or a review list to resolve the issue.

For more information, see Customize machine-assisted moderation rules and Manage custom text libraries.

Why are whitelisted keywords still blocked?

A custom text library may not take effect for the following reasons:

• It takes about 15 minutes for added keywords to take effect. Try again later.
• Confirm how the text library is used:
  • For content with five or fewer characters, use the Keywords option. Set the matching method to Transform then Match.
  • For content with more than five characters, use the Similar Text option.
• Make sure that the text library is applied to the corresponding business scenario (Biztype).

For more information, see Manage custom text libraries.

Why are images with national flags and emblems not blocked?

AI Guardrails provides several detection scenarios, such as pornography detection, terrorist content, text and image violations, and undesirable scenes. To block content such as national flags and emblems, use the terrorist content detection scenario. This scenario detects several types of content, including people, symbols, weapons, events, religion, official business, and certificates. Adjust the machine-assisted moderation rules for images in the console. In the Symbol Detection category, select the national flag and emblem. You must also specify the terrorist content detection scenario in the AI Guardrails API.

For more information, see Customize machine-assisted moderation rules and Synchronous detection.

How do I handle medical images of human bodies that are identified as pornographic?

The pornography detection feature of AI Guardrails may incorrectly classify medical images as pornographic content. If an image is misclassified, use its data ID (dataId) to perform a manual review. The dataId is returned by the synchronous image detection API and the manual image review API.

For more information, see the synchronous image detection API or the manual image review API.

Why are Content Moderation detection results unstable, or why does content remain blocked after whitelisting or manual correction?

Detection results may appear inconsistent or may not respond to whitelist rules and manual corrections due to several factors. The following describes the three most common scenarios.

Scenario 1: Whitelist or manual correction not taking effect

If you have configured a whitelist entry or submitted a manual correction, but the content continues to be blocked, possible causes include:

• Data synchronization delay: Whitelist rules and manual corrections typically take up to 15 minutes to propagate. Confirm your configuration is correct and wait 15 minutes, then retest.

• Backend configuration anomaly: If the content is still blocked after 15 minutes, submit a support ticket and include the RequestID of the affected request so the backend team can investigate.

You can also upgrade to Content Moderation Enterprise Edition, which supports custom detection rules for more precise and controllable enforcement.

Scenario 2: Inconsistent detection results for the same image

The same image may receive different detection results on separate calls. This can be caused by:

• Dynamic adjustment of backend detection policies.

• AI model updates or optimization.

Recommended action: Call the detection API again with the same image to verify the latest result. If the inconsistency persists, include the latest RequestID in your feedback ticket so the backend team can investigate.

Scenario 3: Specific RequestID shows missed detections or false positives

If content that should be blocked passes through (missed detection), or if valid content is incorrectly flagged—for example, as political content, pornography, or drug-related content (false positive)—possible causes include:

• Special detection policies active during sensitive time periods.

• AI model recognition bias.

• Backend configuration issues.

Recommended action: Retest the content to confirm whether the issue is reproducible. If the issue persists, include the latest RequestID in your feedback ticket. The backend team will perform policy adjustment or model fine-tuning as needed.