Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix Regarding the issue where the WORKFLOW_LOG_CLEANUP_SPECIFIC_WORKFLOW_IDS configuration parameter is not taking effect [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35545•Fetched 2026-04-24 10:43:34
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
1
Author
xieshifeng985xieshifeng985
Participants
dosubot[bot]dosubot[bot]xieshifeng985xieshifeng985
Timeline (top)
closed ×1commented ×1labeled ×1
RAW_BUFFERClick to expand / collapse

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

V1.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have configured the following parameters to retain application logs with appid 20561d75-9589-43e6-943a-43ee4040d6be for only 3 days, but it is not taking effect; WORKFLOW_LOG_CLEANUP_ENABLED=true WORKFLOW_LOG_RETENTION_DAYS=3 WORKFLOW_LOG_CLEANUP_BATCH_SIZE=100 WORKFLOW_LOG_CLEANUP_SPECIFIC_WORKFLOW_IDS=20561d75-9589-43e6-943a-43ee4040d6be

The way to obtain APPID is shown in the figure below <img width="852" height="106" alt="Image" src="https://github.com/user-attachments/assets/2f7f1e06-e9f6-4388-8502-360861a77094" /> The log of the APP is still from 7 days ago, indicating that the configuration has not taken effect, as shown in the following image <img width="1909" height="677" alt="Image" src="https://github.com/user-attachments/assets/59dd56c6-a8a4-4498-9415-db66dc4b4b4b" />

✔️ Expected Behavior

I hope to retain only the most recent 3 days of application log information based on the configuration parameters <img width="1895" height="652" alt="Image" src="https://github.com/user-attachments/assets/422a077f-ac76-4da2-9591-c809b24d0946" />

WORKFLOW_LOG_CLEANUP_ENABLED=true WORKFLOW_LOG_RETENTION_DAYS=3 WORKFLOW_LOG_CLEANUP_BATCH_SIZE=100 WORKFLOW_LOG_CLEANUP_SPECIFIC_WORKFLOW_IDS=20561d75-9589-43e6-943a-43ee4040d6be

❌ Actual Behavior

No response

extent analysis

TL;DR

Check the configuration parameters and ensure they are correctly applied to the self-hosted Docker environment.

Guidance

  • Verify that the environment variables WORKFLOW_LOG_CLEANUP_ENABLED, WORKFLOW_LOG_RETENTION_DAYS, WORKFLOW_LOG_CLEANUP_BATCH_SIZE, and WORKFLOW_LOG_CLEANUP_SPECIFIC_WORKFLOW_IDS are correctly set in the Docker configuration.
  • Check the Docker container logs to see if there are any errors related to the log cleanup process.
  • Confirm that the WORKFLOW_LOG_CLEANUP_SPECIFIC_WORKFLOW_IDS parameter is correctly formatted and matches the expected APPID.
  • Review the documentation for the self-hosted Docker environment to ensure that the configuration parameters are being applied correctly.

Notes

The issue may be related to the configuration parameters not being applied correctly to the self-hosted Docker environment. Without more information about the Docker configuration and environment, it is difficult to provide a more specific solution.

Recommendation

Apply workaround by double-checking the configuration parameters and ensuring they are correctly applied to the self-hosted Docker environment, as the issue seems to be related to configuration rather than a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#container setup#orchestration issue#cache issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING