[Non-public cloud]:"Run Trigger" button is grayed out in overview page after deploying to logic app.

[v-ksruthi]

Severity

P1 - Critical (Blocking production)

Describe the Bug with repro steps

Repro Steps:

1. Install VSIX version 5.273.0
2. Choose an Azure cloud in VSCode settings
3. Log in to Mooncake with the necessary credentials.
4. In the VSCode command palette (Ctrl+Shift+P), type "Deploy to logic app"
5. Select "Create new Logic App (Standard) in Azure..."
6. Enter the logic app name
7. Choose China North 2 as the location
8. Select the Workflow Standard option
9. Once the logic app is created successfully
10. Click Deploy
11. After deployment is successful, Upload Local Settings.
12. After successfully upload the local settings
13. Open the logic app and open designer
14. click on overview tab

Expected result: Overview blade is should open succesfully
Actual result: Run trigger button is showing grayed out in Overview blade

What type of Logic App Is this happening in?

Standard (VSCode)

Are you experiencing a regression?

No response

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

Screenshots or Videos

Environment

Issue is in latest vs code request
VSIX version: 5.273.0
Bundle version:1.161.3

Additional context

No response

[takyyon]

AI Triage Analysis

Component: VS Code Overview / Runtime Check | Priority: P1 | SKU: Standard (VS Code, Non-public cloud)

Relevant Code

• apps/vs-code-react/src/app/overview/app.tsx — Overview page with runtime ping (lines 36-48)
• libs/designer-ui/src/lib/overview/overviewcommandbar.tsx — Run Trigger button disabled logic (line 62)
• libs/logic-apps-shared/src/utils/src/lib/helpers/run.ts — isRuntimeUp() function (lines 77-89)
• apps/vs-code-designer/src/app/utils/codeless/common.ts — getWorkflowManagementBaseURI() (lines 350-356)

Probable Root Cause

The Run Trigger button is disabled when !isWorkflowRuntimeRunning || !triggerName (overviewcommandbar.tsx line 62). The isWorkflowRuntimeRunning state is determined by isRuntimeUp(baseUrl) which makes an unauthenticated axios.get() to ${baseUrl}/operationGroups (run.ts line 83). For remote deployments, baseUrl is the ARM management URI (e.g., https://management.chinacloudapi.cn/.../hostruntime/.../management). This unauthenticated request will fail (401/403) on Mooncake's stricter endpoints, causing isRuntimeUp to return false and graying out the button.

The isRuntimeUp function was designed for local runtime checks (http://localhost:PORT/...) and does not pass authentication headers needed for remote ARM endpoints, especially in sovereign clouds where unauthenticated requests may be rejected more aggressively.

Suggested Investigation

1. Confirm whether isRuntimeUp succeeds for remote deployments in public Azure — if it does, investigate whether Mooncake ARM proxies behave differently for unauthenticated requests.
2. Consider passing the accessToken to the runtime check for remote (non-local) deployments, or skip the runtime-up check entirely for remote resources since the runtime is managed by Azure.
3. Check if triggerName is being resolved correctly for Mooncake deployments.

Similar Issues

No prior similar issues found for non-public cloud Run Trigger.

---

Automated analysis by issue triage agent. May contain inaccuracies — verify before acting.
Calibration: reviewed 4 past triage(s), 0 correction(s) applied.

[v-ksruthi]

Issue repro in latest vscode testpass
VSIX Version:5.273.0
Bundle Version:1.165.9