mcpField
M
manage-flows

manage-flows

github.com/microsoftDevelopment1.1k153 installsUpdated today
Repository

About manage-flows

A skill for managing flow lifecycles through publishing and testing, batch actions, inventory reports, health checks, and incident response. It uses FlowAgent MCP tools, with CLI commands for operations those tools do not cover.

Key features

  1. 01Publish flows and verify runs
  2. 02Batch publish, disable, or delete flows
  3. 03Report environments and flow inventory
  4. 04Check run history and failure rates
  5. 05Cancel runaway runs and resubmit eligible runs

Use cases

  1. 01Test a flow immediately after publishing
  2. 02Disable or remove several flows
  3. 03Review flow states across environments
  4. 04Investigate repeated failures or queued runs

MCP support

Uses FlowAgent MCP tools for flow operations such as publishing, running, listing, and checking histories. CLI shell commands are reserved for CLI-only operations or when MCP tools are unavailable.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/microsoft/power-platform-skills --skill manage-flows

After installing, type/manage-flowsin Claude Code to confirm it loaded.

Details

From the project README

Flow Lifecycle Manager

Autonomous agent for flow lifecycle operations: publish-and-test, batch operations, inventory reports.

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). Use CLI shell commands (local engine build only) for CLI-only operations (connection lifecycle, sharing, solutions/admin) or when no MCP tools are present.

Capabilities

1. Publish-and-Test Cycle
  1. Call publish_flow to enable
  2. Call run_flow with wait: true and timeout: 30 to trigger and wait for completion
  3. Report: pass/fail, duration, action statuses
2. Batch Operations

For multiple flows (IDs from $ARGUMENTS or from list_flows):

  • Batch disable: Call disable_flow per flow
  • Batch delete: Call delete_flow per flow (confirm first)
  • Batch publish: Call publish_flow per flow Report per-item success/failure.
3. Inventory Report
  1. Call list_environments to get environments
  2. Call list_flows on each (or specified) environment
  3. Produce summary: flow counts by state, trigger types, recent modifications
4. Health Check

For each flow in an environment:

  1. Call get_run_history with top: 5
  2. Count Succeeded vs Failed runs
  3. Flag flows with >50% failure rate Report: flow name, success rate, last run status, last failure error.
5. Incident Response (runaway runs)

When a flow is misfiring with many queued runs:

  1. Call cancel_all_runs to bulk-cancel every Running/Waiting run (uses the Dataverse bulk action for solution & modern non-solution flows, per-run fallback otherwise). Pass turnOff: true to also disable the flow while the root cause is fixed.
  2. After fixing, resubmit_run the affected runs (note: only self-invoked runs are resubmittable per PA policy).

Comments

Markdown supported