langgenius/dify

call to the /datasets/dataset_id/documents/metadata interface was successful, But the metadata displayed on the interface is empty

Open

#26521 opened on Oct 1, 2025

View on GitHub
 (5 comments) (2 reactions) (0 assignees)TypeScript (141,412 stars) (22,210 forks)batch import
good first issue🐞 bug

Description

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

1.91.

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

call to the /datasets/dataset_id/documents/metadata interface was successful, But the metadata displayed on the interface is empty

✔️ Expected Behavior

The API description does not provide any information about the operation metadata The call to the /datasets/dataset_id/documents/metadata interface was successful, But the metadata displayed on the interface is empty

❌ Actual Behavior

No response

Contributor guide

Tech stack
typescript
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of REST APIsBasic familiarity with Dify's codebase
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Start by examining the endpoint handler for GET /datasets/{dataset id}/documents/metadata in the backend code (likely in the datasets module). Check if the metadata is being retrieved from the database and returned properly. Look for any recent changes to the API response format. Also review the API documentation to see if the metadata field is documented. The issue mentions that the API call succeeds but returns empty metadata, so the problem could be in the database query, serialization, or frontend display. Consider adding a debug log to trace the response data.