Latency regression
load_office_document p95 slowed 524%
9.5 s now vs 1.5 s previously across 27 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
27
+93% vs previous 7d21 saved production turns
p50 latency
1.0 s
+2571% vs previous 7d27 timed calls
p95 latency
9.5 s
+524% vs previous 7d27 timed calls
Tool failures
29.6%
-56.1 pts vs previous 7d8 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
1.3
-17% 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 |
|---|---|---|---|---|---|
| load_office_document | 27+93% vs prior | 1.0 s+2571% vs prior | 9.5 s+524% vs prior | 29.6%-56.1 pts vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
NotFound8
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.
load_office_documentHJC679 msOct 6, 6:12 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_PLO…
Turn sequence
3 of 21
Turn state
Completed
load_office_documentHJC1.3 sOct 6, 6:08 PM UTC
Outcome
Success
Thread
50ac87df…
Tool call
call_ps1…
Turn sequence
10 of 28
Turn state
Completed
load_office_documentTRP 21.0 sOct 6, 1:58 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_Lq0…
Turn sequence
13 of 58
Turn state
Completed
load_office_documentTRP 2674 msOct 6, 1:59 PM UTC
Outcome
Success
Thread
09a6f0d4…
Tool call
call_ami…
Turn sequence
24 of 58
Turn state
Completed
load_office_documentTRP 2991 msOct 6, 12:22 PM UTC
Outcome
Success
Thread
d7e232c7…
Tool call
call_iqC…
Turn sequence
19 of 70
Turn state
Completed
load_office_documentHJC11 sOct 5, 11:07 PM UTC
Outcome
Success
Thread
c7640a45…
Tool call
chatcmpl…
Turn sequence
3 of 32
Turn state
Completed
load_office_documentHJC1.8 sOct 5, 8:49 PM UTC
Outcome
Success
Thread
5d45850a…
Tool call
chatcmpl…
Turn sequence
2 of 8
Turn state
Completed
load_office_documentHJC1.4 sOct 5, 8:38 PM UTC
Outcome
Success
Thread
bf677805…
Tool call
chatcmpl…
Turn sequence
8 of 20
Turn state
Completed
load_office_documentHJC101 msOct 5, 8:05 PM UTC
Outcome
NotFound
Thread
215345f3…
Tool call
chatcmpl…
Turn sequence
8 of 38
Turn state
Completed
load_office_documentHJC38 msOct 5, 8:05 PM UTC
Outcome
NotFound
Thread
215345f3…
Tool call
chatcmpl…
Turn sequence
9 of 38
Turn state
Completed
load_office_documentHJC32 msOct 5, 7:33 PM UTC
Outcome
NotFound
Thread
10f9fa7b…
Tool call
call_UIV…
Turn sequence
4 of 5
Turn state
Completed
load_office_documentRagle1.6 sOct 5, 4:19 PM UTC
Outcome
Success
Thread
a7a7a1cd…
Tool call
call_ZDW…
Turn sequence
6 of 14
Turn state
Completed
load_office_documentRagle49 msOct 5, 4:19 PM UTC
Outcome
NotFound
Thread
a7a7a1cd…
Tool call
call_7tk…
Turn sequence
10 of 14
Turn state
Completed
load_office_documentHJC40 msOct 5, 10:17 AM UTC
Outcome
NotFound
Thread
ca157012…
Tool call
chatcmpl…
Turn sequence
3 of 33
Turn state
Completed
load_office_documentHJC1.3 sOct 4, 6:53 PM UTC
Outcome
Success
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
14 of 16
Turn state
Completed
load_office_documentHJC38 msOct 4, 6:47 PM UTC
Outcome
NotFound
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
6 of 22
Turn state
Completed
load_office_documentHJC37 msOct 4, 6:47 PM UTC
Outcome
NotFound
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
7 of 22
Turn state
Completed
load_office_documentHJC658 msOct 2, 8:47 PM UTC
Outcome
Success
Thread
8d6df445…
Tool call
call_Lxq…
Turn sequence
2 of 7
Turn state
Completed
load_office_documentHJC3.1 sOct 2, 8:02 PM UTC
Outcome
Success
Thread
8d6df445…
Tool call
chatcmpl…
Turn sequence
14 of 19
Turn state
Completed
load_office_documentHJC1.3 sOct 2, 3:56 PM UTC
Outcome
Success
Thread
72a32790…
Tool call
chatcmpl…
Turn sequence
1 of 9
Turn state
Completed
load_office_documentHJC36 msOct 2, 3:49 PM UTC
Outcome
NotFound
Thread
72a32790…
Tool call
call_gw3…
Turn sequence
11 of 14
Turn state
Completed
load_office_documentHJC1.1 sOct 2, 2:06 PM UTC
Outcome
Success
Thread
b5b8e17f…
Tool call
chatcmpl…
Turn sequence
3 of 34
Turn state
Completed
load_office_documentHJC6.1 sOct 2, 2:09 PM UTC
Outcome
Success
Thread
b5b8e17f…
Tool call
chatcmpl…
Turn sequence
20 of 34
Turn state
Completed
load_office_documentHJC7.2 sOct 1, 7:06 PM UTC
Outcome
Success
Thread
b5b8e17f…
Tool call
chatcmpl…
Turn sequence
6 of 32
Turn state
Completed