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

Monitoring View: Actions under scope actions are greyed out #6484

Closed
vgouth opened this issue Jan 28, 2025 · 2 comments
Closed

Monitoring View: Actions under scope actions are greyed out #6484

vgouth opened this issue Jan 28, 2025 · 2 comments

Comments

@vgouth
Copy link

vgouth commented Jan 28, 2025

Describe the Bug with repro steps

  1. Create a consumption logic app or use existing logic app
  2. Open Designer
  3. Add http request trigger
  4. Add all the following scope actions

a. Condition

b. For Each

c. Scope

d. Switch

e. Until

5.Within the scope, add at least two actions (e.g., HTTP and Compose).

a. Condition - add actions to both True and False

b. Switch - add actions to a case and the default case

6.Save Logic app and run it
5. Open Monitoring view from logic app run
6. Expand the scope actions
7. In condition, switch and until scope actions, branches under these actions are greyed out but clickable.

Expected: Condition, switch and until scope actions, branches under these actions should not be greyed out.

Actual: Condition, switch and until scope actions, branches under these actions are greyed out but clickable. If this change is expected change, please note that the branches under these actions are overlapping with lines, which is not ideal.

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

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

Yes

Workflow JSON

Screenshots or Videos

Image

Image

Image

Browser

Edge

Additional context

Version: 2.50107.1.3

@ccastrotrejo
Copy link
Contributor

Hi @vgouth thank you so much for raising this issue. This issue was addressed in this PR #6408. It seems that the designer version we set on the current portal request doesn't have the fix yet. I will make sure to put that fix in.

@vgouth
Copy link
Author

vgouth commented Feb 3, 2025

Issue not repro in updated staging version
Version: 2.50203.1.1

Image

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

No branches or pull requests

2 participants