flowstudio-power-automate-monitoring

Monitors tenant-wide Power Automate flow health using the FlowStudio MCP cached store.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill flowstudio-power-automate-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowstudio-power-automate-monitoring
Source: https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-monitoring
Command: npx skills add https://github.com/github/awesome-copilot --skill flowstudio-power-automate-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Power Platform administrators lack a fast, aggregated view of flow health across an entire tenant without hitting Power Automate API rate limits. This Skill provides cached, tenant-wide monitoring data including failure rates, run trends, maker inventories, and inactive owner detection.

Core Features & Use Cases

  • Tenant-wide health monitoring: List flows with failure rates, run statistics, and monitoring status through cached store tools that avoid live API throttling.
  • Run history and failure analysis: Retrieve per-run records with status, duration, failed action names, and remediation hints for monitored flows.
  • Inventory and maker audits: Enumerate environments, connections, Power Apps, and makers, including deleted accounts that still own flows.
  • Use Case: Run a daily health check by listing all flows, flagging those with a failure rate above 20 percent, and pulling failed run details with remediation hints for critical flows.

Quick Start

Ask the agent to list all Power Automate flows in the tenant with a failure rate above 10 percent and summarize their health using the FlowStudio store tools.

Frequently Asked Questions about flowstudio-power-automate-monitoring

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

FAQPage Schema
How do I monitor Power Automate flow failure rates across a tenant?

Use list_store_flows to retrieve all flows with runPeriodFailRate and runPeriodTotal fields, then filter and sort by failure rate. For a specific flow, call get_store_flow_summary for aggregated stats and get_store_flow_runs with status Failed for per-run detail.

What is the difference between FlowStudio store tools and live tools?

Store tools read cached daily scan data for fast aggregated tenant views without API rate limits, answering what happened and how healthy flows are. Live tools query the Power Automate API directly for action-level inputs, outputs, and run resubmission.

Does Power Automate monitoring require a FlowStudio Pro+ subscription?

Yes, all store_* tools require a FlowStudio for Teams or MCP Pro+ subscription. Without it, the first store tool call returns a 403 or 404 error, and you should use live-tool skills like flowstudio-power-automate-mcp instead.

Why does get_store_flow_runs return empty results?

Empty results occur when the flow does not have monitor set to true or when the cached scan is stale. Call get_store_flow to verify the monitor flag and check the scanned field for data freshness.

How do I find inactive owners still running Power Automate flows?

Call list_store_makers and identify entries with deleted set to true but ownerFlowCount greater than zero. Use get_store_maker for full detail on specific users including licenses and account status.