Agent loop pressure
More turns are using five or more tools
64.5% now vs — previously (20 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
40
New activity vs previous 7d31 saved production turns
p50 latency
144 ms
Timing not instrumented40 timed calls
p95 latency
190 ms
Timing not instrumented40 timed calls
Tool failures
2.5%
+2.5 pts vs previous 7d1 excluding NoResults
No result
0.0%
No change vs previous 7d0 product outcomes
Calls / turn
1.3
New activity vs previous 7d64.5% 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_run | 40No prior data | 144 msNo prior timing | 190 msNo prior timing | 2.5%No prior data | 0.0%No prior data |
Failure codes
Operational failures only; NoResults is excluded.
Unknown1
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_runHJC170 msOct 6, 8:24 PM UTC
Outcome
Success
Thread
ed7becf5…
Tool call
call_XIZ…
Turn sequence
1 of 1
Turn state
Completed
get_flow_runHJC162 msOct 6, 8:01 PM UTC
Outcome
Success
Thread
ed7becf5…
Tool call
call_O0t…
Turn sequence
1 of 27
Turn state
Completed
get_flow_runBidlo76 msOct 6, 4:54 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_dVE…
Turn sequence
1 of 5
Turn state
Completed
get_flow_runBidlo151 msOct 6, 4:29 PM UTC
Outcome
Success
Thread
20a1bcaf…
Tool call
call_e7N…
Turn sequence
1 of 8
Turn state
Completed
get_flow_runHJC142 msOct 5, 11:49 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_bUN…
Turn sequence
1 of 10
Turn state
Completed
get_flow_runHJC141 msOct 5, 11:44 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_xLt…
Turn sequence
1 of 3
Turn state
Completed
get_flow_runHJC156 msOct 5, 11:34 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_ztx…
Turn sequence
3 of 34
Turn state
Completed
get_flow_runHJC80 msOct 5, 11:37 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_EAD…
Turn sequence
25 of 34
Turn state
Completed
get_flow_runHJC150 msOct 5, 11:24 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_Qzm…
Turn sequence
1 of 3
Turn state
Completed
get_flow_runHJC153 msOct 5, 10:48 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_1oj…
Turn sequence
8 of 12
Turn state
Completed
get_flow_runHJC168 msOct 5, 9:52 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_Wbp…
Turn sequence
1 of 26
Turn state
Completed
get_flow_runHJC190 msOct 5, 9:47 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_icv…
Turn sequence
1 of 6
Turn state
Completed
get_flow_runHJC70 msOct 5, 9:43 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_pfD…
Turn sequence
1 of 3
Turn state
Completed
get_flow_runHJC149 msOct 5, 9:40 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_zXp…
Turn sequence
15 of 24
Turn state
Completed
get_flow_runHJC145 msOct 5, 9:40 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_HkY…
Turn sequence
16 of 24
Turn state
Completed
get_flow_runHJC134 msOct 5, 9:40 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_9lX…
Turn sequence
17 of 24
Turn state
Completed
get_flow_runHJC138 msOct 5, 9:40 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_b22…
Turn sequence
18 of 24
Turn state
Completed
get_flow_runHJC144 msOct 5, 9:32 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_0zw…
Turn sequence
13 of 14
Turn state
Completed
get_flow_runHJC142 msOct 5, 9:32 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_0zB…
Turn sequence
14 of 14
Turn state
Completed
get_flow_runHJC153 msOct 5, 8:21 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_SOD…
Turn sequence
3 of 9
Turn state
Completed
get_flow_runHJC141 msOct 5, 8:14 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_wEM…
Turn sequence
1 of 22
Turn state
Completed
get_flow_runHJC138 msOct 5, 8:14 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_jWq…
Turn sequence
3 of 22
Turn state
Completed
get_flow_runHJC69 msOct 5, 8:15 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_GvZ…
Turn sequence
10 of 22
Turn state
Completed
get_flow_runHJC131 msOct 5, 8:11 PM UTC
Outcome
Success
Thread
8baa70ed…
Tool call
call_POI…
Turn sequence
2 of 28
Turn state
Completed