Plugin
power-automate
Plugin Version
2.0.0
Skill / Command
browse-flows (list_flows, list_connectors)
Bug Description
Every call that hits the PPAPI/Flow API for a "Default" (tenant-root) environment fails
with a network error. The tool constructs a hostname by inserting a stray dot 2
characters before the end of the environment GUID (with dashes stripped), producing an
invalid, non-existent hostname instead of a valid PPAPI endpoint.
Steps to Reproduce
- Have a Power Platform "Default" environment (env ID format: Default-).
- Call list_environments — succeeds, environment is listed correctly.
- Call set_current_env (or pass env directly) to select that Default environment.
- Call list_flows (or list_connectors) against that environment.
Expected Behavior
The tool builds a valid PPAPI hostname (e.g. ..environment.api.powerplatform.com)
and returns the list of flows/connectors.
Actual Behavior
Fails with:
FlowApiError: Flow API 0 NetworkError: Network request failed: ENOTFOUND
(hostname: <32-hex-chars-with-dashes-removed, minus last 2 chars>.<last-2-chars>.environment.api.powerplatform.com)
This often means the environment ID produced an invalid PPAPI URL.
Example (GUID replaced with a placeholder, structure preserved):
Env ID: Default-11111111-2222-3333-4444-555555555555
Resulting (broken) hostname: 111111112222333344445555555555.55.environment.api.powerplatform.com
(dot inserted 2 chars from the end of the 32-char no-dash GUID)
This reproduces identically across multiple tools (list_flows, list_connectors), and
resolve_environment reports this environment's provisioned field as false, which may
be a related signal in the hostname-construction logic.
Azure CLI auth (az login, az account show) is confirmed working and unrelated to
this failure — the bug is isolated to PPAPI hostname construction for this environment
ID shape.
Relevant Logs / Screenshots
FlowApiError: Flow API 0 NetworkError: Network request failed: ENOTFOUND
(hostname: 111111112222333344445555555555.55.environment.api.powerplatform.com)
This often means the environment ID produced an invalid PPAPI URL. Verify the
environment ID is a valid GUID.
Environment
OS: Windows 11 Pro 10.0.26100
Claude Code: 2.1.216 (Claude Code)
PAC CLI: not installed
Plugin
power-automate
Plugin Version
2.0.0
Skill / Command
browse-flows (list_flows, list_connectors)
Bug Description
Every call that hits the PPAPI/Flow API for a "Default" (tenant-root) environment fails
with a network error. The tool constructs a hostname by inserting a stray dot 2
characters before the end of the environment GUID (with dashes stripped), producing an
invalid, non-existent hostname instead of a valid PPAPI endpoint.
Steps to Reproduce
Expected Behavior
The tool builds a valid PPAPI hostname (e.g. ..environment.api.powerplatform.com)
and returns the list of flows/connectors.
Actual Behavior
Fails with:
Example (GUID replaced with a placeholder, structure preserved):
This reproduces identically across multiple tools (list_flows, list_connectors), and
resolve_environment reports this environment's
provisionedfield asfalse, which maybe a related signal in the hostname-construction logic.
Azure CLI auth (
az login,az account show) is confirmed working and unrelated tothis failure — the bug is isolated to PPAPI hostname construction for this environment
ID shape.
Relevant Logs / Screenshots
FlowApiError: Flow API 0 NetworkError: Network request failed: ENOTFOUND (hostname: 111111112222333344445555555555.55.environment.api.powerplatform.com) This often means the environment ID produced an invalid PPAPI URL. Verify the environment ID is a valid GUID.Environment
OS: Windows 11 Pro 10.0.26100
Claude Code: 2.1.216 (Claude Code)
PAC CLI: not installed