Study guide
12.4 Troubleshooting Automations, Run History & Analytics
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
12.4 Troubleshooting Automations, Run History & Analytics
Key Takeaways Explain This Topic AI
Power Automate Cloud Flow execution history is retained for exactly 28 days, enabling makers to inspect action inputs, outputs, error codes, and execution durations.
Failed flow runs can be resubmitted directly from the Run History, utilizing the exact original trigger payload or after editing the flow definition to fix structural defects.
Flow testing supports two distinct modes: Manual triggering (awaiting a live event) and Using Recently Used Triggers (replaying historical payloads without duplicating upstream data).
Power Platform Admin Center (PPAC) provides centralized analytics across environments, tracking cloud flow usage, failure rates, maker trends, and throttling bottlenecks.
Classic background workflows and asynchronous jobs are monitored via the System Jobs (asyncoperation) view, while plug-in and low-code plug-in execution traces are captured in the Plug-in Trace Log.
Last updated: August 2026
Troubleshooting Automations, Run History & Analytics
Designing and deploying automations is only half the responsibility of a Power Platform Functional Consultant. In production environments, automations encounter intermittent service outages, data schema mismatches, API rate limits, and concurrency conflicts. To ensure business continuity and meet enterprise service-level agreements (SLAs), consultants must master the diagnostic toolset across Power Automate Run History , Power Platform Admin Center (PPAC) Analytics , Dataverse System Jobs , and Plug-in Trace Logs .
1. Cloud Flow Run History & Action Inspection
Whenever an automated, instant, or scheduled cloud flow executes, Power Automate captures detailed execution metadata in the flow's Run History . +-----------------------------------------------------------------------------------+
- | CLOUD FLOW RUN HISTORY VIEWER |
- | |
- | [RUN HISTORY RETENTION: EXACTLY 28 DAYS] |
- | |
- | Start Time Duration Status Trigger Outputs |
- | 2026-08-17 10:14 1.2s Succeeded { id: "acc-101", name: "Contoso" } |
- | 2026-08-17 10:12 0.8s Failed { id: "acc-102", name: "Fabrikam" } |
- | 2026-08-17 09:55 -- Running { id: "acc-103", name: "Litware" } |
- | |
- | +-----------------------------------------------------------------------------+ |
- | | CLICKING A RUN OPENS THE STEP-BY-STEP DIAGNOSTIC VIEWER: | |
- | | | |
- | | [✓] When a row is added (Dataverse Trigger) ..................... 120ms | |
- | | [✓] Get Customer Profile (Dataverse Action) ..................... 240ms | |
- | | [✕] Post Invoice to SAP (HTTP REST Action) ...................... 450ms | |
- | | * Status Code: 400 Bad Request | |
- | | * Inputs: { "TaxID": null, "Amount": 4500.00 } | |
- | | * Error Message: "TaxID is a required field for EU customers." | |
- | +-----------------------------------------------------------------------------+ |
- +-----------------------------------------------------------------------------------+
- Key Run History Diagnostics
28-Day Retention Limit: Run history logs are retained for 28 days . After 28 days, execution history is purged automatically by the platform.
Status Identifiers:
Succeeded: All executed actions completed successfully.
Failed: At least one action encountered an unhandled error, terminating the flow run.
Running: The flow is actively processing actions (or waiting on an Approval / Delay step).
Timed Out: An action or flow exceeded its maximum execution window (e.g., an approval waiting >30 days).
Cancelled: The flow run was aborted manually by a maker or administrator.
Raw Inputs & Outputs Inspection: Clicking any individual action reveals the exact JSON payloads sent to and received from the underlying API. Makers can inspect HTTP status codes (e.g., 400 Bad Request , 401 Unauthorized , 404 Not Found , 429 Too Many Requests , 502 Bad Gateway ) to diagnose integration faults.
Apply to Each Iteration Debugging: When errors occur inside a loop, the run viewer displays navigation arrows allowing consultants to page directly to the specific iteration number that failed.
2. Resubmission & Flow Testing Strategies
When a cloud flow fails due to a temporary downstream service interruption or an expression bug, consultants have powerful tools to correct and reprocess transactions without impacting end users. +-----------------------------------------------------------------------------+
- | FLOW RESUBMISSION & TESTING |
- | |
- | [RESUBMIT FAILED RUN] |
- | - Takes the exact historical trigger payload from the failed run. |
- | - Re-executes the flow without requiring the user to re-trigger the event.|
- | |
- | [EDIT AND RESUBMIT PATTERN] |
- | 1. Identify bug in failed run (e.g., faulty expression). |
- | 2. Edit the Cloud Flow in the designer and Save updates. |
- | 3. Return to Run History > Select Failed Run > Click 'Resubmit'. |
- | 4. The new flow version executes using the original failed data! |
- | |
- | [TESTING: WITH RECENTLY USED TRIGGER] |
- | - Allows makers to test flow logic during development by replaying |
- | prior trigger payloads without creating dummy records in production. |
- +-----------------------------------------------------------------------------+
- Resubmitting Failed Runs
Original Payload Replay: Selecting Resubmit on a failed run immediately creates a brand-new run instance using the identical trigger body captured during the original event.
Fix-and-Resubmit Workflow: If a flow failed due to a missing action or an expression error, the maker can edit the flow definition, save the changes, and then resubmit the failed run. The newly saved logic will process the original payload.
Testing Modes in Flow Designer
When testing a flow, makers choose between two modes:
Manually: The flow enters a listening state. The maker must perform the real-world trigger action (e.g., creating a row in Dataverse or uploading a SharePoint file) to start the test.
Automatically (With a recently used trigger): The designer displays a list of recent trigger payloads from previous runs. The maker selects a prior execution to instantly test the flow without creating test data or waiting for external events.
3. Power Platform Admin Center (PPAC) Analytics
While Run History provides tactical debugging for individual flows, the Power Platform Admin Center (PPAC) provides strategic, tenant-wide operational analytics. +-----------------------------------------------------------------------------------+
- | PPAC AUTOMATION ANALYTICS ENGINE |
- | |
- | [DASHBOARDS] |
- | - Usage: Total runs, active flows, daily/weekly execution trends |
- | - Errors: Failure rates, error breakdown by connector type, top 10 failing flows |
- | - Maker Activity: Flow creation distribution, departmental adoption |
- | |
- | [CAPACITY & THROTTLING MONITORING] |
- | - Power Platform Request Limits (API calls per 24-hour rolling window) |
- | - Connector Throttling Alerts (Detecting 429 Too Many Requests) |
- | |
- | [ORPHANED FLOW GOVERNANCE] |
- | - Identifies flows owned by disabled/departed Microsoft Entra users |
- | - Allows administrators to assign new co-owners or service principals |
- +-----------------------------------------------------------------------------------+
- Core PPAC Analytics Views
Usage Dashboard: Displays aggregated execution counts, daily active flows, and run metrics across environments.
Error Analytics: Highlights the Top 10 failing flows in the environment and categorizes errors by connector and error type, enabling administrators to identify problematic integrations proactively.
Power Platform Request (API) Consumption: Tracks daily API call volumes against tenant licensing limits, identifying flows causing performance degradation or triggering connector throttling.
4. Dataverse System Jobs ( asyncoperation ) & Plug-in Trace Logs
For automations executing natively inside Dataverse—including Classic Background Workflows, Bulk Delete tasks, Rollup Column calculations, and Server-Side Plug-ins—monitoring is managed through specialized Dataverse system tables. +-----------------------------------------------------------------------------+
- | DATAVERSE SYSTEM MONITORING |
- | |
- | [SYSTEM JOBS (asyncoperation)] [PLUG-IN TRACE LOG (plugintracelog)]|
- | - Tracks Background Workflows - Captures Low-Code & C# Plug-in |
- | - Tracks Bulk Deletions & Imports execution exceptions |
- | - Tracks Rollup / Calc recalculations - Tracing Settings: |
- | - States: Ready, In Progress, * Off (Disabled) |
- | Paused, Succeeded, Failed, * Exception (Logs errors only) |
- | Canceling, Canceled * All (Logs all runs - verbose) |
- +-----------------------------------------------------------------------------+
- System Job States and Status Reasons
The asyncoperation table maintains the lifecycle state of all asynchronous jobs:
Ready: The job is queued and waiting for an available worker thread in the AsyncService pool.
In Progress: The job is actively executing.
Pausing / Paused: The job was temporarily paused (e.g., waiting for a scheduled timer or wait condition).
Succeeded: The background job completed without error.
Failed: The job encountered a fatal error after exhausting all retry attempts.
Canceled / Canceling: The job was terminated by an administrator.
Plug-in Trace Log Configuration
To diagnose faults in Low-Code Plug-ins or C# custom plug-ins, administrators configure the Plug-in and custom workflow activity tracing setting in PPAC ( Settings > Custom code and extensions > Plug-in trace log ):
Off: No logs are recorded (Default production setting to optimize storage).
Exception: Logs are created only when a plug-in throws an unhandled exception or Error() call. (Recommended for production environments).
All: Logs every single execution, including execution time, input parameters, and trace messages. (Used temporarily in development and testing environments for deep diagnostics; must not be left active indefinitely in high-volume production due to database storage consumption).