power-automate-monitoringlisted

Monitor Power Automate flow health, track failure rates, and inventory tenant assets using the FlowStudio MCP cached store. The live API only returns top-level run status. Store tools surface aggregated stats, per-run failure details with remediation hints, maker activity, and Power Apps inventory — all from a fast cache with no rate-limit pressure on the PA API. Load this skill when asked to: check flow health, find failing flows, get failure rates, review error trends, list all flows with monitoring enabled, check who built a flow, find inactive makers, inventory Power Apps, see environment or connection counts, get a flow summary, or any tenant-wide health overview. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app
ninihen1/power-automate-mcp-skills · ★ 14 · DevOps & Infrastructure · score 78

Install: claude install-skill ninihen1/power-automate-mcp-skills

# Power Automate Monitoring with FlowStudio MCP Monitor flow health, track failure rates, and inventory tenant assets through the FlowStudio MCP **cached store** — fast reads, no PA API rate limits, and enriched with governance metadata and remediation hints. > **Requires:** A [FlowStudio for Teams or MCP Pro+](https://mcp.flowstudio.app) > subscription. > > **Start every session with `tools/list`** to confirm tool names and parameters. > This skill covers response shapes, behavioral notes, and workflow patterns — > things `tools/list` cannot tell you. If this document disagrees with > `tools/list` or a real API response, the API wins. --- ## How Monitoring Works Flow Studio scans the Power Automate API daily for each subscriber and caches the results. There are two levels: - **All flows** get metadata scanned: definition, connections, owners, trigger type, and aggregate run statistics (`runPeriodTotal`, `runPeriodFailRate`, etc.). Environments, apps, connections, and makers are also scanned. - **Monitored flows** (`monitor: true`) additionally get per-run detail: individual run records with status, duration, failed action names, and remediation hints. This is what populates `get_store_flow_runs`, `get_store_flow_errors`, and `get_store_flow_summary`. **Data freshness:** Check the `scanned` field on `get_store_flow` to see when a flow was last scanned. If stale, the scanning pipeline may not be running. **Enabling monitoring:** Set `monitor: true` via `updat