Reliability regression
read_file failures increased
5.7% now vs 1.2% previously across 35 calls; Unknown is the leading code.
Inspect recent failures, then check the tool handler and upstream dependency logs.
InvestigateBidlo Status Frontend
Chat tool telemetry
Find slow, failing, and repetitive agent tools without exposing prompts, arguments, or outputs.
Detailed production timing active
495 of 570 saved tool calls include execution duration.
Tool calls
35
-58% vs previous 7d16 saved production turns
p50 latency
1.7 s
Timing not instrumented33 timed calls
p95 latency
2.5 s
Timing not instrumented33 timed calls
Tool failures
5.7%
+4.5 pts vs previous 7d2 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
2.2
-21% vs previous 7d93.8% 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
Aug 2Aug 5Aug 8
Payload pressure
How often results exceed the 20 KB inline cap.
Unavailable
handle rows / all calls
The handle store could not be read with the current credentials.
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 |
|---|---|---|---|---|---|
| read_file | 35-58% vs prior | 1.7 sNo prior timing | 2.5 sNo prior timing | 5.7%+4.5 pts vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
Unknown2
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.
read_fileBidlo2.0 sAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_co8…
Turn sequence
1 of 19
Turn state
Completed
read_fileBidlo94 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_zel…
Turn sequence
2 of 19
Turn state
Completed
read_fileTRP Infrastructure Services, LLC1.9 sAug 6, 3:04 PM UTC
Outcome
Success
Thread
c395a2e5…
Tool call
call_ADY…
Turn sequence
1 of 7
Turn state
Completed
read_fileTRP Infrastructure Services, LLC70 msAug 6, 3:04 PM UTC
Outcome
Success
Thread
c395a2e5…
Tool call
call_11V…
Turn sequence
2 of 7
Turn state
Completed
read_fileTRP Infrastructure Services, LLC86 msAug 6, 3:04 PM UTC
Outcome
Success
Thread
c395a2e5…
Tool call
call_qBW…
Turn sequence
3 of 7
Turn state
Completed
read_fileBidlo2.5 sAug 6, 1:15 PM UTC
Outcome
Success
Thread
a4c6b869…
Tool call
call_mKO…
Turn sequence
1 of 18
Turn state
Completed
read_fileBidlo101 msAug 6, 1:15 PM UTC
Outcome
Success
Thread
a4c6b869…
Tool call
call_95j…
Turn sequence
2 of 18
Turn state
Completed
read_fileHJC247 msAug 5, 8:40 PM UTC
Outcome
Success
Thread
d02bb273…
Tool call
call_Gn8…
Turn sequence
1 of 6
Turn state
Completed
read_fileHJCNot timedAug 5, 8:18 PM UTC
Outcome
Success
Thread
d02bb273…
Tool call
call_ZuH…
Turn sequence
1 of 17
Turn state
Completed
read_fileHJCNot timedAug 5, 8:18 PM UTC
Outcome
Success
Thread
d02bb273…
Tool call
call_8A1…
Turn sequence
2 of 17
Turn state
Completed
read_fileHJC2.3 sAug 5, 2:09 PM UTC
Outcome
Success
Thread
4c56afbc…
Tool call
call_WCk…
Turn sequence
1 of 11
Turn state
Completed
read_fileHJC113 msAug 5, 2:09 PM UTC
Outcome
Success
Thread
4c56afbc…
Tool call
call_yVi…
Turn sequence
2 of 11
Turn state
Completed
read_fileHJC2.5 sAug 5, 9:57 AM UTC
Outcome
Success
Thread
044f7884…
Tool call
call_fLC…
Turn sequence
1 of 18
Turn state
Completed
read_fileHJC70 msAug 5, 9:57 AM UTC
Outcome
Success
Thread
044f7884…
Tool call
call_GrF…
Turn sequence
2 of 18
Turn state
Completed
read_fileHJC100 msAug 5, 10:00 AM UTC
Outcome
Success
Thread
044f7884…
Tool call
call_Kon…
Turn sequence
8 of 18
Turn state
Completed
read_fileHJC2.1 sAug 4, 4:52 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_Qky…
Turn sequence
1 of 30
Turn state
Completed
read_fileHJC85 msAug 4, 4:52 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_Gv1…
Turn sequence
3 of 30
Turn state
Completed
read_fileHJC126 msAug 4, 4:52 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_d7N…
Turn sequence
4 of 30
Turn state
Completed
read_fileTexas Materials1.9 sAug 3, 6:42 PM UTC
Outcome
Success
Thread
6ef49cff…
Tool call
call_uYx…
Turn sequence
3 of 6
Turn state
Completed
read_fileTexas Materials1.9 sAug 3, 5:33 PM UTC
Outcome
Success
Thread
1765bb64…
Tool call
call_t8F…
Turn sequence
1 of 20
Turn state
Completed
read_fileHJC1.9 sAug 3, 5:17 PM UTC
Outcome
Unknown
Thread
813d04aa…
Tool call
call_7o0…
Turn sequence
1 of 14
Turn state
Completed
read_fileHJC100 msAug 3, 5:17 PM UTC
Outcome
Unknown
Thread
813d04aa…
Tool call
call_ilF…
Turn sequence
4 of 14
Turn state
Completed
read_fileHJC148 msAug 3, 5:17 PM UTC
Outcome
Success
Thread
813d04aa…
Tool call
call_CdI…
Turn sequence
5 of 14
Turn state
Completed
read_fileHJC236 msAug 3, 5:20 PM UTC
Outcome
Success
Thread
813d04aa…
Tool call
call_OBt…
Turn sequence
13 of 14
Turn state
Completed