dify - 💡(How to fix) Fix Workflow node returns data format exception [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35260Fetched 2026-04-16 07:06:46
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
1
Participants
Timeline (top)
labeled ×1
RAW_BUFFERClick to expand / collapse

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.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The workflow node returns conversion_fistory as array [object], but it cannot be obtained by subsequent nodes.

✔️ Expected Behavior

Subsequent nodes can obtain conversion_cistory normally.

❌ Actual Behavior

<img width="214" height="149" alt="Image" src="https://github.com/user-attachments/assets/963cb5b7-7ff3-4fdd-b2f0-65e97d94d95d" /> <img width="315" height="206" alt="Image" src="https://github.com/user-attachments/assets/d25a304e-db54-4f38-b54c-fdc9be7c3201" /> <img width="468" height="192" alt="Image" src="https://github.com/user-attachments/assets/a66691a5-2408-42c6-b36d-ba4ba0383848" />

extent analysis

TL;DR

The issue can be resolved by checking the data type and structure of the conversion_fistory variable in the workflow node and ensuring it is compatible with subsequent nodes.

Guidance

  • Verify the data type of conversion_fistory in the workflow node to ensure it is not an array of objects, which may be causing the issue.
  • Check the documentation of subsequent nodes to confirm they can handle the data type and structure of conversion_fistory.
  • Inspect the workflow configuration to ensure that the conversion_fistory variable is being passed correctly to subsequent nodes.
  • Consider adding a debugging node to inspect the value and structure of conversion_fistory before it is passed to subsequent nodes.

Notes

The provided images do not offer sufficient information to determine the root cause of the issue, and the problem may be specific to the workflow configuration or node implementations.

Recommendation

Apply workaround: Modify the workflow configuration to ensure compatibility between the conversion_fistory variable and subsequent nodes, as the root cause is likely related to data type or structure mismatch.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING