Agent loop pressure
More turns are using five or more tools
100.0% now vs — previously (5 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
6
New activity vs previous 7d5 saved production turns
p50 latency
221 ms
Timing not instrumented6 timed calls
p95 latency
263 ms
Timing not instrumented6 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.2
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 |
|---|---|---|---|---|---|
| get_flow_runs | 6No prior data | 221 msNo prior timing | 263 msNo prior timing | 0.0%No prior data | 0.0%No prior data |
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.
get_flow_runsHJC263 msOct 5, 10:48 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_rem…
Turn sequence
4 of 12
Turn state
Completed
get_flow_runsHJC147 msOct 5, 9:32 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_5Ck…
Turn sequence
9 of 14
Turn state
Completed
get_flow_runsTRP 2234 msOct 1, 5:15 AM UTC
Outcome
Success
Thread
a4ef58fe…
Tool call
call_ROc…
Turn sequence
2 of 5
Turn state
Completed
get_flow_runsTRP 2230 msOct 1, 4:51 AM UTC
Outcome
Success
Thread
a4ef58fe…
Tool call
call_rb4…
Turn sequence
2 of 7
Turn state
Completed
get_flow_runsTRP 2221 msOct 1, 1:18 AM UTC
Outcome
Success
Thread
a4ef58fe…
Tool call
call_P60…
Turn sequence
2 of 6
Turn state
Completed
get_flow_runsTRP 2162 msOct 1, 1:18 AM UTC
Outcome
Success
Thread
a4ef58fe…
Tool call
call_MRL…
Turn sequence
3 of 6
Turn state
Completed