Scopes group related work so the next action can respond to a final result. A failed intermediate attempt does not immediately require Catch if the retry policy can still recover it. Configure run after against the final scope status, then inspect the failed attempt and successful retry separately.
A Try scope that succeeds causes a failure-only Catch to be skipped. A later audit must accept both Succeeded and Skipped from Catch if it must run on both outcomes. A Catch failure should not silently count as a completed recovery. Keep the support alert and audit separate from the business result.
The exercises include transient recovery, exhausted retries and permission errors that must not retry. Your work must preserve the original failure evidence while providing a specific next action for the operator.
Catch runs only after the final failed result, including exhausted retries. A successful Try skips Catch, so the audit explicitly accepts Skipped as well as Succeeded. Recovery success proves the alert was sent; it does not prove the enterprise read succeeded.