Agent loop pressure
More turns are using five or more tools
100.0% now vs — 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
6101 of 6166 saved tool calls include execution duration.
Tool calls
8
New activity vs previous 7d4 saved production turns
p50 latency
662 ms
Timing not instrumented8 timed calls
p95 latency
1.6 s
Timing not instrumented8 timed calls
Tool failures
37.5%
+37.5 pts vs previous 7d3 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
2.0
New activity 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 |
|---|---|---|---|---|---|
| update_map | 8No prior data | 662 msNo prior timing | 1.6 sNo prior timing | 37.5%No prior data | 0.0%No prior data |
Failure codes
Operational failures only; NoResults is excluded.
InvalidArguments3
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.
update_mapHJC662 msOct 6, 7:11 PM UTC
Outcome
Success
Thread
91821b64…
Tool call
chatcmpl…
Turn sequence
14 of 15
Turn state
Completed
update_mapHJC407 msOct 6, 7:11 PM UTC
Outcome
Success
Thread
91821b64…
Tool call
chatcmpl…
Turn sequence
15 of 15
Turn state
Completed
update_mapHJC902 msOct 6, 5:39 PM UTC
Outcome
InvalidArguments
Thread
eac20ce4…
Tool call
chatcmpl…
Turn sequence
14 of 17
Turn state
Completed
update_mapHJC789 msOct 6, 5:40 PM UTC
Outcome
Success
Thread
eac20ce4…
Tool call
chatcmpl…
Turn sequence
17 of 17
Turn state
Completed
update_mapHJC1.5 sOct 4, 8:50 PM UTC
Outcome
InvalidArguments
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
13 of 15
Turn state
Completed
update_mapHJC1.6 sOct 4, 8:50 PM UTC
Outcome
InvalidArguments
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
14 of 15
Turn state
Completed
update_mapHJC474 msOct 4, 8:50 PM UTC
Outcome
Success
Thread
913d4f54…
Tool call
chatcmpl…
Turn sequence
15 of 15
Turn state
Completed
update_mapHJC363 msOct 2, 8:00 PM UTC
Outcome
Success
Thread
c1a79eab…
Tool call
chatcmpl…
Turn sequence
27 of 28
Turn state
Completed