Logic App Not Rendering Input and Output

Question

Logic App Not Rendering Input and Output

Andres Guzman (ALLYIS INC) 20 Microsoft External Staff

User's image

Is there an ongoing fix to this?

Andres Guzman (ALLYIS INC) 20 Reputation points Microsoft External Staff

2026-04-17T23:36:23.2233333+00:00

We are running Standard Logic Apps and have VNet integration enabled along with the appropriate authentication and networking configurations, all of which are functioning correctly. We are seeing this across all environments and workflows and it is not limited to any specific actions or document sizes. The data displays as expected when selecting raw inputs or outputs but having to repeatedly switch to a separate view to access this data slows things down during active development and debugging.
Rakesh Mishra 9,340 Reputation points Microsoft External Staff Moderator

2026-04-20T19:24:23.6+00:00
Hello Andres,

Thank you for the detailed clarification. Since the raw inputs and outputs load successfully, this confirms your VNet and storage configurations are correctly allowing your browser to fetch the artifacts. This isolates the problem directly to the Azure Portal's UI rendering component, which is failing to parse and display the formatted designer view for your Standard Logic Apps.

Given that this UI behavior is bottlenecking your active development and debugging across all environments, you can try below alternate to debug the workflows:

Visual Studio Code: For Standard Logic Apps, using VS Code with the Azure Logic Apps (Standard) extension is the optimal environment. It provides a native, responsive debugging experience where you can step through runs, view histories, and inspect inputs/outputs locally, completely bypassing the portal's web UI rendering quirks.

Azure CLI: To quickly validate run logic, verify execution details, or extract specific action outputs without navigating the portal, you can utilize the Azure CLI. Querying the workflow run history via CLI allows you to rapidly retrieve and parse the exact JSON payloads directly in your terminal.

Because this is a portal rendering issue affecting multiple environments in your tenant, I have reached out to you over Private message regarding some details. Please check and share the details.

Answer accepted by question author

0 additional answers

Your answer

Andres Guzman (ALLYIS INC) 20 Reputation points Microsoft External Staff

2026-04-17T23:36:23.2233333+00:00

We are running Standard Logic Apps and have VNet integration enabled along with the appropriate authentication and networking configurations, all of which are functioning correctly. We are seeing this across all environments and workflows and it is not limited to any specific actions or document sizes. The data displays as expected when selecting raw inputs or outputs but having to repeatedly switch to a separate view to access this data slows things down during active development and debugging.
Rakesh Mishra 9,340 Reputation points Microsoft External Staff Moderator

2026-04-20T19:24:23.6+00:00

Hello Andres,

Thank you for the detailed clarification. Since the raw inputs and outputs load successfully, this confirms your VNet and storage configurations are correctly allowing your browser to fetch the artifacts. This isolates the problem directly to the Azure Portal's UI rendering component, which is failing to parse and display the formatted designer view for your Standard Logic Apps.

Given that this UI behavior is bottlenecking your active development and debugging across all environments, you can try below alternate to debug the workflows:

Visual Studio Code: For Standard Logic Apps, using VS Code with the Azure Logic Apps (Standard) extension is the optimal environment. It provides a native, responsive debugging experience where you can step through runs, view histories, and inspect inputs/outputs locally, completely bypassing the portal's web UI rendering quirks.

Azure CLI: To quickly validate run logic, verify execution details, or extract specific action outputs without navigating the portal, you can utilize the Azure CLI. Querying the workflow run history via CLI allows you to rapidly retrieve and parse the exact JSON payloads directly in your terminal.

Because this is a portal rendering issue affecting multiple environments in your tenant, I have reached out to you over Private message regarding some details. Please check and share the details.

Answer 1

Rakesh Mishra 9,340 Microsoft External Staff Moderator

Hello Andres,

Please find the summary of issue and resolution discussed over MS Teams.

Issue: There was a regression bug in Preview portal of Azure which caused outputs and inputs to be not visible.

Resolution: We raised the issue to Product team via support request, and they fixed the UI bug and released it also. Also, you confirmed that issue is fixed now.

0 comments

Share via

Logic App Not Rendering Input and Output

0 additional answers

Your answer