mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
tongyi plugin: Output data may contain inappropriate content #616
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ihadu on GitHub (Sep 4, 2025).
Self Checks
Dify version
1.7.0
Plugin version
0.0.45
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Error log
No response
@dosubot[bot] commented on GitHub (Sep 4, 2025):
Hi @ihadu! I'm Dosu and I’m helping the dify-official-plugins team.
The "Output data may contain inappropriate content" error is triggered by Dify's core content moderation system, which uses the OpenAI moderation model to check outputs for policy violations. If the output is flagged, Dify returns a preset response and a 400 error code instead of the original content. This moderation is enforced centrally in Dify, not in the Tongyi plugin itself, so plugin-specific configuration won't affect this behavior. You can review or adjust moderation settings in your Dify configuration if you want to fine-tune or disable output moderation for your self-hosted deployment. Recent updates to the Tongyi plugin (v0.0.45) improved error handling for these cases, but the moderation logic remains in Dify core, not the plugin itself. For more details on how moderation is implemented, see the Dify moderation code and recent plugin error handling changes.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@ihadu commented on GitHub (Sep 4, 2025):
If possible, it would be great to support a
skip_moderationparameter.qwen-longalready allows skipping both input and output content inspection by adding the following header:@dosubot[bot] commented on GitHub (Sep 20, 2025):
Hi, @ihadu. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!