Update FlowStudio Power Automate skills for server 1.2.77 - #2943
Conversation
trigger_live_flow now runs scheduled (Recurrence) flows on demand; list_live_connections requires environmentName and applies top after search; the ChatGPT/claude.ai connector path is documented in the mcp skill; the brand reads FlowStudio (one word) across the skills and plugin README; the build skill is back under the 500-line lint limit.
🔒 PR Risk Scan ResultsScanned 7 changed file(s).
✅ No matching risk patterns were detected in changed files.
|
There was a problem hiding this comment.
🟡 Changes recommended
The creation example reads a nonexistent response field, and the debug table recommends unsupported triggering for connector flows.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates FlowStudio Power Automate guidance for MCP server 1.2.77.
Changes:
- Documents Recurrence flow execution and connection requirements.
- Corrects deployment guidance and OAuth setup.
- Standardizes FlowStudio branding.
File summaries
| File | Description |
|---|---|
skills/flowstudio-power-automate-monitoring/SKILL.md |
Updates branding. |
skills/flowstudio-power-automate-mcp/SKILL.md |
Adds OAuth connector setup. |
skills/flowstudio-power-automate-mcp/references/tool-reference.md |
Updates tool behavior and requirements. |
skills/flowstudio-power-automate-governance/SKILL.md |
Updates branding. |
skills/flowstudio-power-automate-debug/SKILL.md |
Revises trigger guidance. |
skills/flowstudio-power-automate-build/SKILL.md |
Revises non-HTTP flow testing guidance. |
plugins/flowstudio-power-automate/README.md |
Updates branding. |
Review details
- Files reviewed: 4/7 changed files
- Comments generated: 2
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| definition=definition, connectionReferences=connection_references, | ||
| displayName="Overdue Invoice Notifications") | ||
| FLOW_ID = FLOW_ID or result["created"] | ||
| FLOW_ID = FLOW_ID or result["flowName"] |
| | SharePoint / connector trigger | `resubmit_live_flow_run` | Cannot be triggered without creating a real SP item | | ||
| | HTTP, Button, or PowerApps trigger with **custom** test payload | `trigger_live_flow` | When you need to send different data than the original run | | ||
| | Brand-new flow, never run | `trigger_live_flow` (HTTP, Button, PowerApps) | No prior run exists to resubmit | | ||
| | Brand-new flow, never run | `trigger_live_flow` | No prior run exists to resubmit | |
🔍 Vally Lint Results✅ All checks passed
Summary
Full linter output |
There was a problem hiding this comment.
🟡 Changes recommended
The revised guidance contains an invalid response-key lookup and conflicting instructions for connection and trigger handling.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (2)
skills/flowstudio-power-automate-build/SKILL.md:433
- The documented
update_live_flowcontract returns the new GUID increated(tool-reference.md:244) and does not define aflowNameresponse key. WhenFLOW_IDis empty for a new connector flow, this lookup raisesKeyError, so the sample never triggers the flow or restores its production trigger.
FLOW_ID = FLOW_ID or result["flowName"]
skills/flowstudio-power-automate-debug/SKILL.md:415
- This unqualified row also covers brand-new connector-triggered flows, but those cannot be invoked by
trigger_live_flowand have no prior run to resubmit. Following this table would therefore send those flows to a guaranteed error; scope the row to the trigger types the tool supports.
| Brand-new flow, never run | `trigger_live_flow` | No prior run exists to resubmit |
- Files reviewed: 4/7 changed files
- Comments generated: 1
- Review effort level: Balanced
| > `environmentName` is required — the platform cannot list connections across | ||
| > environments (omitting it answers 400 MissingEnvironmentFilter). Get one from | ||
| > `list_live_environments`. |
What changed
FlowStudio MCP server 1.2.77 changed two tools, and the brand spelling was updated to one word. Seven files across the five FlowStudio skills and the plugin README:
flowstudio-power-automate-debug/SKILL.md—trigger_live_flownow runs scheduled (Recurrence) flows on demand (nobody; scheduled triggers take no inputs), so the resubmit-vs-trigger guidance sends scheduled flows there instead of claiming they cannot be run.flowstudio-power-automate-build/SKILL.md— the HTTP-twin workaround now applies only to connector-triggered flows (Recurrence no longer needs it); fixes a sample that read the new flow id from a boolean; back under the 500-line lint limit that PR Update FlowStudio Power Automate skills for Button, PowerApps, and Skills triggers #2826 tripped.flowstudio-power-automate-mcp/SKILL.md+references/tool-reference.md— the ChatGPT/claude.ai connector path in prerequisites;list_live_connectionsrequiresenvironmentName(the across-environments claim was never supported by the platform) and appliestopaftersearch; retired wording the server's 1.2.55 descriptions dropped.flowstudio-power-automate-governance/SKILL.md,flowstudio-power-automate-monitoring/SKILL.md,plugins/flowstudio-power-automate/README.md— brand spelling: FlowStudio, one word.Frontmatter unchanged, so README output is unaffected. All five skills pass
@microsoft/vally-cli lintlocally. Behavior claims verified against the production server (1.2.77).🤖 Generated with Claude Code