Issue Station
Sign In
Tools hereToolbox

dify - ✅(Solved) Fix Answer node structured_output variable picker closes and output is missing from run result [2 pull requests, 1 comments, 2 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#35730•Fetched 2026-05-01 05:53:27
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
1
Author
BlackouttaBlackoutta
Participants
BlackouttaBlackouttaiamjoeliamjoel
Assignees
fateleifateleiiamjoeliamjoel
Timeline (top)
cross-referenced ×3assigned ×2labeled ×2closed ×1

Fix Action

Fixed

PR fix notes

PR #35732: fix: var reference picker can not choose sub vars

Description (problem / solution / changelog)

Fix the first issue of https://github.com/langgenius/dify/issues/35730

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint && make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

Changed files

  • eslint-suppressions.json (modified, +0/-5)
  • web/app/components/base/prompt-editor/plugins/component-picker-block/__tests__/index.spec.tsx (modified, +42/-0)
  • web/app/components/base/prompt-editor/plugins/component-picker-block/index.tsx (modified, +8/-5)
  • web/app/components/workflow/nodes/_base/components/variable/object-child-tree-panel/picker/field.tsx (modified, +1/-1)
  • web/app/components/workflow/nodes/_base/components/variable/var-reference-vars.tsx (modified, +3/-2)

PR #35747: fix: fix structured_output_enabled miss in second validate

Description (problem / solution / changelog)

This reverts commit 071033418024406638d61877fc4d19c9ddbe74a8.

[!IMPORTANT]

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

fix #35730

structured_output_enabled after second validate, it miss and become to false

Screenshots

BeforeAfter
......

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint && make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

Changed files

  • api/core/workflow/node_factory.py (modified, +9/-6)
  • api/tests/unit_tests/core/workflow/graph_engine/test_tool_in_chatflow.py (modified, +49/-0)
  • api/tests/unit_tests/core/workflow/nodes/answer/test_answer.py (modified, +77/-0)
  • api/tests/unit_tests/core/workflow/test_node_factory.py (modified, +87/-3)
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.14.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This issue groups two symptoms that both appear to be related to structured_output in an Answer node.

Issue 1: variable picker disappears when hovering over structured_output

  1. Create or open a workflow that has a node exposing a structured_output variable.
  2. Add an Answer node.
  3. Open the variable selection window in the Answer node.
  4. Move the mouse over the structured_output variable.

https://github.com/user-attachments/assets/6dc3b44b-7359-42bc-bad6-f4d06489adc0

Issue 2: configured structured output does not appear in the run result

  1. In the Answer node, configure it to use structured output.
  2. Run the workflow.
  3. Check the final run result/output.

https://github.com/user-attachments/assets/ffc17314-d75d-4761-a5e5-12c55583afe4

✔️ Expected Behavior

  1. In the Answer node, hovering over the structured_output variable should keep the variable selection window open, so the variable can be selected normally.
  2. If structured output is configured in the Answer node, the corresponding structured output should appear in the workflow run result.

❌ Actual Behavior

  1. When the mouse moves over the structured_output variable in the Answer node, the variable selection window disappears immediately, preventing normal selection.
  2. Although structured output is configured in the Answer node, it does not appear in the final run result.

extent analysis

TL;DR

The issue can be addressed by investigating and potentially updating the handling of structured_output variables in the Answer node, specifically regarding hover behavior and output display.

Guidance

  • Review the code responsible for rendering the variable selection window in the Answer node to ensure it correctly handles hover events over structured_output variables.
  • Verify that the Answer node's configuration for structured output is correctly implemented and that the output is properly passed through to the workflow run result.
  • Check for any CSS or JavaScript issues that might cause the variable selection window to disappear on hover.
  • Test the Answer node with different types of variables to isolate if the issue is specific to structured_output variables.

Example

No specific code example can be provided without access to the actual codebase, but the fix might involve modifying event listeners or CSS rules related to the variable selection window.

Notes

The solution may require updates to the frontend code of the Answer node, specifically in how it handles user interactions and displays variables. Without access to the code, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by manually selecting the structured_output variable without hovering over it, if possible, until a permanent fix can be implemented. This approach allows for temporary mitigation of the issue while a more robust solution is developed.

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…
#api#ssr#file not found#serialization error#model compatibility

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

dify - ✅(Solved) Fix Answer node structured_output variable picker closes and output is missing from run result [2 pull requests, 1 comments, 2 participants]