langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #31843] feat(api): add scheduled cleanup task for specific workflow logs #33434

New Issue
Closed
opened 2026-02-21 20:53:16 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:53:16 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/31843

State: closed
Merged: Yes

Add a new Celery task to clean up workflow run logs for specific workflows with an independent retention policy. This allows setting different retention periods for high-volume workflows without affecting others.

Configuration:

  • SPECIFIC_WORKFLOW_LOG_CLEANUP_ENABLED: enable/disable the task
  • SPECIFIC_WORKFLOW_IDS: comma-separated workflow IDs to clean
  • SPECIFIC_WORKFLOW_LOG_RETENTION_DAYS: retention period (default: 7 days)

The task runs daily at 3:00 AM and cascades deletion to all related records.

close https://github.com/langgenius/dify/issues/31883

Summary

Screenshots

Before After
... ...

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 and make type-check (backend) and cd web && npx lint-staged (frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/31843 **State:** closed **Merged:** Yes --- Add a new Celery task to clean up workflow run logs for specific workflows with an independent retention policy. This allows setting different retention periods for high-volume workflows without affecting others. Configuration: - SPECIFIC_WORKFLOW_LOG_CLEANUP_ENABLED: enable/disable the task - SPECIFIC_WORKFLOW_IDS: comma-separated workflow IDs to clean - SPECIFIC_WORKFLOW_LOG_RETENTION_DAYS: retention period (default: 7 days) The task runs daily at 3:00 AM and cascades deletion to all related records. close https://github.com/langgenius/dify/issues/31883 ## 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. --> ## Screenshots | Before | After | |--------|-------| | ... | ... | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `make lint` and `make type-check` (backend) and `cd web && npx lint-staged` (frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:53:16 -05:00
yindo closed this issue 2026-02-21 20:53:16 -05:00
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 pull-request
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#33434
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?