Operation Errors - cases parameter errors ('Equals' is required)

[yuki-ACN]

Describe the Bug

As you can infer from the error text, there is probably a problem with the validation of the switch action of the control connector on 'designer'.

This error occurs when trying to save changes on the 'designer'. On the other hand, saving changes in the 'code view' does not occur it. The workflow itself can also be executed normally. In other words, we believe that the bug occurs only for changes made from the designer.

We did not see this bug until at least 8/10/2023 at midnight (JST); we just resumed work on 8/10/2023 at 9:00am(JST) and have encountered this bug.

Plan Type

Standard

Steps to Reproduce the Bug or Issue

As explained above.

Workflow JSON

Difficult to provide due to business critical workflow.

Screenshots or Videos

Additional context

If anyone have other reports like this, please share the information.

AB#24806354

AB#24835108

[ChrisDRiley]

Noticing the exact same error myself, even just initializing a new variable causes this error for me and I am unable to save.

[SimonAdaptiv]

Yes, I noticed the same on Friday. I saw the new Errors button after trying to save and thought that's pretty useful. Sadly, it just spun its wheels and the whole designer would no longer work i.e. I could no longer save. I worked around the issue by making changes in code view, which I don't need to say is very cumbersome.
Possibly the common factor is the workflow has a case statement somewhere.

[MalcolmKAdaptiv]

Editing a workflow with a case in VS Code Designer or Code View also does not work, it puts 2 sequential actions as parallel actions.

[hartra344]

@Eric-B-Wu i think this is like related to your conditional validation. Can we get this hotfixed asap?

[tonylevaggi]

I am also seeing this issue in the Logic App Designer. Making a change in a step that isn't near the switch-case block errors with the same 'equals' is required behavior

[Eric-B-Wu]

@Eric-B-Wu i think this is like related to your conditional validation. Can we get this hotfixed asap?

This was related to a change where we check the validation on every parameter before saving. This fix should have been fixed in Riley's earlier PR, https://github.com/Azure/LogicAppsUX/pull/3119, though we found another problem with that PR which we're looking to fix currently https://github.com/Azure/LogicAppsUX/issues/3128

[Eric-B-Wu]

We are currently hotfixing this change. Expect it to finish to all regions by EOD today

[Eric-B-Wu]

closing issue as its been deployed to all regions