Look at the top right corner previous and next arrows. Also notice that you have 1 out 15 tasks to evaluate in the first condition. Refer to my prior post below where I put a pic of where I troubleshooted that. Why did the first condition failed? Most likely your values are incorrect. Thus the message is saying: 'We are not going to bother doing condition 2, since the prior action did not work', the prior action being that of listing the rows in excel. It also shows the FIRST condition, evaluated to false.Īs such if the condition evaluated to FALSE, the flow will continue in the NO option, but since you have nothing in there, it puts the error in the YES option. This helps other users find it more easily via search.Īs you can see all items on the YES branch failed (the grey 'X') next to each. If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. Let me know if that's something you've already addressed.but I didn't even think of it until I started building my own. I don't know what the fix is (To-Do?) but I'm sure one of the experts have already thought this through. Each run will add more and more rows (exponentially?) and this will get ugly fast. When it hits the 11th row, it will match again, and update that row, and then carry on until row 19. Each time, not finding a match, and each time adding a new row. Then, it will find the match, but keep going.

And in each of those 3, it will add a new row. If it is in there, but let's say 4 rows down, it's going to get a 'No' response 3 times before it hits the yes. When the Flow runs, it looks at the first task and asks 'Is this in the spreadsheet?' Let's say you've got 10 rows in your spreadsheet.If we use a condition to 'sync' things, it will play out like this, right: I just thought of something else, too, I think:

Microsoft task scheduler excel