This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 94%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
When debugging a Logic App Run online, a Switch action sometimes marks the Default as being ran with a green question mark instead of the case that was executed. I noticed this mainly when the switch is on a string that contains digits only. Attached is a screenshot.
@Thomas Johnson This is likely because of the types like you've mentioned. If the input is the string of a number, you need to compare against the expression string(204) instead of just 204. Or the other way of comparing the expression int(<token>) to the numbers the way you have now.
Your solution doesn't work. It will treat that as a literal, meaning it wants to see "string(204)" not "204". Current designer has "204" (with quotes) not 204 as value since the input is string. It does execute correctly; it just doesn't display correctly in the debugger.
Case statements can only take string literals, integers or a parameter. You cannot use expressions in a Case statement.
When I tried to use "@{string("string(204)")}". It produces the following error:
Failed to save logic app Test_Switch. The template validation failed: 'The template action 'Switch' at line '1' and column '414' is not valid: the value '@{string(940)}' specified for 'case' property in switch case 'Case' contains expressions that are not supported. Only a literal of type string or interger or a '@parameters()' expression can be specified for the 'case' property.'.
I've included a new screenshot to show more completely what I mean. Red arrow indicate the wrong icon is displayed and green arrow indicate the correct icon is displayed. This is when viewing a run not code editing.
@Thomas Johnson You are right about the values not supporting expression. I missed that.
So, you should be able to use int(<token>) for the on field and then compare against integer values which do work.
Here is the workflow that I tried against
and here is a test run
Thank you. This is a good "workaround" to getting the debug page to display correctly.
I still think the debug page should display correctly without us adding "extra" code.
@Thomas Johnson This has now been fixed. Here is a screenshot of a successful run
