Study guide
10.4 Error Handling, Configure Run After & Scope Controls
Microsoft Power Platform Functional Consultant PL-200
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Dataverse Tables, Relationships & Core Columns
1.1 Dataverse Table Types, Properties & Ownership 1.2 Table Relationships & Cascading Rules 1.3 Column Types, Formats, Primary Keys & Alternate Keys 1.4 Rollup, Calculated & Formula Columns with Power Fx
2 Chapter 2: Dataverse Data Management & Governance
2.1 Dataverse Search, Quick Find & Relevance Indexing 2.2 Auditing Configuration & Log Management 2.3 Duplicate Detection Rules & Settings 2.4 Bulk Record Operations, Data Import, Export & Templates
3 Chapter 3: Dataverse Security Model & Access Control
3.1 Business Units, Ownership Models & Modern BU Matrix 3.2 Security Roles, Privileges & Depth Levels 3.3 Teams Architecture: Owner, Access, and Microsoft Entra (AAD) Group Teams 3.4 Column-Level Security & Hierarchy Security Models
4 Chapter 4: Model-Driven App Fundamentals & Information Architecture
4.1 Model-Driven App Design, Site Map Navigation & Modern App Designer 4.2 Form Types: Main, Quick Create, Quick View & Card Forms 4.3 View Configuration, System Views, Personal Views & Filters
5 Chapter 5: Advanced Model-Driven App Components & Custom Pages
5.1 Custom Pages & Modern Commanding with Power Fx 5.2 Form Component Controls & Specialized UX Elements 5.3 Embedding Canvas Apps in Model-Driven Forms 5.4 Embedding Power BI Reports, Dashboards & Tiles
6 Chapter 6: Canvas Apps Structure, Formulas & Data Operations
6.1 Canvas App Architecture, Screens, Containers & Controls 6.2 Power Fx Formulas, Delegation & Data Source Limits 6.3 Variables (Context, Global), Collections & State Management 6.4 Triggering Power Automate Cloud Flows from Canvas Apps
7 Chapter 7: Power Pages Site Design, Navigation & Content
7.1 Power Pages Design Studio & Site Structure 7.2 Power Pages Templates, Styling & Responsive Layouts 7.3 Web Pages, Navigation Menus & Content Snippets
8 Chapter 8: Power Pages Data Integration, Forms & Web Roles
8.1 Power Pages Lists, Basic Forms & Advanced Forms 8.2 Table Permissions, Web Roles & Page Access Security 8.3 External Identity Providers & Authentication Configuration
9 Chapter 9: Power Automate Cloud Flow Fundamentals & Triggers
9.1 Cloud Flow Types: Automated, Instant, Scheduled & Desktop Overview 9.2 Dataverse Connector Triggers & Operational Filters 9.3 Standard Connectors, Custom Connectors & Connection References
10 Chapter 10: Cloud Flow Actions, Expressions & Logic Controls
10.1 Logic Controls: Conditions, Switches, Apply to Each & Do Until Loops 10.2 Variables, Data Operations & Dynamic Content Manipulation 10.3 Power Automate Expression Language (WDL / Functions) 10.4 Error Handling, Configure Run After & Scope Controls
11 Chapter 11: Business Process Flows & Guided Processes
11.1 Business Process Flow Architecture, Stages, Steps & Data Steps 11.2 Branching Rules & Multi-Entity Business Process Flows 11.3 BPF Action Steps, Workflows & Cloud Flow Execution 11.4 BPF Security Roles, Order & Process Lifecycle
12 Chapter 12: Classic Workflows, Business Rules & Modern Logic Extensibility
12.1 Classic Dataverse Workflows: Real-Time vs. Background (Async) 12.2 Business Rules: Scope & Actions 12.3 Low-Code Plug-ins in Dataverse: Automated vs. Instant 12.4 Troubleshooting Automations, Run History & Analytics
13 Chapter 13: Power Platform Environment Architecture & Security
13.1 Environment Types: Default, Sandbox, Production, Trial, Developer 13.2 Environment Governance, Groups, Routing & Capacity Management 13.3 Data Loss Prevention (DLP) Policies & Connector Classifications
14 Chapter 14: Application Lifecycle Management (ALM) & Solutions
14.1 Unmanaged vs. Managed Solutions & Solution Layering Mechanics 14.2 Solution Components, Dependencies, Publishers & Prefixes 14.3 Exporting, Importing, Upgrading & Patches 14.4 Solution Checker, App Checker & ALM Best Practices
15 Chapter 15: Enterprise Interoperability & Service Integration
15.1 Exchange / Server-Side Synchronization & Email Integration 15.2 SharePoint & OneDrive Document Management Integration 15.3 Microsoft Word & Excel Document Templates
16 Chapter 16: Copilot, AI Capabilities & Exam Strategy
16.1 Copilot Studio & Generative AI across Power Platform 16.2 AI Builder Prebuilt & Custom Models in Apps and Flows 16.3 PL-200 Exam Strategy, Time Management & Question Analysis
10.4 Error Handling, Configure Run After & Scope Controls
Key Takeaways Explain This Topic AI
By default, Power Automate actions execute only when the immediately preceding action 'is successful' (Succeeded); if an action fails, subsequent actions are skipped and the flow fails.
'Configure Run After' settings allow actions to run based on four execution states: is successful, has failed, is skipped, and has timed out.
The enterprise Try-Catch-Finally pattern groups critical logic into a 'Try' Scope, error logging and alerts into a 'Catch' Scope (run after Try has failed/timed out/is skipped), and cleanup actions into a 'Finally' Scope (run after Catch regardless of result).
The Terminate action halts flow execution with a status of Succeeded, Cancelled, or Failed; specifying a custom Error Code and Message inside a Catch block ensures failed runs are accurately reported in telemetry.
Action retry policies can be customized between Default (exponential backoff), Fixed interval, Exponential interval, and None (essential for non-idempotent transactional actions).
Last updated: August 2026
Error Handling, Configure Run After & Scope Controls
In mission-critical enterprise environments, automated cloud flows must be resilient to external system outages, network timeouts, invalid payloads, and transient API rate limits. Without explicit error handling, a single action failure causes all downstream actions to be skipped, leaving transactions half-completed, records orphaned in locked states, and support teams unaware of system disruptions.
For the PL-200: Microsoft Power Platform Functional Consultant exam, you must master the mechanics of Configure Run After , implement the industry-standard Scope-based Try-Catch-Finally pattern , configure action Retry Policies and Timeouts , and utilize the Terminate action to ensure accurate operational telemetry.
1. Flow Execution State Machine & Status Codes
Every action executed by the Power Automate workflow runtime concludes in one of four discrete execution states: +-----------------------------------------------------------------------------+
- | ACTION EXECUTION STATUS STATES |
- | |
- | [SUCCEEDED] ---> Action completed successfully with HTTP 2xx or valid ops|
- | |
- | [FAILED] ---> Action threw an unhandled error, HTTP 4xx/5xx, or crash |
- | |
- | [SKIPPED] ---> Action was bypassed because predecessor failed/skipped |
- | |
- | [TIMED OUT] ---> Action exceeded configured timeout or gateway limit |
- +-----------------------------------------------------------------------------+
- The Default Flow Execution Behavior
By default, every action is configured to run only if the preceding action is successful ( Succeeded ) .
If Action 1 succeeds, Action 2 executes.
If Action 2 fails, the engine immediately halts the sequential pipeline: Action 3 and Action 4 are marked as Skipped , and the overall flow run status is recorded as Failed .
2. Configure Run After Mechanics
The Configure Run After setting allows makers to alter the default execution dependency of any action. By accessing an action's ellipsis menu ( ... ) > Configure run after , you can select which status outcomes of the preceding action will trigger the current action. +-----------------------------------------------------------------------------+
- | CONFIGURE RUN AFTER SELECTION GRID |
- | |
- | Run 'Notify_DevOps_On_Failure' after 'Execute_Payment_Gateway' : |
- | |
- | [ ] is successful (Predecessor returned Succeeded) |
- | [X] has failed (Predecessor threw error / HTTP 4xx/5xx) |
- | [X] is skipped (Predecessor was bypassed due to upstream fault) |
- | [X] has timed out (Predecessor exceeded max duration limit) |
- +-----------------------------------------------------------------------------+
- The Four Run After Conditions
is successful : Executes when the predecessor action finishes with status Succeeded . (Default setting).
has failed : Executes when the predecessor action encounters any operational failure (e.g., Dataverse record not found, REST API 500 error, division by zero).
is skipped : Executes when the predecessor action was not executed because an upstream step failed or a conditional branch was not taken.
has timed out : Executes when the predecessor action exceeds its maximum execution duration (e.g., an HTTP webhook listener that received no response within its timeout window).
3. The Scope Control & Try-Catch-Finally Pattern
Configuring run-after settings on individual individual actions across a 30-step flow is unmaintainable. The enterprise best practice is the Scope-based Try-Catch-Finally pattern .
A Scope is an organizational container that groups multiple actions. The Scope itself reports a collective status: if all actions inside the Scope succeed, the Scope status is Succeeded ; if any action inside the Scope fails, the Scope status immediately becomes Failed . +-----------------------------------------------------------------------------+
- | ENTERPRISE TRY-CATCH-FINALLY ARCHITECTURE |
- | |
- | +---------------------------------------------------------------------+ |
- | | SCOPE: Scope - Try | |
- | | - Action 1: Query ERP System (HTTP GET) | |
- | | - Action 2: Transform Data with Data Operations | |
- | | - Action 3: Update Dataverse Master Record | |
- | +---------------------------------------------------------------------+ |
- | | |
- | Configure Run After: has failed / is skipped / timed out |
- | v |
- | +---------------------------------------------------------------------+ |
- | | SCOPE: Scope - Catch | |
- | | - Action 1: Send High-Priority Teams / Email Alert to DevOps | |
- | | - Action 2: Create Incident Row in Dataverse Issue Table | |
- | | - Action 3: Terminate (Status: Failed, Code: 'ERP-500', Message: ..)| |
- | +---------------------------------------------------------------------+ |
- | | |
- | Configure Run After: is successful / has failed / |
- | is skipped / has timed out |
- | v |
- | +---------------------------------------------------------------------+ |
- | | SCOPE: Scope - Finally | |
- | | - Action 1: Unlock Dataverse Record (Clear Processing Lock Flag) | |
- | | - Action 2: Write Execution Audit Log Record | |
- | +---------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------+
- Implementing the Pattern Step-by-Step
Create Scope - Try : Place all core business logic actions inside this scope. Leave its run-after settings as default ( is successful ).
Create Scope - Catch : Place error notification, logging, and rollback actions inside this scope. Open its Configure run after settings and check has failed , is skipped , and has timed out (unchecking is successful ).
Create Scope - Finally : Place cleanup actions (unlocking resources, logging audit entries) inside this scope. Open its Configure run after settings and check all four boxes : is successful , has failed , is skipped , and has timed out . This guarantees Scope - Finally executes under every possible scenario.
Extracting Detailed Error Payloads: result()
To extract the exact error message and failing step name from Scope - Try , use the result('Scope_Try') WDL expression. This returns an array containing the execution output of every action inside the Try scope. You can pass this array into a Filter array action where item()?['status'] is equal to 'Failed' to isolate the exact error details.
4. The Terminate Action & Run History Accuracy
The Terminate action immediately halts the entire flow execution run. It is critical for managing the overall flow run status displayed in Power Automate run history and administrative analytics. +-----------------------------------------------------------------------------+
- | TERMINATE ACTION STATUS MODES |
- | |
- | [SUCCEEDED] ---> Halts flow immediately; marks overall run as Succeeded |
- | (Used for early-exit business logic where no work needed|
- | |
- | [CANCELLED] ---> Halts flow immediately; marks overall run as Cancelled |
- | (Used when process is aborted due to external state) |
- | |
- | [FAILED] ---> Halts flow immediately; marks overall run as Failed |
- | Exposes mandatory: 'Code' (e.g., ERR-402) and |
- | 'Message' (e.g., 'Payment processor declined card') |
- +-----------------------------------------------------------------------------+
Caution
The 'Catch Scope False Positive' Trap on PL-200: When an error occurs in Scope - Try , execution routes into Scope - Catch . If the actions inside Scope - Catch (such as sending an email) execute successfully, Power Automate considers the final step of the flow Succeeded . As a result, the overall flow run will be marked as 'Succeeded' in run history , masking the underlying failure from administrators! To prevent this false positive, always place a Terminate action configured with Status = Failed as the final step of the Catch block or after Finally.
5. Action Retry Policies & Timeout Configuration
In addition to flow-level branching, individual actions provide settings to handle transient network faults and enforce duration limits. +-----------------------------------------------------------------------------+
- | ACTION RETRY POLICY SETTINGS |
- | |
- | [DEFAULT (EXPONENTIAL)] ---> 4 retries with exponential backoff delays |
- | [FIXED INTERVAL] ---> Specific retry count at fixed delay (e.g. 5s|
- | [EXPONENTIAL INTERVAL] ---> Specific retry count with min/max intervals|
- | [NONE] ---> Zero retries; fails immediately on error |
- | (MANDATORY for non-idempotent payments) |
- +-----------------------------------------------------------------------------+
- Retry Policy Configurations
In any action's Settings > Retry Policy , makers can choose:
Default: Automatically performs 4 retries using an exponential backoff algorithm.
None: Disables retries entirely. Fails immediately upon the first error. Critical rule: Use None for non-idempotent operations (such as credit card charges or non-reversible ERP postings) to prevent accidental duplicate transactions.
Fixed Interval: Retries a specified number of times (e.g., 3) with a static delay between attempts (e.g., PT10S ).
Exponential Interval: Retries a specified number of times with randomized exponential backoff between a configured minimum and maximum duration.
Action Timeout Configuration
By default, asynchronous cloud flow actions wait up to 30 days ( P30D ) for a callback or completion. In an action's Settings > Timeout , makers can define an ISO 8601 duration string (e.g., PT2M for 2 minutes, PT30S for 30 seconds). If the action does not complete within this window, it terminates with status TimedOut , allowing downstream Configure Run After branches to catch the timeout.