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-ca

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 format: Default <envGuid .<flowGuid . Split on first . to get environmentName and flowName . triggerUrl and tags are optional. Some entries are sparse (just id + monitor ) — skip entries without displayName . Tags on list store flows are auto extracted from the flow's description field (maker hashtags like operations ). Tags written via update store flow(tags=...) are stored separately and only visible on get store flow — they do NOT appear in the list response. get store flow Full cached record. Key fields: Category Fields Identity name , displayName , environmentName , state , triggerType , triggerKind , tier , sharingType Run stats runPeriodTotal , runPeriodFails , runPeriodSuccess , runPeriodFailRate , runPeriodSuccessRate , runPeriodDurationAverage / Max / Min (milliseconds), runTotal , runFails , runFirst , runLast , runToday Governance monitor (bool), rule notify onfail (bool), rule notify onmissingdays (number), rule notify email (string), log notify onfail (ISO), description , tags Freshness scanned (ISO), nextScan (ISO) Lifecycle deleted (bool), deletedTime (ISO) JSON strings actions , connections , owners , complexity , definition , createdBy , security , triggers , referencedResources , runError — all require json.loads() to parse Duration fields ( runPeriodDurationAverage , Max , Min ) are in milliseconds . Divide by 1000 for seconds. runError contains the last run error as a JSON string. Parse it: json.loads(record["runError"]) — returns {} when no error. get store flow summary Aggregated stats over a time window (default: last 7 days). Returns all zeros when no run data exists for this flow in the window. Use startTime and endTime (ISO 8601) parameters to change the window. get store flow runs Direct array of cached run records. Parameters: startTime , endTime , status (array — pass ["Failed"] for an errors only view, ["Succeeded"] , or omit for all). Returns [] when no run data exists in the window. Trigger URL Read the triggerUrl field directly from get store flow (cached) or get live flow (live). It is null for non HTTP triggers. Starting / stopping a flow Use set live flow state from the monitor flow server bundle. The cache catches up on the next daily scan; if you need cache freshness sooner, call get live flow after the state change to confirm and let the next scan sync. update store flow Updates governance metadata. Only provided fields are updated (merge). Returns the full updated record (same shape as get store flow ). Settable fields: monitor (bool), rule notify onfail (bool), rule notify onmissingdays (number, 0=disabled), rule notify email (comma separated), description , tags , businessImpact , businessJustification , businessValue , ownerTeam , ownerBusinessUnit , supportGroup , supportEmail , critical (bool), tier , security . list store environments Direct array. sku values: Default , Production , Developer , Sandbox , Teams . list store connections Direct array. Can be very large (1500+ items). createdBy and statuses are JSON strings — parse with json.loads() . list store makers Direct array. Deleted makers have deleted: true and no displayName / mail fields. get store maker Full maker record. Key fields: displayName , mail , userPrincipalName , ownerFlowCount , ownerAppCount , accountEnabled , deleted , country , firstFlow , firstFlowCreatedTime , lastFlowCreatedTime , firstPowerApp , lastPowerAppCreatedTime , licenses (JSON string of M365 SKUs). list store power apps Direct array. Common Workflows Find unhealthy flows Check a specific flow's health Enable monitoring on a flow Daily health check Maker audit Inventory Related Skills flowstudio power automate mcp — Foundation skill: connection setup, MCP helper, tool discovery flowstudio power automate debug — Deep diagnosis with action level inputs/outputs (live API) flowstudio power automate build — Build and deploy flow definitions flowstudio power automate governance — Governance metadata, tagging, notification rules, CoE patterns

flowstudio-power-automate-monitoring