Agent loop pressure
More turns are using five or more tools
100.0% now vs 81.8% previously (4 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
5
-64% vs previous 7d4 saved production turns
p50 latency
527 ms
Timing not instrumented5 timed calls
p95 latency
15 s
Timing not instrumented5 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.3
-2% 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
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 |
|---|---|---|---|---|---|
| create_database_view | 5-64% vs prior | 527 msNo prior timing | 15 sNo prior timing | 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_database_viewHJC524 msAug 7, 2:34 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_7RW…
Turn sequence
8 of 9
Turn state
Completed
create_database_viewHJC539 msAug 4, 4:52 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_e1i…
Turn sequence
15 of 30
Turn state
Completed
create_database_viewHJC527 msAug 4, 4:53 PM UTC
Outcome
Success
Thread
c1ea98f7…
Tool call
call_xA0…
Turn sequence
30 of 30
Turn state
Completed
create_database_viewHJC449 msAug 3, 3:59 PM UTC
Outcome
Success
Thread
562421d5…
Tool call
call_jXO…
Turn sequence
15 of 17
Turn state
Completed
create_database_viewHJC15 sAug 3, 3:49 PM UTC
Outcome
Success
Thread
f5d38ce1…
Tool call
call_Dra…
Turn sequence
7 of 7
Turn state
Completed