No longer required State is stopping flow to execute further

[MahiM4999578481]

In Flow Designer Ask For Approval, when sysapproval_approver state becomes No Longer Required, how can the action be resumed? Is there any supported mechanism similar to Workflow's skipped/activity.result behavior?"

in this scenario if the state of Approval of user B changes to No Longer Required then the flow stop executing further and I'm not able to see approval for user C.

[Mark Manders]

How have you configured it? Because if A and B are asked for approval and only one of them has to approve, this is expected behavior. It's your (work)flow that should show what needs to happen after A's approval.

[MahiM4999578481]

When A approves, B receives the approval. At that point, if I manually change B's sysapproval_approver.state to No Longer Required, the Flow Designer Ask For Approval action never resumes, so approval for C is never created.

I understand that Approved, Rejected, and even Cancelled allow the flow to continue, but No Longer Required seems to leave the Ask For Approval action waiting indefinitely.

My question is whether this is the expected behavior in Flow Designer, and if there is any supported way to resume the Ask For Approval action after setting the approval to No Longer Required, similar to Workflow's activity.result = skipped behavior.

I

[Mark Manders]

Yes. Because 'no longer required' is not an outcome. It means 'don't look at this anymore' and your flow doesn't. Why would you update an approval manually to 'no longer required' when it is required? Your process says 'if a approves, b needs to approve and then c' and you intervene by setting b to 'no longer required'. If it doesn't matter what b does, it shouldn't be in there at all. Just go straight to c.