MENU
A company uses an agent flow that calls a connector action. The flow sends an administrative notification if the action fails or times out
Administrators require the following configuration to help troubleshoot and manage failures:
* Handle failure and timeout outcomes explicitly.
* Continue execution after a failure is handled.
* Avoid retrying the failed action automatically.
You need to configure the agent flow so that failures are handled in a controlled and predictable way.
Which two actions should you perform? Each correct answer presents part of the solution. Choose two.
NOTE: Each correct selection is worth one point.
Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The connector action's retry policy should be set to None when the business requirement explicitly says not to retry automatically. Otherwise, platform retries can repeat a non-idempotent operation or delay the controlled failure path. The notification action must then use Configure run after so it executes when the connector action fails or times out and can include the available error details. This combination directly addresses the three requirements: explicit failure and timeout handling, continuation into the notification branch, and no automatic retry. A scope can be valuable for grouping a try block and evaluating its aggregate result, but grouping alone does not disable retries or define the notification's run-after conditions. Increasing the timeout changes how long the action waits and can make recovery slower without handling the error. The flow should also end with a deliberate final status, avoid exposing secrets in the notification, and distinguish transient dependency errors from validation failures. If the external operation is non-idempotent, a correlation or idempotency key should be used to prevent duplicate effects when an administrator later resubmits the run manually. Study Guide alignment: Plan and configure agent solutions > Create and monitor agent flows in Copilot Studio > Implement error handling in agent flows.
===============