Notifications
Clear all
Topic starter
20/08/2026 6:10 pm
TL;DR: Production failures cluster around retrieval noise, hallucinated tool calls, recursive loops, guardrail gaps, and schema drift, with traceability and trajectory-level evaluation emerging as the core operational fix, according to Arize field analysis of millions of agent decision paths. The central issue is not that agents are merely inaccurate, but that deterministic enterprise workflows now absorb probabilistic behaviour that can silently fail, misfire, or mask errors.
NHIMG editorial — based on content published by Arize: Why AI Agents Break: A Field Analysis of Production Failures
Questions worth separating out
Q: What breaks when AI agents rely on retrieval without chunk-level governance?
A: The system can retrieve the right document and still use the wrong fragment, which means the answer may look grounded while missing the actual instruction or policy.
Q: Why do AI agents cause identity and access concerns in production workflows?
A: Because once an agent can invoke tools, it is no longer just generating text.
Q: How do security teams know if agent policies are actually safe?
A: Look for static validation before deployment, explicit scope limits, pinned dependencies, and a clear owner for every policy file.
Practitioner guidance
- Implement span-level retrieval monitoring Measure which text chunks actually informed the agent's final action, not just which documents were retrieved into the context window.
- Trace every tool call before execution Capture raw payloads, resolved parameters, and response codes so teams can detect hallucinated fields, wrong object names, and empty-result masking.
- Add deterministic policy gates outside the model Block disallowed outputs and high-risk actions with a separate control layer that sits between agent reasoning and tool execution.
What's in the full article
Arize's full analysis covers the operational detail this post intentionally leaves for the source:
- Decision-path examples showing how each failure pattern appears in real agent traces
- Observed trace and telemetry patterns that distinguish hallucination from genuine backend failure
- Implementation-oriented guardrail and trajectory evaluation guidance for production teams
- Comparative examples of retrieval, tool-use, and long-session drift across agent workflows
👉 Read Arize's analysis of why AI agents break in production →
AI agent production failures: where observability and controls fail?
Explore further
20/08/2026 6:46 pm
AI agents are becoming non-human identities with behavioural risk, not just model risk. Once an agent can call tools, query systems, and act inside production workflows, it needs identity, privilege, and audit boundaries that traditional chatbot thinking does not provide. The real governance challenge is not the prompt, but the access path behind the prompt. Teams should treat agent runtime behaviour as part of the identity perimeter.
A question worth separating out:
Q: What should teams do when agent behaviour drifts during long sessions?
A: They should treat long-session drift as a control problem and reset the constraints that matter most near the point of action. Reassert task scope, identity boundaries, and safety rules before each sensitive operation, because earlier instructions can lose weight as the context grows.
👉 Read our full editorial: Why AI agents break in production and what that means
