is there any way to cleanup the history data in Dify?

[dickens88]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Content

Hi guys,

I had Dify running in my server for several months. It seems Dify will keep all the history data include the logs and never remove?

Now the volumes of myu Dify instance is very huge and i have to remove the history data manully, which i think is very dangerous operation. Is there any settings in Dify to manage the TTL of those data? for example the data will be remove automatically after 3 months.

[dosubot[bot]]

Dify does not automatically clean up all history or log data by default, but it does provide some built-in scheduled cleanup tasks you can enable and configure:

• Workflow run logs: You can enable automatic cleanup by setting the environment variable WORKFLOW_LOG_CLEANUP_ENABLED=true in your docker-compose.yaml or .env file. You can also set WORKFLOW_LOG_RETENTION_DAYS (default is 30) to control how long logs are kept. This scheduled task will remove workflow logs and related data older than the retention period every day at 2:00 AM. See details in the code reference.

• Message history: There is a cleanup task for messages, but it only runs for apps on the "SANDBOX" cloud plan. The retention period is controlled by PLAN_SANDBOX_CLEAN_MESSAGE_DAY_SETTING. This deletes messages and related records older than the configured number of days, but is not available for all plans or self-hosted setups. Reference

• Files and uploads: There is no built-in TTL or automatic cleanup for uploaded files or attachments in the community version. File cleanup only happens when you explicitly delete datasets or documents. To manage disk space, you can write a scheduled script to delete files older than a certain age from both storage and the database. A sample script and instructions are available in this discussion.

• Other storage (Redis, Weaviate, etc.): No automatic TTL or cleanup is configured by default. You need to manage retention for these stores externally if needed.

Important: Always back up your data before running any manual cleanup or custom scripts. Manual deletion of database records or files can be risky if not done carefully.

For more details, see the FAQ on storage cleanup and the docker-compose.yaml reference.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}