dify - โœ…(Solved) Fix improve output node [1 pull requests, 1 participants]

Official PRs (โ€ฆ)
ON THIS PAGE

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#35510โ€ขFetched 2026-04-24 06:14:23
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
1
Author
Participants
Timeline (top)
cross-referenced ร—1labeled ร—1

Fix Action

Fixed

PR fix notes

PR #35511: feat: improve output node

Description (problem / solution / changelog)

[!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

<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> <!-- If this PR was created by an automated agent, add `From <Tool Name>` as the final line of the description. Example: `From Codex`. -->

fix https://github.com/langgenius/dify/issues/35510

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

  • web/app/components/workflow/hooks/__tests__/use-available-blocks.spec.ts (modified, +6/-4)
  • web/app/components/workflow/hooks/__tests__/use-checklist.spec.ts (modified, +35/-0)
  • web/app/components/workflow/hooks/use-available-blocks.ts (modified, +2/-2)
  • web/app/components/workflow/hooks/use-checklist.ts (modified, +47/-0)
  • web/app/components/workflow/hooks/use-workflow-run-event/__tests__/use-workflow-finished.spec.ts (modified, +4/-1)
  • web/app/components/workflow/hooks/use-workflow-run-event/__tests__/use-workflow-text-chunk.spec.ts (modified, +48/-0)
  • web/app/components/workflow/hooks/use-workflow-run-event/use-workflow-started.ts (modified, +1/-0)
  • web/app/components/workflow/hooks/use-workflow-run-event/use-workflow-text-chunk.ts (modified, +12/-1)
  • web/app/components/workflow/hooks/use-workflow-run-event/use-workflow-text-replace.ts (modified, +1/-0)
  • web/app/components/workflow/nodes/end/__tests__/default.spec.ts (added, +32/-0)
  • web/app/components/workflow/nodes/end/default.ts (modified, +4/-1)
  • web/app/components/workflow/store/workflow/workflow-slice.ts (modified, +1/-0)
  • web/i18n/ar-TN/workflow.json (modified, +1/-0)
  • web/i18n/de-DE/workflow.json (modified, +1/-0)
  • web/i18n/en-US/workflow.json (modified, +1/-0)
  • web/i18n/es-ES/workflow.json (modified, +1/-0)
  • web/i18n/fa-IR/workflow.json (modified, +1/-0)
  • web/i18n/fr-FR/workflow.json (modified, +1/-0)
  • web/i18n/hi-IN/workflow.json (modified, +1/-0)
  • web/i18n/id-ID/workflow.json (modified, +1/-0)
  • web/i18n/it-IT/workflow.json (modified, +1/-0)
  • web/i18n/ja-JP/workflow.json (modified, +1/-0)
  • web/i18n/ko-KR/workflow.json (modified, +1/-0)
  • web/i18n/nl-NL/workflow.json (modified, +2/-1)
  • web/i18n/pl-PL/workflow.json (modified, +1/-0)
  • web/i18n/pt-BR/workflow.json (modified, +1/-0)
  • web/i18n/ro-RO/workflow.json (modified, +1/-0)
  • web/i18n/ru-RU/workflow.json (modified, +1/-0)
  • web/i18n/sl-SI/workflow.json (modified, +1/-0)
  • web/i18n/th-TH/workflow.json (modified, +1/-0)
  • web/i18n/tr-TR/workflow.json (modified, +1/-0)
  • web/i18n/uk-UA/workflow.json (modified, +1/-0)
  • web/i18n/vi-VN/workflow.json (modified, +1/-0)
  • web/i18n/zh-Hans/workflow.json (modified, +1/-0)
  • web/i18n/zh-Hant/workflow.json (modified, +1/-0)
  • web/types/workflow.ts (modified, +1/-0)
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Now there are 4 issues for the output node of workflow:

  1. you can add multi output nodes, but you only can add second output node by clicking the button of an edge.
  2. the user require to add a variable after add the output node, maybe add a default variable is better
  3. when two output nodes has a same name variable, one of it will lost, but there is no any hint
  4. if there are two variables in a single output node, they will display in different line in the workflow result panel. but if the two vars in different output nodes, they will display mixed together

2. Additional context or comments

<img width="1000" height="864" alt="Image" src="https://github.com/user-attachments/assets/17c576bc-cd53-4441-a490-98d4b86318f2" />
<img width="1236" height="500" alt="Image" src="https://github.com/user-attachments/assets/b73155d2-fbd4-4429-b280-253c072d9a29" />
<img width="1540" height="456" alt="Image" src="https://github.com/user-attachments/assets/bd6e6193-8642-4f42-8da1-95dbca6fd79e" />
<img width="2024" height="504" alt="Image" src="https://github.com/user-attachments/assets/7d8a2242-e9e7-44ce-831c-12c9b29831f3" />

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

extent analysis

TL;DR

To address the issues with output nodes in the workflow, consider implementing a default variable for new output nodes and improving the handling of duplicate variable names.

Guidance

  • Review the current implementation of adding output nodes and variables to identify why only the second output node can be added by clicking the button of an edge.
  • Investigate the possibility of adding a default variable when a new output node is added to streamline the user experience.
  • Develop a mechanism to handle duplicate variable names across multiple output nodes, such as displaying a warning or automatically renaming variables.
  • Examine the display logic for variables in the workflow result panel to ensure consistent formatting, whether variables are from the same or different output nodes.

Example

No specific code snippet can be provided without more context on the existing implementation, but a potential approach could involve modifying the addOutputNode function to include a default variable and checking for duplicate variable names across all output nodes.

Notes

The provided issue lacks specific technical details about the current implementation, making it challenging to offer a precise solution. However, the guidance points should help in addressing the identified issues.

Recommendation

Apply workaround: Implementing a default variable for new output nodes and improving duplicate variable name handling can enhance the user experience and address the reported issues.

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

dify - โœ…(Solved) Fix improve output node [1 pull requests, 1 participants]