Explanation:
Capture response # Use the action ' s response outputs in later steps; Continue the same run # Allow the action to wait for and return a response before continuing; Require a manual decision # Add a human approval action.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: A human-in-the-loop flow must preserve execution state while it waits. The approval or information action pauses the current run and returns a response when the designated person acts; triggering a new flow would lose that direct continuation contract. The response outputs-decision, comments, supplied fields, responder, and timestamps as applicable-are then referenced by downstream conditions and actions. A human approval action provides the explicit decision gate required before processing continues. Sending a notification or message alone does not wait and cannot guarantee that the decision controls the flow. The designer should configure expiration, escalation, reassignment, and rejection paths so the run cannot remain suspended without governance.
Responses should be validated before use, and sensitive values should be protected in variables and history.
Test approval, rejection, timeout, duplicate response, and unauthorized response scenarios. These controls ensure that human oversight changes execution deterministically instead of acting as an informational side channel. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Create a human-in-the-loop agent flow.