dify - 💡(How to fix) Fix Tracing enable toggle sends enabled=true without tracing_provider after Langfuse is configured [1 pull requests]

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

1.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Deploy Dify 1.14.1 with Docker Compose.
2. Deploy Langfuse separately.
3. Configure Langfuse in an app's Monitoring / Tracing panel.
4. Confirm the Langfuse config is saved and shown as configured.
5. Open the Monitoring page.
6. Click the global tracing enable toggle.
7. The UI shows a validation error: "tracing_provider is required when enabled is True".

✔️ Expected Behavior

When Langfuse is already configured, enabling tracing should send both enabled=true and tracing_provider="langfuse", then the app tracing setting should be saved successfully.

❌ Actual Behavior

The enable toggle appears to send enabled=true without tracing_provider. The backend rejects the request with an AppTracePayload validation error.

<img width="264" height="110" alt="Image" src="https://github.com/user-attachments/assets/79e793b0-f9cc-45c8-a8ca-f1f2e208f783" /> <img width="301" height="64" alt="Image" src="https://github.com/user-attachments/assets/ee7241b6-cb81-4efc-a2cd-92e7166ec3dd" />