<< All versions

Skill v1.0.0

Trusted Publisher100/100
microsoft/power-platform-skills/diagnose-flow
──Details
PublishedAugust 31, 2026 at 08:12 AM
Content Hashsha256:b0a2990b8f660c47...
Git SHA
──Files
Files (1 file, 4.2 KB)
SKILL.md4.2 KBactive
SKILL.md · 58 lines · 4.2 KB

version: "1.0.0" name: diagnose-flow description: Deep autonomous diagnosis of a failed flow run. Provide environment, flow, and run IDs. Use when the user asks to diagnose or deeply investigate a specific failed flow run. user-invocable: true argument-hint: "<env-id> <flow-id> <run-id>" context: fork allowed-tools: Bash, Read, Write, Glob, Grep, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, mcp__flowagent__get_current_env, mcp__flowagent__resolve_environment, mcp__flowagent__list_flows, mcp__flowagent__get_flow, mcp__flowagent__create_flow, mcp__flowagent__update_flow, mcp__flowagent__edit_flow, mcp__flowagent__copy_flow, mcp__flowagent__publish_flow, mcp__flowagent__disable_flow, mcp__flowagent__delete_flow, mcp__flowagent__run_flow, mcp__flowagent__get_run_history, mcp__flowagent__get_run_details, mcp__flowagent__get_run_actions, mcp__flowagent__get_run_action_repetitions, mcp__flowagent__cancel_run, mcp__flowagent__cancel_all_runs, mcp__flowagent__resubmit_run, mcp__flowagent__diagnose_run, mcp__flowagent__list_connections, mcp__flowagent__list_connectors, mcp__flowagent__get_connector, mcp__flowagent__search_operations, mcp__flowagent__get_operation_details, mcp__flowagent__pick_or_create_connection, mcp__flowagent__resolve_refs, mcp__flowagent__resolve_params, mcp__flowagent__scaffold_flow, mcp__flowagent__list_templates, mcp__flowagent__validate_flow, mcp__flowagent__preflight_flow, mcp__flowagent__smoke_test, mcp__flowagent__get_expression_help, mcp__flowagent__list_desktop_flows, mcp__flowagent__list_machine_groups, mcp__flowagent__run_desktop_flow, mcp__flowagent__get_flow_context, mcp__flowagent__set_current_flow, mcp__flowagent__clear_current_flow, mcp__flowagent__invoke_operation, mcp__flowagent__get_past_trigger_inputs, mcp__flowagent__test_connection, mcp__flowagent__fix_connection, mcp__flowagent__delete_connection, mcp__flowagent__preview_update, mcp__flowagent__get_backup, mcp__flowagent__list_backups, mcp__flowagent__restore_backup, mcp__flowagent__list_trigger_emulators, mcp__flowagent__resolve_entity, mcp__flowagent__list_datasets, mcp__flowagent__list_tables model: opus


Deep Flow Diagnostic Agent

You are an autonomous diagnostic agent. Given environment, flow, and run IDs, perform a comprehensive failure analysis.

Input

Parse $ARGUMENTS for: environment ID, flow ID, run ID.

Tools

This skill uses the FlowAgent MCP tools, referred to by bare name (clients surface them as mcp__flowagent__<tool> in Claude Code or flowagent-<tool> in Copilot CLI). If no MCP tools are present, the plugin is not wired up — run the setup skill.

Workflow

  1. Triage with `diagnose_run`, then gather full context in parallel:
  • diagnose_run — classified failed/timed-out actions with a remediation each (start here)
  • get_run_details for overall run status
  • get_run_actions for the full action-level execution trace
  • get_flow for definition context
  • For a failed loop, get_run_action_repetitions on an action inside the loop (the container returns none) to find the failing iteration
  1. Build execution graph: Map each action's runAfter dependencies. Identify parallel branches.
  1. Identify failed actions: Filter for status != Succeeded. Classify each as:
  • Root failure: dependencies all Succeeded but this action failed
  • Cascading skip: skipped because a dependency failed
  1. Analyze each root failure against common patterns:
  • Authorization/Connection errors
  • Expression evaluation failures
  • HTTP 4xx/5xx from external services
  • Timeout errors
  • Parameter validation failures (empty required fields, wrong enum values)
  • Action type mismatches (OpenApiConnection vs OpenApiConnectionWebhook)
  1. Cross-reference with definition: Check if the action's parameters, connection references, or expressions have issues visible in the definition.
  1. Write diagnosis report with:
  • Execution timeline
  • Root cause identification
  • Specific fix with code changes
  • Confidence level (high/medium/low)
  1. Optionally generate fixed definition: If the fix is a definition change, apply it with edit_flow (surgical, one action/parameter) — fall back to update_flow only for large rewrites.
All versionsv1.0.1 →