[BUG] Can the retention period of CozeLoop’s trace be extended beyond 7 days?

[flyJia]

📋 CheckList

• I have searched existing issues to avoid duplicates
• I am using a recently maintained version of Coze Loop
• I have provided all required information
• I understand this is a bug report and not a feature request
• I have submitted this report in English (otherwise it will not be processed)

🐛 Bug Description

Can the retention period of CozeLoop’s trace be extended beyond 7 days?

🔄 Steps to Reproduce

Can the retention period of CozeLoop’s trace be extended beyond 7 days?

✅ Expected Behavior

Can the retention period of CozeLoop’s trace be extended beyond 7 days?

❌ Actual Behavior

Can the retention period of CozeLoop’s trace be extended beyond 7 days?

🚨 Severity

None

🔧 Component

None

💻 Environment

No response

🔧 Go Environment

No response

📋 Logs

📝 Additional Context

No response

[kidkidkid]

you mean the self hosted coze-loop trace duration? It should beyond 7 days now.

[kidkidkid]

i see, do you mean the frontend can only select the latest 7 days?

[flyJia]

Excatly，the frontend can only select the latest 7 days. Has this bug been fixed in version 1.1.0 of the Docker image?

[kidkidkid]

Excatly，the frontend can only select the latest 7 days. Has this bug been fixed in version 1.1.0 of the Docker image?

yes, it will be fixed in later version, but not the 1.1.0 version.