PowerShell code blocks don't load

[JDziurlaj]

Severity

Medium

Describe the Bug with repro steps

When loading a workflow that was originally developed in the Azure Portal containing an Execute PowerShell Code section in the VS Code extension, the source of the PowerShell script fails to load.

What type of Logic App Is this happening in?

Standard

Are you experiencing a regression?

No

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

ms-azuretools.vscode-azurelogicapps Version 5.230.15

Additional context

No response

[takyyon]

AI Triage Analysis

Component: VS Code Extension / Custom Code (InlineCode) | Priority: P3 | SKU: Standard (VS Code)

Relevant Code

• libs/logic-apps-shared/src/designer-client-services/lib/base/manifests/inlinecode.ts — Defines inlinePowershellManifest with operationType PowershellCode
• libs/logic-apps-shared/src/utils/src/lib/helpers/customcode.ts — getFileExtensionName() maps PowerShell to .ps1, generateDefaultCustomCodeValue() generates default PS scripts
• libs/designer/src/lib/core/actions/bjsworkflow/operationdeserializer.ts — Lines ~394-397: calls updateCustomCodeInInputs() to populate custom code from CustomCodeFileNameMapping
• libs/designer/src/lib/core/actions/bjsworkflow/initialize.ts — updateCustomCodeInInputs() reads file data from the mapping and sets customCodeData
• apps/vs-code-react/src/app/designer/app.tsx — Line 61: initializes customCode state from panelMetaData?.customCodeData

Probable Root Cause

When a workflow with Execute PowerShell Code is created in Azure Portal, the PS1 script source is stored as a separate file (not inline in the workflow JSON). During VS Code deserialization, operationdeserializer.ts calls updateCustomCodeInInputs() which reads from a CustomCodeFileNameMapping. If the VS Code extension host does not populate this mapping by reading the .ps1 file from the local project filesystem before passing it to the designer, the code editor will show empty/fail to load. The data flow is: VS Code extension reads files → passes customCodeData via panelMetaData → designer initializes the code editor. A gap in file reading or mapping between Portal-format and VS Code local project structure is the likely cause.

Suggested Investigation

1. Check how panelMetaData.customCodeData is populated in the VS Code extension host — verify the .ps1 file path resolution for Portal-created workflows
2. Verify the CustomCodeFileNameMapping contains the correct filename key matching what the workflow JSON references
3. Test with a workflow created natively in VS Code (vs imported from Portal) to confirm if the issue is Portal→VS Code migration specific

Similar Issues

• No closely matching open issues found

---

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