Latency regression
create_app p95 slowed 118%
8.4 s now vs 3.8 s previously across 8 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
8
+167% vs previous 7d8 saved production turns
p50 latency
3.1 s
-16% vs previous 7d8 timed calls
p95 latency
8.4 s
+118% vs previous 7d8 timed calls
Tool failures
0.0%
No change vs previous 7d0 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
1.0
No change vs previous 7d100.0% 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 |
|---|---|---|---|---|---|
| create_app | 8+167% vs prior | 3.1 s-16% vs prior | 8.4 s+118% vs prior | 0.0%No change 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.
create_appHJC2.8 sOct 6, 7:07 PM UTC
Outcome
Success
Thread
dae0a154…
Tool call
call_cuU…
Turn sequence
1 of 36
Turn state
Completed
create_appBidlo2.7 sOct 6, 3:47 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_OUu…
Turn sequence
3 of 48
Turn state
Completed
create_appHJC3.1 sOct 6, 3:16 PM UTC
Outcome
Success
Thread
1a4e54dc…
Tool call
chatcmpl…
Turn sequence
2 of 15
Turn state
Completed
create_appHJC2.8 sOct 5, 7:14 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
chatcmpl…
Turn sequence
4 of 36
Turn state
Completed
create_appHJC3.5 sOct 4, 4:33 PM UTC
Outcome
Success
Thread
e1179f50…
Tool call
call_NQu…
Turn sequence
3 of 54
Turn state
Completed
create_appBidlo3.1 sOct 4, 5:29 AM UTC
Outcome
Success
Thread
3ed32d55…
Tool call
call_kw9…
Turn sequence
2 of 29
Turn state
Completed
create_appBidlo8.4 sOct 2, 5:24 PM UTC
Outcome
Success
Thread
d5678187…
Tool call
call_OaF…
Turn sequence
1 of 15
Turn state
Completed
create_appBidlo4.0 sOct 2, 5:19 PM UTC
Outcome
Success
Thread
f319d57c…
Tool call
call_JhW…
Turn sequence
1 of 19
Turn state
Completed