Skip to content

[Bug]: HTTP API Document parse Stops at First Invalid ID in List, Leaving Subsequent Document Unparesed #6229

@asiroliu

Description

@asiroliu

Self Checks

  • 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).
  • Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
  • Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

x

RAGFlow image version

9b0b84ae20f8(infiniflow/ragflow:nightly)

Other environment information

Actual behavior

refer #5760 #6174 ,the unexpected API behavior in this case is related to the parse document endpoint.

Expected behavior

No response

Steps to reproduce

refer #5760 #6174

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions