/flowstudio-power-automate-monitoring

name: flowstudio-power-automate-monitoring
description: >-
  Pro+ subscription required. Tenant-wide Power Automate monitoring using the
  FlowStudio MCP cached store: failure rates, run-health trends, maker/app
  inventory, inactive owners, and compliance/health reports. Use only for
  aggregated tenant views. For one environment, one flow, run control, or
  root-cause debugging, use flowstudio-power-automate-mcp, flowstudio-power-automate-debug, or the
  server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+.

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.

> **⚠️ Pro+ subscription required.** This skill calls `store_*` tools that > only work for FlowStudio for Teams or MCP Pro+ subscribers. > > **If the user does not have Pro+ access:** the first `store_*` tool call > will return a 403/404 error. When that happens: > 1. STOP calling store tools > 2. Tell the user this feature requires a Pro+ subscription > 3. Link them to https://mcp.flowstudio.app/pricing > 4. If their question can be answered with live tools (e.g. "list flows in > one environment"), offer to use the `flowstudio-power-automate-mcp` skill instead > > **Discovery:** load tool schemas via `tool_search` rather than `tools/list` — > call with `query: "select:list_store_flows,get_store_flow_summary"` for the > common monitoring tools, or load the full set with `query: "skill:governance"` > (the server's governance bundle covers most monitoring reads too — this skill > and `flowstudio-power-automate-governance` share the underlying tool family). This skill > covers response shapes, behavioral notes, and workflow patterns — things > `tool_search` cannot tell you. If this document disagrees with a real API > response, the API wins.

---

How Monitoring Works

FlowStudio 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` 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 `update_store_flow` or the FlowStudio for Teams app ([how to select flows](https://learn.flowstudio.app/teams-monitoring)).

**Designating critical flows:** Use `update_store_flow` with `critical=true` on business-critical flows. This enables the governance skill's notification rule management to auto-configure failure alerts on critical flows.

---

Tools

| Tool | Purpose | |---|---| | `list_store_flows` | List flows with failure rates and monitoring filters | | `get_store_flow` | Full cached record: run stats, owners, tier, connections, definition (`triggerUrl` field included) | | `get_store_flow_summary` | Aggregated run stats: success/fail rate, avg/max duration | | `get_store_flow_runs` | Per-run history with duration, status, failed actions, remediation (filter `status="Failed"` for errors-only view) | | `update_store_flow` | Set monitor flag, notification rules, tags, governance metadata | | `list_store_environments` | All Power Platform environments | | `list_store_connections` | All connections | | `list_store_makers` | All makers (citizen developers) | | `get_store_maker` | Maker detail: flow/app counts, licenses, account status | | `list_store_power_apps` | All Power Apps canvas apps |

> For start/stop, use `set_live_flow_state` from the `monitor-flow` bundle > (`tool_search query: "select:set_live_flow_state"`) — the cache resyncs on > the next scan. The previous `set_store_flow_state` convenience wrapper is > deprecated.

---

Store vs Live

| Question | Use Store | Use Live | |---|---|---| | How many flows are failing? | `list_store_flows` | — | | What's the fail rate over 30 days? | `get_store_flow_summary` | — | | Show error history for a flow | `get_store_flow_runs` (filter `status="Failed"`) | — | | Who built this flow? | `get_store_flow` → parse `owners` | — | | Read the full flow definition | `get_store_flow` has it (JSON string) | `get_live_flow` (structured) | | Inspect action inputs/outputs from a run | — | `get_live_flow_run_action_outputs` | | Resubmit a failed run | — | `resubmit_live_flow_run` |

> Store tools answer "what happened?" and "how healthy is it?" > Live tools answer "what exactly went wrong?" and "fix it now."

> If `get_store_flow_runs` or `get_store_flow_summary` return empty results, > check: (1) is `monitor: true` on the flow? and (2) is the `scanned` field > recent? Use `get_store_flow` to verify both.

---

Response Shapes

`list_store_flows`

Direct array. Filters: `monitor` (bool), `rule_notify_onfail` (bool), `rule_notify_onmissingdays` (bool).

[
  {
    "id": "Default-<envGuid>.<flowGuid>",
    "displayName": "Stripe subscription updated",
    "state": "Started",
    "triggerType": "Request",
    "triggerUrl": "https://...",
    "tags": ["#operations", "#sensitive"],
    "environmentName": "Default-aaaaaaaa-...",
    "monitor": true,
    "runPeriodFailRate": 0.012,
    "runPeriodTotal": 82,
    "createdTime": "2025-06-24T01:20:53Z",
    "lastModifiedTime": "2025-06-24T03:51:03Z"
  }
]

> `id` format: `Default-<envGuid>.<flowGuid>`. Split on first `.` to get > `environmentName` and `flowName`. > > `triggerUrl` and `tags` are optional. Some entries are sparse (just `id` + > `monitor`)