-
Notifications
You must be signed in to change notification settings - Fork 308
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
Comments
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.
You can share both items above to my email ccastrotrejo@microsoft.com CleanShot.2025-02-19.at.11.48.22.mp4 |
I sent you the Har and JSON for the Logic App. |
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. |
I sent the requested information and updated this ticket saying I did. what else is there to do? |
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 |
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
Browser
Microsoft Edge for Business
Version 133.0.3065.69 (Official build) (64-bit)
Additional context
No response
The text was updated successfully, but these errors were encountered: