Discard button not functioning as intended

[vgouth]

Describe the Bug with repro steps

1. Create a standard logic app
2. Add stateful workflow
3. Open designer
4. Add http request trigger
5. Save the workflow
6. Now confirm the pop up whether the workflow is saved or not
7. Once the workflow is saved add one action of your choice, I am taking response action in this case
8. Now verify both save and discard buttons are enabled after adding response action
9. Click on discard button

Expected: Actions added after the workflow is saved should be removed when the discard button is clicked.

**Actual:**We have a HTTP request trigger in the workflow that is already saved. Now, we have added a response action which is not saved. When we click the discard button, it deletes the entire workflow instead of just the response action. To retrieve the saved workflow, we need to either refresh the Azure website or switch from the designer to another blade and then back to the designer blade which is not the correct way.

What type of Logic App Is this happening in?

Standard (Portal)

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

https://github.com/user-attachments/assets/409a104a-cc89-40f6-90e9-67060aa5eb0d

Browser

Edge

Additional context

Version: 2.50224.1.3

[vgouth]

Issue repro in latest stating test pass in consumption portal as well

Version: 2.50324.1.5

[vgouth]

Issue repro in canary test pass Version: 2.0.20250408.2

[ccastrotrejo]

This will be fixed in the next version of portal

[vgouth]

@ccastrotrejo Issue repro in latest stage test pass. We have a HTTP request trigger in the workflow that is already saved. Now, we have added a action which is not saved. When we click the discard button, it deletes the entire workflow instead of just the response action. To retrieve the saved workflow, we need to either refresh the Azure website or switch from the designer to another blade and then back to the designer blade which is not the correct way. This issue repro only for the first time when a workflow is created in standard logic app. once we switch from designer to another blade and come back to designer then discard is functioning as expected. Somewhere the workflow is not getting updated in the backend fastly. Request to re-open this issue

Version: 2.50522.1.3

dicardnotfunctiong.zip

[ccastrotrejo]

Hi @vgouth thanks for letting me know this. We have fixed the issue, but unfortunately, the fix caused a regression. As a result, we decided to revert the changes. The issue will still be present, but I am working on a new fix.

[vgouth]

@ccastrotrejo . Thank you for the update. Issue repro in canary test pass Version: 2.0.20250604.1

[vgouth]

@ccastrotrejo Issue repro in latest stage test pass. Version: 2.50616.1.1

[vgouth]

@ccastrotrejo Issue repro in latest stage test pass. Version: 22.50707.1.2

[vgouth]

@ccastrotrejo Issue repro in latest canary test pass Version: 2.0.20250724.4

[vgouth]

@ccastrotrejo Issue repro in latest staging test pass Version: 2.50725.1.1

[vgouth]

@ccastrotrejo Issue repro in latest staging test pass Version: 2.50808.1.1

[v-ksruthi]

Issue repro in latest staging test pass Version: 2.50818.1.2

[vgouth]

@ccastrotrejo Issue repro in latest canary test pass. We have a HTTP request trigger in the workflow that is already saved. Now, we have added a action which is not saved. When we click the discard button, it deletes the entire workflow instead of just the response action. To retrieve the saved workflow, we need to either refresh the Azure website or switch from the designer to another blade and then back to the designer blade which is not the correct way. This issue repro only for the first time when a workflow is created in standard logic app. once we switch from designer to another blade and come back to designer then discard is functioning as expected. Somewhere the workflow is not getting updated in the backend fastly. Version: 2.0.20250904.2

[vgouth]

@ccastrotrejo Issue repro in latest canary test pass. We have a HTTP request trigger in the workflow that is already saved. Now, we have added a action which is not saved. When we click the discard button, it deletes the entire workflow instead of just the response action. To retrieve the saved workflow, we need to either refresh the Azure website or switch from the designer to another blade and then back to the designer blade which is not the correct way. This issue repro only for the first time when a workflow is created in standard logic app. once we switch from designer to another blade and come back to designer then discard is functioning as expected. Somewhere the workflow is not getting updated in the backend quickly.

Version: 2.50912.1.1

[v-ksruthi]

Isse repro in latest canary testpass Version:2.0.20251006.2

[v-ksruthi]

Issue repro in latest stage environment Version:2.51008.1.2

[v-ksruthi]

Issue repro in latest stage environment Version:2.51029.1.5

[v-ksruthi]

Issue repro in latest stage environment Version:2.51208.1.1