Switch statement - The viewer doesn't match the designer
See original GitHub issueI’m still on 2.3.0-preview.58 so maybe fixed already:
Execution direction is fine as you can see the trail of green.
In the designer everything is looking great:


Once executed it’s not quite as happy in the instance viewer:

Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Why does my Switch-statement case not fire on exact string ...
I have tried removing the default case and added type-checks to the involved variables and it still simply does not match. I have...
Read more >[resolved] Why will my switch statement not work when ...
switch() takes a variable with string or number type. The case is a fixed value that the argument is matched against. This is...
Read more >Is it necessary to add the default case while using switch ...
It seems there are three cases when a default statement is not necessary: no other cases are left, because there is a limited...
Read more >Using switch(true) in JavaScript
You probably know that the switch statement allows matching an expression (the switch ) against different values (the case ), so using switch(true)...
Read more >Removing Switch-Case Statement and using Pattern ...
In this article, we consider how to remove switch-case statements from our code with OOP and Pattern Matching.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

seems to be working fine in the sample project (that rules out the browser). That probably leaves Blazor/different layouts/libraries that cause the problem. I’ll dig deeper later
Well, I switched the write line for JS as I don’t have those console activities ‘on’ It seems to exhaust rendering attempts:
I cant upgrade quite yet due to persistence errors: https://github.com/elsa-workflows/elsa-core/issues/1472
2.3.0-preview.58: It currently looks like
Updated switch (1).zip
Hopefully, the upgrade fixes it. It’s not causing any trouble for me though.