bug(self-hosted v4.6.0): Trace list shows traces but trace detail page returns "Trace not found"

[jiege3324]

Describe your question

Describe the bug

I am running Langfuse self-hosted v4.6.0.

The Tracing list page shows traces correctly, but when I click a trace, the detail page shows:

"Trace not found
The trace is either still being processed or has been deleted."

The trace data exists in ClickHouse, but the UI cannot load the trace detail.

---

Langfuse setup

Deployment:

• Kubernetes (Helm)
• Self-hosted

Version:

• langfuse-web: 4.6.0
• langfuse-worker: 4.6.0

Components:

• PostgreSQL
• ClickHouse 26.5.6
• Redis

---

Steps to reproduce

1. Send tracing data through Langfuse SDK.
2. Open:

Tracing -> select a trace from the list

3. The trace detail panel shows:

Langfuse Cloud or Self-Hosted?

Self-Hosted

If Self-Hosted

4.6.0

If Langfuse Cloud

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[inkeep-ai-assistant[bot]]

This "Trace not found" issue where the list shows traces but the detail page cannot load them is typically caused by a ClickHouse timezone misconfiguration.

ClickHouse must run with its timezone set to UTC (the default). Langfuse does not support non-UTC ClickHouse timezones. Running ClickHouse with a different timezone will cause queries to return incorrect or empty results. (1)

Verify Your ClickHouse Timezone

Run this query against your ClickHouse instance:

SELECT timezone()

(1)

This should return UTC. If it returns something else (e.g., Asia/Shanghai, Europe/Berlin), that's the cause of your issue.

How to Fix

If the timezone is not UTC, update your ClickHouse server configuration to remove any custom timezone setting and restart the server. (1)

The same UTC requirement applies to PostgreSQL as well — all infrastructure components must use UTC. (1)

Additional Checks

If the timezone is already UTC, verify that:

• The Langfuse worker container is running and processing events properly
• Redis connectivity is working (used for queuing and caching)
• Check worker container logs for any processing errors

The trace list query and trace detail query may use different query paths, which explains why the list works but detail lookups fail when there's a timezone mismatch.

📚 Sources:

1. ClickHouse

---

Have another question? Just tag @inkeep.