langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

can't access to round of agent node on error #623

New Issue
Closed
opened 2026-02-16 10:19:57 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:19:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @nicho2 on GitHub (Sep 5, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

have an error on agent node

✔️ Expected Behavior

access to details of agent node even when there is an error

Image Image

❌ Actual Behavior

can't access to the details.

Image
Originally created by @nicho2 on GitHub (Sep 5, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.8.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce have an error on agent node ### ✔️ Expected Behavior access to details of agent node even when there is an error <img width="488" height="327" alt="Image" src="https://github.com/user-attachments/assets/7c8ac1eb-74b3-4295-b647-87d0eca9f9cb" /> <img width="572" height="355" alt="Image" src="https://github.com/user-attachments/assets/6bb118b9-2b58-4957-bf90-d58cabbfe1b4" /> ### ❌ Actual Behavior can't access to the details. <img width="491" height="692" alt="Image" src="https://github.com/user-attachments/assets/c2d01e41-d04e-4807-ba64-0d1f5398cc11" />
yindo added the bug label 2026-02-16 10:19:57 -05:00
yindo closed this issue 2026-02-16 10:19:57 -05:00
yindo commented 2026-02-16 10:19:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 5, 2025):

This issue isn't tracked in existing tickets, but based on the code and recent updates, Dify is designed to let you access agent node details and error logs even when a node fails, as long as error and agentLog data are present in the backend response. There’s no intentional block in the UI or backend for error states—if you can’t access details, it’s likely due to missing or malformed agentLog data, or a frontend state issue in v1.8.0.

Recent versions (mid-2025) have improved agent log handling and detail rendering, so upgrading may resolve this problem if it’s caused by data or UI bugs in your current version. If you’re unable to upgrade, check that your backend is returning agentLog and error fields for failed nodes, and that your frontend is up-to-date with log rendering logic. More details on the architecture and recent changes can be found here and here.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 5, 2025): <!-- Answer --> This issue isn't tracked in existing tickets, but based on the code and recent updates, Dify is designed to let you access agent node details and error logs even when a node fails, as long as error and agentLog data are present in the backend response. There’s no intentional block in the UI or backend for error states—if you can’t access details, it’s likely due to missing or malformed agentLog data, or a frontend state issue in v1.8.0. Recent versions (mid-2025) have improved agent log handling and detail rendering, so upgrading may resolve this problem if it’s caused by data or UI bugs in your current version. If you’re unable to upgrade, check that your backend is returning agentLog and error fields for failed nodes, and that your frontend is up-to-date with log rendering logic. More details on the architecture and recent changes can be found [here](https://github.com/langgenius/dify/pull/24080) and [here](https://github.com/langgenius/dify/blob/cd95237ae4c61b6d90a9977957aed22a33a26b74/web/app/components/workflow/run/node.tsx). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a87a0bf8-cba6-43e1-8006-afcf644458c2?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1667)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#623
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?