langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The model is qwen-plus. Dialog contains sensitive information (Server Unavailable Error, Failed to invoke model qwen-plus, status code: 500, message: Input data may contain inappropriate content), and then use this conversation_id to send any message w… #7256

New Issue
Closed
opened 2026-02-21 18:19:40 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:19:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @ouguofeng on GitHub (Dec 17, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.13.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1734492488017
When I use the api to have a conversation that contains sensitive information. The session id can no longer be used

The model I used was qwen-plus

✔️ Expected Behavior

I hope this conversation id has sensitive information that will allow me to continue using it. Dropping this session id will affect my context content

❌ Actual Behavior

/v1/chat-messages
{
"inputs": {},
"conversation_id": "4c990d67-5abd-4421-820f-44bcb30ebe73",
"query": "亚洲有几个发达国家",
"user": "2",
"response_mode": "streaming"
}

Originally created by @ouguofeng on GitHub (Dec 17, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.13.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![1734492488017](https://github.com/user-attachments/assets/ad0913f5-ba7b-43e7-b4b0-f7023fd50d8f) When I use the api to have a conversation that contains sensitive information. The session id can no longer be used The model I used was qwen-plus ### ✔️ Expected Behavior I hope this conversation id has sensitive information that will allow me to continue using it. Dropping this session id will affect my context content ### ❌ Actual Behavior /v1/chat-messages { "inputs": {}, "conversation_id": "4c990d67-5abd-4421-820f-44bcb30ebe73", "query": "亚洲有几个发达国家", "user": "2", "response_mode": "streaming" }
yindo added the 🐞 bug label 2026-02-21 18:19:40 -05:00
yindo closed this issue 2026-02-21 18:19:40 -05:00
yindo commented 2026-02-21 18:19:40 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 17, 2024):

Hello, @ouguofeng! I'm here to help you with any bugs, questions, or contributions you might have. Let's get to the bottom of this together!

The issue you're experiencing seems to be related to the handling of sensitive information within the Dify platform, specifically when using the qwen-plus model. When a session ID is flagged due to sensitive content, it becomes unusable for further interactions. This is likely due to the platform's moderation tools, which are designed to prevent the continuation of conversations that contain inappropriate content.

To address this, you might consider the following approaches:

  1. Review and Adjust Moderation Settings: Check if the moderation settings, such as custom keywords or the use of the OpenAI Moderation API, are too restrictive. Adjusting these settings might help prevent legitimate content from being flagged as sensitive.

  2. Create a New Session: If a session ID is flagged and becomes unusable, you may need to start a new session with a different ID. While this might affect the continuity of the conversation, it ensures compliance with content policies.

  3. Custom Moderation Extensions: Implement custom moderation extensions tailored to your specific needs. This can help in creating more nuanced rules for what constitutes sensitive content, potentially reducing false positives.

Unfortunately, there isn't a direct way to reset or continue a conversation with a flagged session ID without starting a new session, as the platform is designed to enforce strict content policies to ensure safety and compliance.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 17, 2024): <!-- Greeting --> Hello, @ouguofeng! I'm here to help you with any bugs, questions, or contributions you might have. Let's get to the bottom of this together! <!-- Answer --> The issue you're experiencing seems to be related to the handling of sensitive information within the Dify platform, specifically when using the qwen-plus model. When a session ID is flagged due to sensitive content, it becomes unusable for further interactions. This is likely due to the platform's moderation tools, which are designed to prevent the continuation of conversations that contain inappropriate content. To address this, you might consider the following approaches: 1. **Review and Adjust Moderation Settings**: Check if the moderation settings, such as custom keywords or the use of the OpenAI Moderation API, are too restrictive. Adjusting these settings might help prevent legitimate content from being flagged as sensitive. 2. **Create a New Session**: If a session ID is flagged and becomes unusable, you may need to start a new session with a different ID. While this might affect the continuity of the conversation, it ensures compliance with content policies. 3. **Custom Moderation Extensions**: Implement custom moderation extensions tailored to your specific needs. This can help in creating more nuanced rules for what constitutes sensitive content, potentially reducing false positives. Unfortunately, there isn't a direct way to reset or continue a conversation with a flagged session ID without starting a new session, as the platform is designed to enforce strict content policies to ensure safety and compliance. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/7228f1df-1f16-4efb-8713-8369e9de76b2?feedback_type=other)</sup>
yindo commented 2026-02-21 18:19:41 -05:00
Author
Owner
Copy Link
Copy Source

@ouguofeng commented on GitHub (Dec 17, 2024):

Well, thank you very much

@ouguofeng commented on GitHub (Dec 17, 2024): Well, thank you very much
yindo commented 2026-02-21 18:19:41 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 18, 2024):

If you turn on the llm memory switch, then it won't be removed until it moves to the start of the memory. In this case, you can not alter the memory in the web UI.

@crazywoola commented on GitHub (Dec 18, 2024): If you turn on the llm memory switch, then it won't be removed until it moves to the start of the memory. In this case, you can not alter the memory in the web UI.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7256
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?