Latency regression
hcss_api p95 slowed 284%
1.3 s now vs 336 ms previously across 40 calls.
Open the tool view and inspect the slowest recent calls for a repeatable bottleneck.
InvestigateBidlo Status Frontend
Chat tool telemetry
Find slow, failing, and repetitive agent tools without exposing prompts, arguments, or outputs.
Detailed production timing active
6101 of 6166 saved tool calls include execution duration.
Tool calls
40
+264% vs previous 7d6 saved production turns
p50 latency
272 ms
+20% vs previous 7d40 timed calls
p95 latency
1.3 s
+284% vs previous 7d40 timed calls
Tool failures
0.0%
-9.1 pts vs previous 7d0 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
6.7
+82% vs previous 7d83.3% of turns at 5+ calls
What changed
Material regressions ranked by severity and affected call volume.
Regression checks require at least 3 calls in both windows. Latency is flagged at +20%; failure and no-result rates are flagged at +1 and +3 points respectively.
Execution volume
Successful calls, no-results, and failures combined.
Calls
Oct 1Oct 4Oct 7
Payload pressure
How often results exceed the 20 KB inline cap.
5.0%
handle rows / all calls
309 stored handles in this period. This is a payload-size proxy, not a one-to-one call classification.
Tool comparison
Each change is measured against the previous equal window; latency appears only where detailed timing exists.
| Tool | Calls | p50 | p95 | Failures | No result |
|---|---|---|---|---|---|
| hcss_api | 40+264% vs prior | 272 ms+20% vs prior | 1.3 s+284% vs prior | 0.0%-9.1 pts vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
No operational failures
in the selected view
Interpretation notes
The data has known edges that change what a chart means.
- Blocked loops are invisible
- Rate-limited and identical-argument calls are rejected before telemetry fires.
- NoResults is not downtime
- It remains a failed tool outcome, but is separated from runtime reliability here.
- Preview volume lives elsewhere
- Preview and threadless chats reach PostHog but are intentionally absent from Postgres.
- Latency is partially instrumented
- Saved tool parts provide production outcomes and volume; duration appears only on calls with detailed telemetry.
- Partial turns are retained
- They remain in volume counts but are excluded from failures and latency percentiles.
- Comparisons use equal windows
- Every delta compares the selected period with the immediately preceding period under the same tool and team filters.
Recent sanitized calls
Arguments, outputs, user IDs, and message content are never rendered.
hcss_apiTRP 2229 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_lsi…
Turn sequence
9 of 58
Turn state
Completed
hcss_apiTRP 2185 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_3kb…
Turn sequence
14 of 58
Turn state
Completed
hcss_apiTRP 2190 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_y8T…
Turn sequence
15 of 58
Turn state
Completed
hcss_apiTRP 2225 msOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_3S2…
Turn sequence
16 of 58
Turn state
Completed
hcss_apiTRP 22.2 sOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_UiR…
Turn sequence
17 of 58
Turn state
Completed
hcss_apiTRP 2321 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_FH3…
Turn sequence
18 of 70
Turn state
Completed
hcss_apiTRP 2187 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_noE…
Turn sequence
22 of 70
Turn state
Completed
hcss_apiTRP 2272 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_8TN…
Turn sequence
24 of 70
Turn state
Completed
hcss_apiTRP 2327 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_bHi…
Turn sequence
26 of 70
Turn state
Completed
hcss_apiTRP 2253 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_4uA…
Turn sequence
32 of 70
Turn state
Completed
hcss_apiTRP 2437 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_kVq…
Turn sequence
33 of 70
Turn state
Completed
hcss_apiTRP 2558 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_gBV…
Turn sequence
34 of 70
Turn state
Completed
hcss_apiTRP 2163 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_1fz…
Turn sequence
35 of 70
Turn state
Completed
hcss_apiTRP 2194 msOct 6, 12:23 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_nbU…
Turn sequence
52 of 70
Turn state
Completed
hcss_apiTRP 2248 msSep 30, 3:35 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_KSM…
Turn sequence
3 of 4
Turn state
Completed
hcss_apiTRP 2343 msSep 30, 3:35 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_PsJ…
Turn sequence
4 of 4
Turn state
Completed
hcss_apiTRP 2488 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_oqN…
Turn sequence
3 of 29
Turn state
Completed
hcss_apiTRP 2305 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_g1O…
Turn sequence
4 of 29
Turn state
Completed
hcss_apiTRP 2489 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_j2v…
Turn sequence
5 of 29
Turn state
Completed
hcss_apiTRP 2369 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_W2R…
Turn sequence
6 of 29
Turn state
Completed
hcss_apiTRP 2193 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_44G…
Turn sequence
7 of 29
Turn state
Completed
hcss_apiTRP 2253 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_0mE…
Turn sequence
8 of 29
Turn state
Completed
hcss_apiTRP 2423 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_zBJ…
Turn sequence
9 of 29
Turn state
Completed
hcss_apiTRP 2179 msSep 30, 3:22 PM UTC
Outcome
Success
Thread
dfa4cc36…
Tool call
call_TEG…
Turn sequence
10 of 29
Turn state
Completed