Agent loop pressure
More turns are using five or more tools
94.4% now vs 89.2% previously (17 turns).
Inspect the affected turn sequences for repeated or avoidable tool selection.
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
83
-60% vs previous 7d18 saved production turns
p50 latency
362 ms
Timing not instrumented68 timed calls
p95 latency
2.1 s
Timing not instrumented68 timed calls
Tool failures
7.2%
-3.8 pts vs previous 7d6 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
4.6
-18% vs previous 7d94.4% 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 1Aug 4Aug 7
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 |
|---|---|---|---|---|---|
| query_database_data | 83-60% vs prior | 362 msNo prior timing | 2.1 sNo prior timing | 7.2%-3.8 pts vs prior | 0.0%No change vs prior |
Failure codes
Operational failures only; NoResults is excluded.
InvalidArguments6
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.
query_database_dataHJC347 msAug 7, 2:34 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_4Rz…
Turn sequence
7 of 9
Turn state
Completed
query_database_dataBidlo1.6 sAug 6, 9:20 PM UTC
Outcome
Success
Thread
5a4e8ad2…
Tool call
call_goU…
Turn sequence
5 of 9
Turn state
Completed
query_database_dataBidlo247 msAug 6, 9:20 PM UTC
Outcome
Success
Thread
5a4e8ad2…
Tool call
call_xvd…
Turn sequence
6 of 9
Turn state
Completed
query_database_dataBidlo287 msAug 6, 9:21 PM UTC
Outcome
Success
Thread
5a4e8ad2…
Tool call
call_vWo…
Turn sequence
7 of 9
Turn state
Completed
query_database_dataBidlo155 msAug 6, 9:21 PM UTC
Outcome
Success
Thread
5a4e8ad2…
Tool call
call_5Im…
Turn sequence
8 of 9
Turn state
Completed
query_database_dataBidlo663 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_okF…
Turn sequence
6 of 19
Turn state
Completed
query_database_dataBidlo684 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_xmS…
Turn sequence
7 of 19
Turn state
Completed
query_database_dataBidlo505 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_zsZ…
Turn sequence
9 of 19
Turn state
Completed
query_database_dataBidlo540 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_BS2…
Turn sequence
10 of 19
Turn state
Completed
query_database_dataBidlo108 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_MvM…
Turn sequence
12 of 19
Turn state
Completed
query_database_dataBidlo436 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_Uao…
Turn sequence
13 of 19
Turn state
Completed
query_database_dataBidlo860 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_vGL…
Turn sequence
14 of 19
Turn state
Completed
query_database_dataBidlo636 msAug 6, 8:53 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_lhj…
Turn sequence
15 of 19
Turn state
Completed
query_database_dataBidlo168 msAug 6, 8:54 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_Kwj…
Turn sequence
16 of 19
Turn state
Completed
query_database_dataBidlo291 msAug 6, 8:54 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_nGr…
Turn sequence
17 of 19
Turn state
Completed
query_database_dataBidlo572 msAug 6, 8:54 PM UTC
Outcome
Success
Thread
21602129…
Tool call
call_Kj3…
Turn sequence
18 of 19
Turn state
Completed
query_database_dataHJCNot timedAug 6, 5:50 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_zXO…
Turn sequence
5 of 21
Turn state
Completed
query_database_dataHJCNot timedAug 6, 5:50 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_CH0…
Turn sequence
6 of 21
Turn state
Completed
query_database_dataHJCNot timedAug 6, 5:50 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_XFd…
Turn sequence
7 of 21
Turn state
Completed
query_database_dataHJCNot timedAug 6, 5:50 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_DlK…
Turn sequence
8 of 21
Turn state
Completed
query_database_dataHJCNot timedAug 6, 5:50 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_kEQ…
Turn sequence
9 of 21
Turn state
Completed
query_database_dataHJC283 msAug 6, 5:43 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_isc…
Turn sequence
10 of 39
Turn state
Completed
query_database_dataHJC514 msAug 6, 5:43 PM UTC
Outcome
Success
Thread
1c6b6c3e…
Tool call
call_oHa…
Turn sequence
11 of 39
Turn state
Completed
query_database_dataHJC182 msAug 6, 5:36 PM UTC
Outcome
Success
Thread
2d1997bc…
Tool call
call_lbV…
Turn sequence
20 of 27
Turn state
Completed