An agent calls a flow that intermittently produces unexpected results during execution. The agent behaves inconsistently.
You need to investigate agent flow executions to diagnose the issue.
Which two actions should you use? Each correct answer presents a complete solution. Choose two. NOTE: Each correct selection is worth one point.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Flow run history provides the chronological record needed to identify which executions succeeded, failed, timed out, or behaved differently. Opening the failed run details then exposes the action-level inputs, outputs, status, duration, connection errors, and failure message that explain the inconsistent result. These two views support evidence-based diagnosis without changing the flow before the cause is known. Updating the trigger, increasing a timeout, or changing connection behavior are potential remediations only after the failure pattern has been established. The Analytics summary is useful for aggregate trends but lacks the full payload and step sequence of an individual run. The Activity tab's Error column can help locate failures, but the question asks for the two complete diagnostic actions and the detailed run inspection is the more direct evidence. Reviewers should compare a failed run with a successful run using the same input, check transient versus deterministic errors, and redact or restrict access to sensitive data captured in run history. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Monitor agent flows.
===============
Currently there are no comments in this discussion, be the first to comment!