Are switch cases in logic apps currently broken?

Question

Currently when I try to add a switch/case control block to a logic app in the designer it loads the switch block with no default case or extra case, with a warning saying "Error loading component.". If I try to copy an existing switch/case from one logic app to another through the code view, when saving I get
"Failed to save logic app <app name>. The request content is not valid and could not be deserialized: 'Required property 'case' expects a value but got null. Path 'properties.definition.actions.Check_Successful_Auth.actions.Check_If_Any_Clockings_To_POST.actions.Switch.cases.Case', line 1, position 11530.'."
Suggesting one of the cases is missing a "case" value to determine whether or not to use it, but all my cases apart from default have a case property, but the default doesn't (which makes sense since this route is selected if no other cases are).

This would suggest that the switch statement is currently bugged, requiring all cases to need a "case" property value including the default, but because the default doesn't (and shouldn't) have a case property value it won't let the app save, especially since the standard component won't load correctly in the designer which needs a default case as standard. Are switches bugged?

Answer 1

Seemed to be a user specific issue, colleague was able to add a switch in with no issues