Power Platform Community Forum Thread Details

Within a scope, had an Apply to loop that generated intentional, handled errors (checking for SharePoint Item Column type). This caused the loop to end with status 'Failed' (whatever). Since the Action after the loop hadn't been set to run on error, my Catch block (Run after Failed) was being invoked after the Try block.

I found this counterintuitive as I assumed that handling an error would not cause its parent to be marked as Failed. There's more nuance than that. Just sharing to spare someone else the research. Picture shows the bottom of the loop with three sequential actions (the first a Condition). Marking it to Run After Failed (and Success) fixed my issue.

While I'm on the topic, I have lots of Column names stored as configuration information in Items (just text). At runtime, I don't know what type of Column it is, which is problematic because it can contain a single value, multiple values, an object, or an array of objects. I use variable assignments with error handling to figure it out.

Anybody else have a better approach?

Categories:

Building flows

Thanks for the details you shared. I want to make sure I’m understanding your setup correctly before anyone tries to offer solutions.

Are you building this as a child flow that will be called by other parent flows, where the parent passes in the column names and values at runtime? That would explain why you don’t know the field types in advance, since a child flow doesn’t have access to the SharePoint list schema and can only work with whatever JSON it receives.

If that’s the case, could you clarify how your parent flow selects the fields and what the overall use‑case is? Understanding whether this is part of a reusable helper flow (for validation or error checking) will help others give you more targeted suggestions.