Active incident

support-agent/refund is the likely broken agent

Refund ranker release pulled full CRM context into the prompt, then retries amplified cost and latency.

Inspect suspect span

Open failures

3

Across 3 agents

Retry waste

$0.181

83% of suspect run cost

P95 latency

15.0s

3x over guardrail

Next span

span_5

ContextLengthExceeded

Local sources

Demo mode uses seeded Paperclip-shaped data. Optional connectors do not block incident review.

TRACEIQ_DATA_MODE=demo

Paperclip

demo

Seeded Paperclip-shaped demo data is active.

Hermes

offline

Connector pending. Set HERMES_API_URL for future live runtime events.

Ironclaw

offline

Connector pending. Set IRONCLAW_API_URL for future policy signals.

TraceIQ ingest

demo

Local API is the normalization boundary for future connectors.

24h run health

Volume, errors, median cost, p95 latency
98 risk scoretr_i9j0k1l2

Start here: support-agent/refund

Refund ranker pulled the full CRM export after the release, causing context errors and retries.

Cost

$0.531

Latency

21.6s

Tokens

17,696

Evidence 1

Release traceiq-refund-ranker-2026-05-23.1 preceded the failure cluster

Evidence 2

CRM tool returned 847 rows

Evidence 3

Healthy comparison trace stayed under the token guardrail

Runs ranked by suspicion

Open trace queue
RiskAgentLikely causeReleaseDeltaCostLatencyNext
99support-agent/refundContextLengthExceeded: prompt exceeds 16,384 token limit at Generate Win/Loss Analysistraceiq-refund-ranker-2026-05-23.1+218% / +184%$0.53121.6sspan_7
94report-generatorContextLengthExceeded: notes payload exceeded model limit at Generate save-plan sectionn/an/a / n/a$0.24711.4sspan_5
57contract-summarizerLatency exceeded guardrail around Generate final summaryn/an/a / n/a$0.11214.5sspan_4
49onboarding-flowToolTimeoutError: profile API exceeded 5s timeout at Fetch profilen/an/a / n/a$0.0075.9sspan_1
46search-agentLatency exceeded guardrail around Rank competitorsn/an/a / n/a$0.08910.0sspan_4