hongzli
commented
3 years ago This is expected behavior. The "Next failed" button will jump to the next iteration that failed, while the "Next" button just goes to the next iteration. The purpose of this button is to speed up the investigation of failed iterations. For example, f you have 100 total iterations with a handful of failed iterations scattered throughout, it is much more convenient to click the "Next failed" button to jump to the next failure.
However, we appreciate the feedback and will work to design something more intuitive.
joechung-msft
I have created a single-tenant Logic App (Standard) workflow that uses a
Foreachloop. When executing the workflow both locally (using Visual Studio Code) and when deployed within the Azure Portal, the Run history window shows the error messages Next failed and Previous failed on the Foreach loop. The Foreach loop and all steps within the loop seem to have executed successfully. Also the rest of the workflow executes fine: