Flow failed/succeded control when concurrent loop is being used
I have a flow where a few dozen Teams adaptive cards are being sent to O365 group users. It's as simple as pulling a list of users from the group and running some logic in a loop.
In this logic an actionable adaptive cards are sent to each Teams user belonging to the group and flow threads are waiting for an answer for a specified amount of time (send card and wait).
Loop concurrency settings are set to allow for a parallel execution.
Despite all run after error cases (timeout, error) being handled properly by having dedicated flow branches for handling exceptions, the parent flow is marked as failed each time at least a single timeout is logged. Even if such timeout event has been handled properly in the flow.
Is there a way for me to control the status of the flow while using parallel loops? I want it to be set to failed only when there were unhandled errors, or when I say so.