flowstudio-power-automate-debug

Debug failing Power Automate cloud flows by locating failed runs and root actions.

27|9|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ninihen1/power-automate-mcp-skills --skill flowstudio-power-automate-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowstudio-power-automate-debug
Source: https://github.com/ninihen1/power-automate-mcp-skills/tree/main/awesome-copilot/skills/flowstudio-power-automate-debug
Command: npx skills add https://github.com/ninihen1/power-automate-mcp-skills --skill flowstudio-power-automate-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rapidly locate, analyze, and remediate failures in Power Automate cloud flows by using FlowStudio MCP to inspect runs, action outputs, and flow definitions so engineers can reduce downtime and restore correct behavior.

Core Features & Use Cases

  • Root-cause identification: Find the failing run, read the top-level run error, and pinpoint the root failing action using live run diagnostics.
  • Detailed action inspection: Retrieve action outputs and upstream data to diagnose expression errors, wrong field paths, type mismatches, and HTTP/connector failures.
  • Repair and verify: Apply definition fixes via the MCP update endpoint, resubmit or trigger flows for verification, and follow a decision tree for connection or auth problems.
  • Use Case: Investigate a recurring failure where a split or parse expression crashes, determine whether the source field is null or misnamed, apply a coalesce or path fix, update the flow, then resubmit and confirm success.

Quick Start

Ask the agent to debug the failed flow named "My Flow Name" in the specified environment by locating the failing run, identifying the root action, inspecting prior action outputs for nulls or type mismatches, and recommending or applying a fix.

Frequently Asked Questions about flowstudio-power-automate-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failing Power Automate flow run?

To debug a failing Power Automate flow run, locate the specific run, read the top-level error, and pinpoint the root failing action. This process helps identify expression errors, connector authentication failures, or HTTP action data quality issues.

How do I diagnose expression errors and connector authentication failures in Power Automate?

Diagnose expression errors and connector authentication failures by retrieving action outputs and inspecting upstream data. This helps find wrong field paths, type mismatches, or null source fields causing the split or parse expression to crash.

What is the best way to fix and resubmit a failed Power Automate cloud flow?

The best way to fix and resubmit a failed flow is to apply definition fixes, such as adding a coalesce or path fix, update the flow, then resubmit or trigger flows for verification to confirm success and restore correct behavior.

Do I need MCP endpoint access to troubleshoot Power Automate flows?

Yes, you need MCP endpoint access with a valid JWT passed as the x-api-key header to troubleshoot Power Automate flows. This access allows you to read definitions, inspect action outputs, update definitions, and trigger HTTP flows for verification.

Why does my Power Automate flow crash when parsing a null field?

Your Power Automate flow crashes when parsing a null field because the source field is misnamed or null. Inspecting prior action outputs reveals nulls or type mismatches, allowing you to apply a coalesce or path fix to resolve the failure.