langfuse-web connect clickhouse timeout

[zym951223]

Describe your question

2026-08-05T08:36:25.499Z error [Connection] Query: HTTP request error.
Error: Timeout error.
at Socket.onTimeout (/app/node_modules/.pnpm/@ClickHouse+client@1.18.5/node_modules/@clickhouse/client/dist/connection/socket_pool.js:536:68)
at Object.onceWrapper (node:events:630:28)
at Socket.emit (node:events:521:24)
at Socket.onTimeout (node:net:610:8)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7)
2026-08-05T08:36:25.499Z error ClickHouse query failed with non-retryable error: Timeout error.
2026-08-05T08:36:25.500Z warn ClickHouse resource limit exceeded Timeout error.
2026-08-05T08:36:25.500Z warn middleware intercepted error with code UNPROCESSABLE_CONTENT
2026-08-05T08:36:25.500Z error tRPC route failed on dashboard.executeQuery: Your query could not be completed. Please narrow your request by adding more specific filters (e.g., a shorter date range). Your query could not be completed. Please narrow your request by adding more specific filters (e.g., a shorter date range).
TRPCError: Your query could not be completed. Please narrow your request by adding more specific filters (e.g., a shorter date range).
at /app/web/.next/server/chunks/[root-of-the-server]__0tb27v5..js:1:3778
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-RoZMIBeA.mjs:256:18)
at async file:///app/node_modules/.pnpm/@baselime+trpc-opentelemetry-middleware@0.1.2_@opentelemetry+api@1.9.0_@trpc+server@11.13.4_typescript@5.9.2_/node_modules/@baselime/trpc-opentelemetry-middleware/dist/index.js:43:22
at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-RoZMIBeA.mjs:256:18)
at async callRecursive (file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-RoZMIBeA.mjs:256:18)
at async procedure (file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/initTRPC-RoZMIBeA.mjs:281:18)
at async file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/resolveResponse-CHqBlAgR.mjs:1948:18
at async resolveResponse (file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/resolveResponse-CHqBlAgR.mjs:1977:28)
at async file:///app/node_modules/.pnpm/@trpc+server@11.13.4_typescript@5.9.2/node_modules/@trpc/server/dist/node-http-Czyjz3cK.mjs:208:22

Langfuse Cloud or Self-Hosted?

Langfuse Cloud

If Self-Hosted

langfuse-web 3.180.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 timeout error is occurring on a dashboard query (dashboard.executeQuery) where ClickHouse couldn't complete the request within the allowed time. The error message itself provides the solution: narrow your request by adding more specific filters such as a shorter date range. (1)

A few things to check:

1. Query scope: The query being executed is too broad. Try:

• Reducing the date range in your dashboard filters
• Adding more specific filters (user, tags, metadata, etc.)
• Breaking down large queries into smaller, more focused ones (2)

2. ClickHouse resources: If you're self-hosting (you mentioned langfuse-web 3.180.0), ensure your ClickHouse instance has adequate CPU and memory. ClickHouse is CPU and memory intensive for analytical and highly concurrent requests. (1)

3. Network connectivity: Verify that Langfuse Web can reliably reach your ClickHouse instance. Review IP whitelisting if applicable and check network latency between the containers. (1)

4. Disk space: Check if ClickHouse is running low on disk space, which can cause performance issues. You can verify this by running:

kubectl exec -it <clickhouse-pod-name> -- df -h /var/lib/clickhouse

(1)

If you're on Langfuse Cloud (as indicated), this is likely a query scope issue rather than infrastructure. Try narrowing your dashboard query filters first.

📚 Sources:

1. ClickHouse
2. Custom Dashboards

---

Have another question? Just tag @inkeep.

[CodeCLS]

Hi @zym951223, did Inkeep's answer help you?