langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The log shows that a certain node has retried four times, but the retry details are empty #15506

New Issue
Closed
opened 2026-02-21 19:22:03 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:22:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @auxpd on GitHub (Jul 20, 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.6.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image Image

✔️ Expected Behavior

Can see the step information for four retries

❌ Actual Behavior

The content that appears after clicking to retry the number of times is empty

Originally created by @auxpd on GitHub (Jul 20, 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.6.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="571" height="86" alt="Image" src="https://github.com/user-attachments/assets/5e2c26dc-2cf3-40f9-bcd8-0aca3f2d0bc0" /> <img width="621" height="205" alt="Image" src="https://github.com/user-attachments/assets/00cfdcfb-c252-493f-ae37-fedcfccd6520" /> ### ✔️ Expected Behavior Can see the step information for four retries ### ❌ Actual Behavior The content that appears after clicking to retry the number of times is empty
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:22:03 -05:00
yindo closed this issue 2026-02-21 19:22:03 -05:00
yindo commented 2026-02-21 19:22:03 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 20, 2025):

The retry details in the UI depend on the backend returning all node execution records with status "retry" for the workflow run. If you see a nonzero retry count but the details are empty, it's likely that either (a) the backend isn't logging or returning those retry executions, or (b) the frontend can't map them due to missing or inconsistent metadata. Recent changes—like the removal of the retry_index column from the workflow_node_executions table—could affect how these details are stored or displayed, especially if your database migration didn't complete cleanly or if the backend logic expects fields that no longer exist (source).

To troubleshoot, check the API response from /apps/{app_id}/workflow-runs/{run_id}/node-executions for the affected run and see if executions with status "retry" are present. If they're missing, review backend logs for errors during workflow execution or database migration. If the executions are present but not shown in the UI, inspect the returned metadata (like node_id, iteration/loop indices) for completeness and consistency. This will help pinpoint whether the issue is in backend data logging, API response, or frontend mapping logic.

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 (Jul 20, 2025): <!-- Answer --> The retry details in the UI depend on the backend returning all node execution records with status "retry" for the workflow run. If you see a nonzero retry count but the details are empty, it's likely that either (a) the backend isn't logging or returning those retry executions, or (b) the frontend can't map them due to missing or inconsistent metadata. Recent changes—like the removal of the `retry_index` column from the `workflow_node_executions` table—could affect how these details are stored or displayed, especially if your database migration didn't complete cleanly or if the backend logic expects fields that no longer exist ([source](https://github.com/langgenius/dify/pull/19285)). To troubleshoot, check the API response from `/apps/{app_id}/workflow-runs/{run_id}/node-executions` for the affected run and see if executions with status "retry" are present. If they're missing, review backend logs for errors during workflow execution or database migration. If the executions are present but not shown in the UI, inspect the returned metadata (like node_id, iteration/loop indices) for completeness and consistency. This will help pinpoint whether the issue is in backend data logging, API response, or frontend mapping logic. <!-- 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/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2edfae1d-c299-4ae1-ac4b-5c3fc7875bc5?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/issues/22665)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug 🤔 cant-reproduce
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#15506
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?