[XMLvaliationintegration][Bundle]: The Response 1 action settings disappear after we debug and run the workflow .

[v-ksruthi]

Severity

P1 - Critical (Blocking production)

Describe the Bug with repro steps

Repro steps:

1. Install VSIX version 5.273.0.
2. Create a logic app workspace and start a new project.
3. Set up the Bundle version and URL in host.json and localsettings.json.
4. Open the designer.
5. Add an HTTP request trigger, XML validation, Response, and a parallel action as response 1.
6. In XML validation, for the content to validate, select the property token as 'body', set the source to integration account, and choose the address.xsd file.
7. Configure the Response action with a status code of 200.
8. Create a parallel response action with a status code of 400. For the body, use the "body" token from XML validation. In settings, under "Run after," select "Has failed" and uncheck "Is successful." 
9. Save the workflow.
10. Click debug.
11. Launch Insomnia.
12. Choose "Post" and enter the workflow runtime URL. In Insomnia, select body > raw, and add valid XML.

Expected Result: Status in Insomnia should be 200. The run should appear as successful in the run history, the response action should be successful, and response 1 action should be skipped.

Actual Result: Status in Insomnia is 200. The run is successful in the run history, but both response action and response 1 action are shown as successful, and the response 1 settings have disappeared from the workflow.

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

XMLintegration.zip

Xmlvlidationfailure.zip

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: Serialization / VS Code Designer | Priority: P1 | SKU: Standard (VS Code)

Relevant Code

• libs/designer/src/lib/core/actions/bjsworkflow/serializer.ts — runAfter serialization (lines 454-457, 661-669)
• libs/designer/src/lib/core/actions/bjsworkflow/serializer.ts — removeRunAfterTriggerFromOperation (lines 1459-1465)
• libs/designer/src/lib/core/actions/bjsworkflow/settings.ts — runAfter settings handling

Probable Root Cause

The issue involves a parallel Response 1 action configured with custom "Run after" settings (only "Has failed" selected). After debugging, the action settings disappear. This likely involves the workflow serialization/deserialization cycle. When the workflow is saved and the runtime processes it, the serializer at line 661-669 (getRunAfter) reconstructs runAfter entries using idReplacements. If the parallel action's ID or its predecessor's ID is not correctly tracked in idReplacements, the runAfter configuration can be lost during re-serialization. Additionally, the removeRunAfterTriggerFromOperation function (line 1462) deletes runAfter entries pointing to the trigger — if the parallel Response 1 action is incorrectly identified as having a trigger runAfter, its settings could be stripped.

The fact that both Response and Response 1 show as "successful" (when Response 1 should be "skipped") suggests the runtime is also not honoring the runAfter conditions, indicating the serialized workflow definition may have already lost the "Has failed" condition before reaching the runtime.

Suggested Investigation

1. Capture the workflow JSON after save (before debug) and after debug — compare the runAfter block of the Response 1 action.
2. Check if the parallel action's runAfter entry is preserved through getRunAfter() in the serializer, particularly the status conditions array (e.g., ["Failed"]).
3. Test with the v1 (non-experiment) designer to determine if this is a serialization issue or a runtime bundle issue.

Similar Issues

No prior similar issues found matching this specific pattern.

---

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

Xmlval.zip