Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logic App designer "save" button not gray even saved successfully #5682

Open
huidongl opened this issue Sep 16, 2024 · 1 comment
Open

Logic App designer "save" button not gray even saved successfully #5682

huidongl opened this issue Sep 16, 2024 · 1 comment
Assignees

Comments

@huidongl
Copy link

huidongl commented Sep 16, 2024

Describe the Bug with repro steps

Whenever customer open the workflows in Standard Logic App, the save and discard button is always enabled even if customer already saved it successfully and didn't make any changes.

Customer save the workflow and it had a "successfully saved workflow" notification. And the "save" and "discard" button became gray

Customer click any other blade such as "overview" and then click the designer to get back to the designer view again, the "save" and "discard" button are enabled again. If customer now click another blade, it will have a warning that you have something unsaved, but actually we didn't make any changes to the code.

We made comparison for the code view when the save button was gray and not gray, and the code are exactly the same.

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

No response

Screenshots or Videos

image

image

Browser

Edge, I am attaching the two workflow JSON after save successfully and re open the designer

workflow1.json

workflow2.json

Additional context

No response

@Elaina-Lee Elaina-Lee self-assigned this Sep 16, 2024
@huidongl
Copy link
Author

May I know if we have any update on this issue? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants