Apply to Each Not Actually Failed

[trentbooks]

CONTEXT

Users can submit a form on our website that pipes values into Power Automate. These values are then sent to another website via an HTTP API call to do fancy stuff.

One of the form values is free form text, but should have a number in it (I can't change this field to require numbers only for "reasons"). I use the split function on the input as a whole to chunk the string into various parts, then loops through the parts using Apply to Each to see if I can convert the value into a float value.

ISSUE

The string could say anything. For example: "The number 4 is what I'm looking for." When I loop through the array produced by the split function, Apply to Each produces these results:

The - fail

number - fail

4 - success

is - fail

what - fail

I'm - fail

looking -fail

for. - fail

For me, this is actually a success because it found "4" and successfully converted it to a float/numeric value. But Power Automate considers this a fail.

WHAT I WANT

Without changing my approach (like...I'm not interested in completely overhauling the flow to do this totally different...it's a somewhat complex flow overall and I just want to solve this one issue) - How can I get Power Automate to only show "Failed" when ALL Apply to Each attempts were failures? Like, if even one succeeds, then it's logged as a success?

Here are a few screenshots to show what I have. And yes, writing with a mouse is as terrible as it looks. 🙂

[jeiland]

By chance, have you solved this? I have a similar issue (my Apply to Each has a condition that is matching a record and then updating accordingly, so it will have 1 success and several failures, but the action is a success) and it's deeply annoying.

[trentbooks]

Unfortunately not. I basically just do the same chunk of code in both places where possible:

So I keep trying logic patterns to address edge cases, but it still shows as a failed run.

The one call out that makes this still a success is this part:

I increment the index and then check if the index is out of bounds...if it is, that's when I proceed to execute based on what I have.....but it *still* shows as a failure. Ugh.

[jeiland]

So frustrating - thanks for sharing your updates. I tried to create a Terminate action that would show it as a success, but you can't run a Terminate action within an Apply to Each, so I can't connect it to the success or failure of the Update actions. Hopefully this will be solvable at some point - you'd think there's be a way to say "if *any* of these succeed, mark as a success" rather than "If all succeed."

[Chriddle]

I definitely recommend changing the approach 😉

However, this might help to get your number:

Select:

 "inputs": {
        "from": "@split(outputs('Compose'), ' ')",
        "select": "@if(isInt(item()), item(), '')"
    }

Compose 2:

{
	"isSuccess":@{greater(length(join(body('Select'),'')),0)},
	"value":@{if(greater(length(join(body('Select'),'')),0),int(join(body('Select'),'')),Null)}
}

Result:

{
  "isSuccess": true,
  "value": 4
}