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

Loops add go to Prior/next error #1304

Open
tjohnson1010 opened this issue Feb 17, 2025 · 5 comments
Open

Loops add go to Prior/next error #1304

tjohnson1010 opened this issue Feb 17, 2025 · 5 comments

Comments

@tjohnson1010
Copy link

tjohnson1010 commented Feb 17, 2025

Describe the issue

When debugging a Run with any kind of loop, the loops have the option of a next or prior iteration. Can you add a go to next or prior error? Maybe use "<<" and ">>" for them. The idea if an iteration has an error, you can click the ">>" and it will go to the next iteration with an error. Right now, if you have 100 iterations, and one had failed, you will need to click through each one and wait to see if it was the one reported as an error.

Are you using new designer or old designer

New Designer (With action panels)

Screenshots or Videos

Image

Browser

Microsoft Edge for Business

Version 133.0.3065.69 (Official build) (64-bit)

Additional context

No response

@ccastrotrejo ccastrotrejo self-assigned this Feb 18, 2025
@ccastrotrejo
Copy link

ccastrotrejo commented Feb 19, 2025

Hi @tjohnson1010 thanks for letting us know about this issue. We do have a pager that goes directly to the failed iteration. I tried to reproduce your workflow using similar actions from your screenshot and was able to see the failed pager. We render the failed pager based on the data we get from an API call, so it might be that the API call is failing.

  • Is there any chance you can share with us the HAR file wile you load the run? Here is a small guide on how to get the HAR file
  • Is there any chance you can share your workflow.json?

You can share both items above to my email ccastrotrejo@microsoft.com

CleanShot.2025-02-19.at.11.48.22.mp4

@tjohnson1010
Copy link
Author

I sent you the Har and JSON for the Logic App.
FYI: The instructions to get ethe HAR are out of date for Edge.
Thank you.

Copy link

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

@github-actions github-actions bot added the stale label Feb 24, 2025
@tjohnson1010
Copy link
Author

I sent the requested information and updated this ticket saying I did. what else is there to do?

@github-actions github-actions bot removed the stale label Feb 24, 2025
@ccastrotrejo
Copy link

Hi @tjohnson1010 sorry for not replying earlier, I just had time to take a look at it. I looked at your HAR file, I will reply you by email

@ccastrotrejo ccastrotrejo transferred this issue from Azure/LogicAppsUX Feb 26, 2025
@ccastrotrejo ccastrotrejo removed their assignment Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants