dify V1.13.3 query for chat history RAG returned no metadata.

[aeefghhcyb]

Self Checks

• I have read the Contributing Guide and Language Policy.
• 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, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

v1.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

In dify's workflow, using the Rag feature and then calling the chat history query API, the returned chat data does not contain the metadata content of the Rag document.

✔️ Expected Behavior

Our RAG file has a lot of important metadata that needs to be displayed, but it's not showing up when viewing the history.

❌ Actual Behavior

Our RAG file has a lot of important metadata that needs to be displayed, but it's not showing up when viewing the history.

[dosubot]

This appears to be a known issue in the v1.13.x series. The retriever_resources field in chat history API responses should include document metadata, but several bugs in this version range can cause it to be missing.

What's happening: RAG document metadata is stored in Message.message_metadata as JSON and is supposed to be returned via the retriever_resources array in API responses [1]. However, there's a reported issue where this field comes back empty despite retrieval working correctly [2]. This was addressed in subsequent fixes related to citation metadata preservation [3].

Recommended fix: Upgrade to the latest Dify release. PR #33778 significantly expanded the metadata fields preserved in API responses — adding dataset_id, dataset_name, document_id, data_source_type, page, title, and more [4]. Additionally, a fix for citation alias serialization (model_dump(by_alias=True)) resolved missing citations in Advanced Chat mode [5].

If you can't upgrade immediately, you can try:

1. Verify that citation/attribution features are enabled in your app settings
2. Check the raw message_metadata field in your database to confirm the metadata is being stored (the issue may be in serialization, not retrieval)
3. Review your workflow logs to confirm knowledge retrieval is completing successfully

Written by @dosu, approved by crazywoola

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[crazywoola]

Hi @aeefghhcyb, thanks for opening this issue.

Why this is being closed

This report does not yet meet the required issue standard for langgenius/dify.

• Describe the feature use case and expected value.

Relevant guidelines

• Bug report template: https://github.com/langgenius/dify/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml
• Code of Conduct / Language Policy: https://github.com/langgenius/dify/blob/main/.github/CODE_OF_CONDUCT.md
• Contributing guide: https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md

Next steps

Please open a new issue in English and include all required details from the bug template/contributing guide.

Thanks for understanding and for your contribution.