If the first round of conversation includes attachments, and the second round also includes attachments, an error will occur. The large model I used is Qwen 3.8-27B-FP8.
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 20h 50m
- Merged PRs (30d)
- 586
Description
### Self Checks
- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [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, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.
### Dify version
1.16.1
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
If the first round of conversation includes attachments, and the second round also includes attachments, an error will occur. The large model I used is Qwen 3.8-27B-FP8.
### ✔️ Expected Behavior
Normally, remember the attachments of the first round while analyzing the files of the second round.
### ❌ Actual Behavior
report an error:{
"text": "处理失败!",
"error_message": "req_id: 28798a2a82 PluginInvokeError: {\"args\":{\"description\":\"[models] Error: API request failed with status code 400: {\\\"error\\\":{\\\"message\\\":\\\"Unsupported chat content part type: 'file'. Supported types: audio_embeds, audio_url, image_embeds, image_pil, image_url, input_audio, input_image, input_text, output_text, prompt_embeds, refusal, text, thinking, tool_reference, video_url. (parameter=type, value=file)\\\",\\\"type\\\":\\\"BadRequestError\\\",\\\"param\\\":\\\"type\\\",\\\"code\\\":400}}\"},\"error_type\":\"InvokeError\",\"message\":\"[models] Error: API request failed with status code 400: {\\\"error\\\":{\\\"message\\\":\\\"Unsupported chat content part type: 'file'. Supported types: audio_embeds, audio_url, image_embeds, image_pil, image_url, input_audio, input_image, input_text, output_text, prompt_embeds, refusal, text, thinking, tool_reference, video_url. (parameter=type, value=file)\\\",\\\"type\\\":\\\"BadRequestError\\\",\\\"param\\\":\\\"type\\\",\\\"code\\\":400}}\"}",
"error_type": "PluginInvokeError"
}
Contributor guide
Research direction
No file or test is named. First reproduce the failure on Dify 1.16.1 with a self-hosted Docker setup, Qwen 3.8-27B-FP8, and attachments in two consecutive conversation rounds; then trace the attachment handling and model request path shown by the PluginInvokeError. Done means the second round succeeds while retaining and analyzing the first round’s attachments.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100