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

[PR #28136] chore: disable workflow logs auto-cleanup by default #31956

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

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

State: closed
Merged: Yes

Summary

This PR changes the default value of WORKFLOW_LOG_CLEANUP_ENABLED from true to false across all configuration files.

Changes

  • api/configs/feature/__init__.py: Changed WorkflowLogConfig.WORKFLOW_LOG_CLEANUP_ENABLED default from True to False
  • api/.env.example: Changed WORKFLOW_LOG_CLEANUP_ENABLED from true to false

Note: docker/.env.example and docker/docker-compose.yaml already had the correct default value of false.

Motivation

Setting the default to false provides safer default behavior by:

  • Preventing unintended data loss for new installations
  • Giving users explicit control over when to enable log cleanup
  • Following the opt-in principle for data deletion features

Users who need automatic cleanup can enable it by setting WORKFLOW_LOG_CLEANUP_ENABLED=true in their configuration.

Fixes #28135

**Original Pull Request:** https://github.com/langgenius/dify/pull/28136 **State:** closed **Merged:** Yes --- ## Summary This PR changes the default value of `WORKFLOW_LOG_CLEANUP_ENABLED` from `true` to `false` across all configuration files. ## Changes - **api/configs/feature/__init__.py**: Changed `WorkflowLogConfig.WORKFLOW_LOG_CLEANUP_ENABLED` default from `True` to `False` - **api/.env.example**: Changed `WORKFLOW_LOG_CLEANUP_ENABLED` from `true` to `false` Note: `docker/.env.example` and `docker/docker-compose.yaml` already had the correct default value of `false`. ## Motivation Setting the default to `false` provides safer default behavior by: - Preventing unintended data loss for new installations - Giving users explicit control over when to enable log cleanup - Following the opt-in principle for data deletion features Users who need automatic cleanup can enable it by setting `WORKFLOW_LOG_CLEANUP_ENABLED=true` in their configuration. Fixes #28135
yindo added the pull-request label 2026-02-21 20:50:28 -05:00
yindo closed this issue 2026-02-21 20:50:28 -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#31956
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?