[Bug]: Iteration component output contains references but downstream Generate node receives empty reference values

[Alphayellowcat]

Self Checks

• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (Language Policy).
• [x] Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• [x] Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

v0.19.0 slim

RAGFlow image version

v0.19.0 slim

Other environment information

Actual behavior

1. Iteration component outputs contain both content and reference fields
2. Generate component receives the iteration output but reference field is empty
3. Final generated report lacks citation markers (##1$$, ##2$$) and source references
4. Only content text is preserved, all citation information is lost

Expected behavior

1. Iteration component output should preserve reference information when passed to downstream components
2. Generate component should receive complete data including references
3. Final output should contain proper citations with reference markers
4. Citation information should be maintained throughout the component chain

Steps to reproduce

1. Create a workflow: Iteration (with Retrieval + Generate inside) → Generate (report generation)
2. Configure Retrieval component with cite=true
3. Configure inner Generate component with cite=true to preserve references
4. Configure outer Generate component to reference the iteration output: {Iteration:ComponentName}
5. Run the workflow and observe that references are lost in the final output

Additional information

• Issue occurs specifically when referencing iteration output in Generate components
• Iteration internal components (Retrieval, Generate) work correctly and show references
• Problem appears to be in the data transfer between Iteration and external Generate components
• Workaround: Currently no known workaround for preserving references across this component boundary

[KevinHuSh]

We‘re refactoring and refining this part. The new version is coming soon.