An agent uses a flow that calls an external service which can occasionally fail or...

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Configure run after is the control that routes execution to an error-handling action when the external-service action fails, times out, is skipped, or reaches another selected status. By configuring the notification action to run after failure and timeout, the flow no longer terminates silently and can send a message containing sanitized error context. The handler can then set a deliberate flow status, record a correlation ID, and provide the operator with the failed action and remediation path. This design should be paired with an appropriate retry policy based on whether the external operation is safe to repeat. For non-idempotent writes, automatic retry may create duplicates and should generally be disabled or protected with an idempotency key. Error notifications must not include tokens, secrets, or unrestricted payloads. Testing should deliberately produce an authorization failure, timeout, and service error to prove that each status enters the handler and that the notification itself has a fallback if its connector is unavailable. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.

===============