When an AI agent fails, its final response tells you what the user saw—not necessarily where the run went wrong. To diagnose a failure, connect the events and errors from the run to its execution trace, the code that handled it, and the versions active at the time. This four-part model is a practical debugging framework, not a formal standard or a guarantee that every failure can be explained from those artifacts alone.
Why an agent’s final answer is not a diagnosis
Agent workflows can involve long, probabilistic sequences of model calls, tool calls, state changes, and handoffs between agents. A visible failure at the end may have started several steps earlier, and a successful final response does not necessarily show whether the run took an unexpected route along the way. Microsoft Research describes this challenge in its [AgentRx framework](https://www.microsoft.com/en-us/research/blog/systematic-debugging-for-ai-agents-introducing-the-agentrx-framework/), which aims to locate the first critical failure step using evidence-backed constraints.
Logs, errors, code, and versions answer related but distinct questions: what happened, what failed, what behavior produced it, and which implementation was running. They work best alongside a trace that connects the steps in order. Google Cloud’s [agent observability guidance](https://docs.cloud.google.com/stackdriver/docs/observability/agent-observability) describes logs, metrics, and traces as complementary data for debugging failures, monitoring costs, and analyzing agent behavior.
What each part tells you
Logs: what happened?
Structured, timestamped events record actions such as a run starting or ending, a model call, a tool invocation and result, a retry, a state transition, or a handoff. Include a stable run or trace identifier so events from different services can be correlated. The [CNCF discussion of cloud-native agentic standards](https://www.cncf.io/blog/2026/03/23/cloud-native-agentic-standards/) emphasizes consistent structured data, a common time basis, and canonical logging. Free-form narrative messages alone are harder to search, compare, and correlate.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Errors: what failed?
Capture the exact exception or tool/API failure, the component that emitted it, relevant status codes, and whether a retry was attempted or considered appropriate. Preserve enough surrounding context to distinguish an upstream failure from a downstream symptom. Error aggregation can help make recurring failures visible: for example, Google Cloud’s Error Reporting analyzes Cloud Logging entries to group errors and show their history. That is a Google Cloud capability, not a property every logging platform provides.
Traces: how did execution unfold?
A trace organizes related work into a path of intermediate steps. For agent debugging, useful context can include prompts, model calls, tool invocations, and sub-agent hops; Microsoft Foundry’s [Build 2026 article](https://devblogs.microsoft.com/foundry/build-2026-from-observability-to-roi-for-ai-agents-on-any-framework/) describes tracing at this granularity. A trace can reveal where actual execution diverged from expectations, but it does not by itself establish which source revision or deployed artifact was responsible.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Code: what behavior produced the event?
Once the trace points to a component or step, inspect the relevant orchestration logic, prompt or configuration, tool schema, validation rules, and error handling. AgentRx illustrates one approach: express tool schemas and domain policies as executable constraints, then record violations step by step. Treat a suspected defect as an observed violation or a testable hypothesis until a reproduction or evaluation supports the diagnosis.
Versions: which implementation was active?
Record version context with the run where available: model identifier, prompt or configuration revision, agent and tool versions, dependency or container image version, and source commit or deployment identifier. This is a practical engineering recommendation, not a version schema mandated by the cited sources. Without it, a developer may inspect current code that differs from the implementation that produced the run’s evidence.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
A practical workflow for investigating a failed run
- Find and correlate the run. Start with its run or trace ID, then follow that identifier across the agent, tools, services, and queues involved. AWS recommends end-to-end tracing and unified views of traces, metrics, and logs for incident diagnosis in its [agent monitoring guidance](https://docs.aws.amazon.com/wellarchitected/latest/agentic-ai-lens/agentrel07.html).
- Read the trace chronologically. Mark the first unexpected observation instead of starting with the final user-visible error. The aim is to identify the earliest supported point where recovery failed, not to assume the last error caused everything before it.
- Compare actual tool behavior with its contract. Check inputs and outputs against the tool schema and relevant policy constraints. Preserve the specific evidence for each suspected violation.
- Match the run to its code and versions. Use the recorded deployment or commit context to inspect the implementation that was active. If version context is missing, note that limitation rather than treating today’s code as proof of what ran.
- Separate cause, symptom, and uncertainty. State what the trace directly shows, what you infer from it, and what remains unverified. Test a proposed fix against the failing case or representative evaluations. Databricks describes using production traces to create evaluation and golden datasets in its [agent observability and quality guide](https://learn.microsoft.com/en-us/azure/databricks/mlflow3/genai/agent-observability-and-quality).
- Check related runs. Look for recurrence, related errors, and changes in latency or token use. Google’s agent observability guidance treats logs, metrics, traces, token usage, latency, and error rates as complementary operational signals.
What to consider when choosing observability tooling
These are implementation criteria, not a ranking of vendors. Compare how well an approach:
- Traces model calls, tools, and sub-agent hops across service and asynchronous boundaries.
- Correlates logs, metrics, errors, and traces with shared identifiers.
- Captures prompts, responses, and tool payloads while supporting appropriate access controls.
- Attaches version and deployment metadata to runs.
- Lets teams turn incidents into repeatable evaluations.
- Exports data and supports interoperable conventions, including OpenTelemetry where relevant. Google recommends vendor-neutral OpenTelemetry instrumentation in its broader observability documentation; CNCF discusses common identifiers and semantic conventions.
- Fits the team’s retention, cost, and operational requirements.
What AgentRx’s results do—and do not—show
Microsoft Research reports that AgentRx was evaluated on 115 manually annotated failed trajectories across τ-bench, Flash, and Magentic-One. Against prompting baselines, the framework reported a 23.6% improvement in failure localization and a 22.9% improvement in root-cause attribution. These are results for one framework and benchmark, not general guarantees that any debugging setup will achieve the same improvements.
Quick Recap
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
