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

Optimization of Node execution Records #20166

New Issue
Closed
opened 2026-02-21 20:06:08 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:06:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @FyhSky on GitHub (Nov 5, 2025).

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.

As time goes by, the operation logs of nodes are getting larger and larger. Have you considered storing the operation logs of nodes in another location instead of in the database?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @FyhSky on GitHub (Nov 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] 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] 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. As time goes by, the operation logs of nodes are getting larger and larger. Have you considered storing the operation logs of nodes in another location instead of in the database? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:06:08 -05:00
yindo closed this issue 2026-02-21 20:06:09 -05:00
yindo commented 2026-02-21 20:06:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 11, 2025):

Hi, @FyhSky. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You proposed optimizing node execution records by storing operation logs externally to better manage their growing size.
  • You have reviewed the contributing guidelines and existing issues and expressed interest in contributing to this enhancement.
  • There has been no further discussion or activity on this issue since your initial proposal.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 11, 2025): Hi, @FyhSky. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You proposed optimizing node execution records by storing operation logs externally to better manage their growing size. - You have reviewed the contributing guidelines and existing issues and expressed interest in contributing to this enhancement. - There has been no further discussion or activity on this issue since your initial proposal. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - If I do not hear back within 15 days, this issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 20:06:09 -05:00
Author
Owner
Copy Link
Copy Source

@FyhSky commented on GitHub (Dec 23, 2025):

Hi, @FyhSky. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You proposed optimizing node execution records by storing operation logs externally to better manage their growing size.
  • You have reviewed the contributing guidelines and existing issues and expressed interest in contributing to this enhancement.
  • There has been no further discussion or activity on this issue since your initial proposal.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

Hi Dosu,

Thank you for reaching out. I have reviewed the latest version of Dify and confirmed that the issue of optimizing node execution records by storing operation logs externally is still relevant. This optimization is important for managing the growing size of execution records and improving overall performance.

I am still interested in contributing to this enhancement. Please let me know if there are any updates or if there is anything specific I can do to move this forward.

Best regards,
FyhSky

@FyhSky commented on GitHub (Dec 23, 2025): > Hi, [@FyhSky](https://github.com/FyhSky). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You proposed optimizing node execution records by storing operation logs externally to better manage their growing size. > * You have reviewed the contributing guidelines and existing issues and expressed interest in contributing to this enhancement. > * There has been no further discussion or activity on this issue since your initial proposal. > > **Next Steps:** > > * Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. > * If I do not hear back within 15 days, this issue will be automatically closed. > > Thank you for your understanding and contribution! Hi Dosu, Thank you for reaching out. I have reviewed the latest version of Dify and confirmed that the issue of optimizing node execution records by storing operation logs externally is still relevant. This optimization is important for managing the growing size of execution records and improving overall performance. I am still interested in contributing to this enhancement. Please let me know if there are any updates or if there is anything specific I can do to move this forward. Best regards, FyhSky
yindo commented 2026-02-21 20:06:09 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 23, 2025):

@crazywoola The user @FyhSky has confirmed that the issue regarding optimizing node execution records by storing operation logs externally is still relevant and is interested in contributing to this enhancement. Could you please assist them with the next steps?

@dosubot[bot] commented on GitHub (Dec 23, 2025): @crazywoola The user @FyhSky has confirmed that the issue regarding optimizing node execution records by storing operation logs externally is still relevant and is interested in contributing to this enhancement. Could you please assist them with the next steps?
yindo commented 2026-02-21 20:06:09 -05:00
Author
Owner
Copy Link
Copy Source

@hangshao009 commented on GitHub (Dec 24, 2025):

I discovered this problem when using the workflow for medical record quality control. The execution records kept piling up in the database, but I didn't have an API to delete them. This is a serious challenge. Many times, we don't need to keep logs of expired database storage.

@hangshao009 commented on GitHub (Dec 24, 2025): I discovered this problem when using the workflow for medical record quality control. The execution records kept piling up in the database, but I didn't have an API to delete them. This is a serious challenge. Many times, we don't need to keep logs of expired database storage.
yindo commented 2026-02-21 20:06:09 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Dec 26, 2025):

now you can save in aliyun sls

@fatelei commented on GitHub (Dec 26, 2025): now you can save in aliyun sls
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 💪 enhancement
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#20166
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?