Parameters are lost when trying new Logix Apps Experience

[leoglaz]

Severity

P3 - Medium (Minor functionality affected)

Describe the Bug with repro steps

Expected Behavior:

• Existing Parameters are displayed, list is editable and parameters are referenceable in the workflow
  Actual Behavior:
• No parameters exist in the list

Steps to Reproduce:

• Create a stateful or Autonomous Agents workflow
• Add 1 one or more parameters
• Add 1 or more actions
• Click the Enable Preview button to use the new Logic Apps experience
• Check the parameters:

What type of Logic App Is this happening in?

Standard (Portal)

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

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "contentVersion": "1.0.0.0",
        "actions": {
            "Agent": {
                "type": "Agent",
                "inputs": {
                    "parameters": {
                        "deploymentId": "gpt-4.1",
                        "messages": [
                            {
                                "role": "system",
                                "content": "test"
                            }
                        ],
                        "agentModelType": "AzureOpenAI",
                        "agentModelSettings": {
                            "agentHistoryReductionSettings": {
                                "agentHistoryReductionType": "maximumTokenCountReduction",
                                "maximumTokenCount": 128000
                            },
                            "deploymentModelProperties": {
                                "name": "gpt-4.1",
                                "format": "OpenAI",
                                "version": "2025-04-14"
                            }
                        }
                    },
                    "modelConfigurations": {
                        "model1": {
                            "referenceName": "agent"
                        }
                    }
                },
                "tools": {},
                "runAfter": {},
                "limit": {
                    "count": 100
                }
            }
        },
        "outputs": {},
        "triggers": {
            "When_an_HTTP_request_is_received": {
                "type": "Request",
                "kind": "Http"
            }
        }
    },
    "kind": "Stateful"
}

Screenshots or Videos

No response

Environment

• Browser: Microsoft Edge for Business Version 146.0.3856.84

Additional context

No response

[github-actions]

AI Triage Analysis

Component: designer-v2 / Portal integration | Priority: P3 | SKU: Standard (Portal)

Relevant Code

• libs/designer-v2/src/lib/core/parsers/ParseReduxAction.ts:67,103 — Destructures parameters from workflowDefinition and calls updateWorkflowParameters(parameters ?? {}, dispatch). If parameters is undefined, initializes with an empty object.
• libs/designer-v2/src/lib/core/actions/bjsworkflow/initialize.ts:121-128 — updateWorkflowParameters maps raw parameter entries and dispatches initializeParameters to the Redux store.
• libs/designer-v2/src/lib/core/state/workflowparameters/workflowparametersSlice.ts:23-28 — Initial state has definitions: {}. Parameters only populate if initializeParameters is dispatched with a non-empty payload.
• apps/Standalone/src/designer/app/AzureLogicAppsDesigner/laDesignerV2.tsx:153-177 — Reference impl: parameters are loaded from Artifact.ParametersFile (parameters.json) separately, stored in currentParameters, then passed as workflow.parameters to BJSWorkflowProvider.

Probable Root Cause

In Standard workflows, parameters live in a separate parameters.json file (not inside the workflow definition). The v2 designer (BJSWorkflowProvider) depends on callers passing a workflow.parameters prop — if the Portal's "Enable Preview" flow constructs the workflow object without fetching and including that separate parameters file, ParseReduxAction.ts receives parameters = undefined, defaults to {}, and the parameters panel appears empty. The v1 designer likely fetches parameters from a different path and that fetch isn't replicated in the v2 integration.

Suggested Investigation

1. Confirm whether the Portal passes parameters in the workflow prop when mounting the v2 BJSWorkflowProvider. Add a temporary log or breakpoint at ParseReduxAction.ts:67 to inspect the workflowDefinition.parameters value on load.
2. Compare the Portal's v2 designer initialization code with the standalone reference in laDesignerV2.tsx:153-177 to verify the parameters.json (or equivalent ARM resource) is fetched and passed to BJSWorkflowProvider.

Similar Issues

No exact duplicates found.

---

Automated analysis by issue triage agent. May contain inaccuracies — verify before acting.
Calibration: reviewed 10 past triage(s), could not verify developer corrections (comments not accessible in this run).

Generated by Issue Triage Agent for Azure Logic Apps UX for issue #9022 · ◷