[power-automate][Bug] list_connectors/search_operations/get_operation_details fail with malformed PPAPI hostname

[paulokane71-dotcom]

Plugin

power-automate

Plugin Version

2.5.0

Skill / Command

N/A (direct MCP tool calls)

Bug Description

list_connectors, search_operations, and get_operation_details all fail with a NetworkError
caused by a malformed environment API hostname. A stray "." is inserted into the environment
GUID right before ".environment.api.powerplatform.com", producing an unresolvable hostname.
This happens regardless of the env value passed to the tool.

Steps to Reproduce

1. Call list_environments, get a valid environment (unique name "Default-").
2. Call set_current_env with that environment (succeeds, returns correct envId).
3. Call list_connectors, search_operations, or get_operation_details — with env passed as
   the "Default-" unique name, as the raw GUID, or omitted entirely (relying on the
   session default set in step 2).
4. All three calls fail the same way.

Note: get_flow and list_flows work correctly with the same environment values, so the bug
appears isolated to the URL builder shared by these three connector-lookup tools.

Expected Behavior

The tools should build a valid PPAPI hostname from the environment GUID and return connector/
operation data.

Actual Behavior

All three calls fail with: "Flow API 0 NetworkError: Network request failed: ENOTFOUND
(hostname: .environment.api.powerplatform.com)". The hostname
has a "." inserted before the last two characters of the GUID, breaking DNS resolution.

Relevant Logs / Screenshots

Flow API 0 NetworkError: Network request failed: ENOTFOUND (hostname:
.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: macOS 15.0.1 (Build 24A348)
Claude Code version: (not detected)

---

🤖 This issue was created using the /report-issue skill.

[radioblazer]

Fixed in v3.0.1 — resolved in PR #393, merged 2026-08-12.

Please update to v3.0.1 and let us know if you're still seeing this.