thankyou for your response, but now it is solved, now it working fine.
thankyou for your response, but now it is solved, now it working fine.
@manojk2 this was skipped because what the condition or switch statement did not trigger it. You need to show the steps before for us to help fix the issue.
I'm also facing same issue, Automate showing successful but still showing this error.
This is just saying that the condition was not met. Sometimes it is a type conversion. You may check that a value is equal to 555,888 and it is comparing a string with a number ("555,888" is not 555,888). Before the condition use the compose function and set it to the item you are comparing. Then you can review the compose outputs to see what you are getting. In the case of the "Approved" the outcome may not be true, but the value "Approved" and so you would need to check it against that string, see image. Also this may need to be in an Apply to Each loop as it may come in an array, even though there is one (it used to). When I'm designing a flow I set everything I'm going to compare or parse so I can see exactly what it is. It saves time debugging later.
Hello
I am facing the same error. I have a flow to update my SharePoint list to new servicer, using an excel sheet. The condition is that if the SharePoint list's client code and branch code matches with the ones in excel and the stage is not equal to done(in SharePoint) replace the old servicer with new servicer. Somehow it is not satisfying with the condition.
Thank you!
why is my input expression recorded as "false" on the control designed to be "true" when the approval notification above is "accepted" via teams notification? It should state "True" when "accepted" as is not, kicking it to terminate or not complete the next step.
I am experiencing this as well. If I allow the "no" condition to be met, the flow terminates even if my condition is met w/ "approve" after completing and approving an approval. It always terminates out to the right as "successful, canceled, or failed" even though "approve" was selected and it should have proceeded down the "yes" route.
Placing "true" or "approve" in the flow condition makes no difference in the error occurring and reported as "false" in the test. Despite having actually approved the approval/condition and noting it should be "true", its not.
Did you ever find a solution to this issue? I am trying to send an email if a condition is equal to Yes as well. It seems to accept the condition but then stalls on that email.
Oh wait, I think I was misunderstanding and thought it was an error with the action itself, but I think I messed up my condition (checking category "equals" Blue category, instead of category "contains" Blue category).
WarrenBelz
146,653
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,999
Most Valuable Professional