You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Row side panel repeatedly refetches sources, me, and clickhouse-proxy requests #2323
When I open a log or trace row side panel from the search page, the UI starts repeatedly calling:
GET /api/sources
GET /api/me
POST /api/clickhouse-proxy
The requests keep repeating while the side panel is open. Closing the side panel stops the loop.
The ClickHouse queries themselves are not failing. The /api/clickhouse-proxy responses are 200 OK, and ClickHouse query logs show successful queries with no exceptions. So this looks more like the frontend repeatedly refetching the row detail query, rather than a backend/query error retry.
Version
HyperDX / ClickStack app version: 2.27.0
Deployed via ClickStack Helm chart:
chart: clickstack/clickstack
chart version: 3.0.0
app version: 2.27.0
Steps to reproduce
Open the search page.
Click a log or trace row to open the side panel.
Keep the side panel open.
Watch the browser Network tab.
Expected behavior
The row detail query should run once, or a small bounded number of times, and then stop unless the row/source/time range changes.
Actual behavior
The browser keeps repeating the same request pattern:
GET /api/sources
GET /api/me
POST /api/clickhouse-proxy
In one reproduction, the app logged roughly 250 requests per minute for each of those endpoints while the side panel was open.
The ClickHouse query was returning successfully with one row, so it did not look like a failed-query retry loop.
Closing this for now, as I can no longer reproduce it after recreating the affected environment.
This now looks specific to my deployment state rather than a general HyperDX issue. I'll reopen or file a new issue if I can reproduce it again consistently.
Activity
shokada commentedon May 29, 2026
Closing this for now, as I can no longer reproduce it after recreating the affected environment.
This now looks specific to my deployment state rather than a general HyperDX issue. I'll reopen or file a new issue if I can reproduce it again consistently.