I get the following error/s (2nd image) when the "Start and Wait for an Approval" process times out. When it doesn't time out the same flow works without error.
For the "Approval Condition - No Time out" the configure run after is set to "Is Successful" & "Has Timed Out". I think it has something to do with the Responses Comments in the body of the Email and not being able to be found in the preceding Start and Wait for Approval process because it has timed out - but how can I resolve this please?
When action times out, you wont have Outcome. What is your goal if action times out? If you just want to worry about not timed out, add a condition to check if Outcome is not null first and then second condition can check if its false. So if it times out, it wont go inside and wont fail.
Thanks @PrasadAthalye when the Approval Times Out I want to basically skip that whole branch, I only want that branch to activate when the Approval succeeds, when it times out it goes successfully down the Escalation Branch.
Can you assist how I would add that condition to use to check for Null & False value please?
I think then its simple. Just remove has timed out from Run after. And escalation should only have has timed out.
Thanks @PrasadAthalye I had already tried that and it was still causing an error going down the "No" path. I think I have now resolved anyway by using 'Terminate' action. Thanks for your help.
Ok. I thought you mentioned that you wanted to continue on escalation path. Note that Outcome is null when timed out. So as long as you are not using any property from Approval action, it should not fail.