A Copilot Studio topic calls an external REST API via an HTTP action. Occasionally the API returns a 503 (Service Unavailable) error. You want the agent to retry the call once before informing the user of a service outage. Which design approach achieves this?
Select an answer to reveal the explanation.
Short Explanation
Copilot Studio's native HTTP action doesn't give you a retry setting, so you wrap the call in a Power Automate flow with retry logic. The flow can retry once on a 503, then return success or failure so your topic can tell the user about the outage.
Full Explanation
Copilot Studio's HTTP action nodes provide basic request/response functionality but do not natively expose retry configuration properties. For resilient HTTP calls that should retry on transient failures, like 503 errors, the recommended pattern is to encapsulate the HTTP call in a Power Automate cloud flow. Power Automate has robust retry and error handling capabilities: you can set a retry policy on HTTP actions, including number of retries and retry interval, use Scope actions with 'Configure run after' settings to handle failures, or implement a Do-Until loop that retries a fixed number of times. The flow returns a status to the Copilot Studio topic indicating success or failure, and the topic branches accordingly. The approach that configures the HTTP action node's built-in retry count property to 1 is wrong because that property does not exist in Copilot Studio's HTTP action configuration as of current platform capabilities. The approach that adds a second identical HTTP action node after the first and connects it via a condition checking the error output is wrong because it's a one-time retry attempt, but it's brittle, hardcodes exactly one retry, clutters the canvas, and doesn't handle the error detection cleanly. The approach that enables the 'Auto-retry on failure' toggle in the agent's HTTP settings panel is wrong because this setting does not exist in Copilot Studio's agent HTTP settings. Design principle: complex HTTP orchestration, including retry, error handling, and conditional logic, belongs in a Power Automate flow. Simple one-and-done REST calls can use the native HTTP action. Use the right tool for the complexity level.