Approval State issue

[dmahendran]

I have a requirement to implement a three-level approval process in my catalog item: the first level is the manager, followed by two approval groups. However, I'm encountering an issue during the second level of approval. When the second-level approver rejects the request, the overall request state changes to "Cancelled" instead of "Rejected," and the first-level approval status also changes from "Approved" to "Cancelled."

Interestingly, when the rejection occurs at the third level of approval, everything works as expected—the request moves to the "Rejected" state, and the approval records from the previous levels remain unchanged.

Can someone please assist in identifying and resolving this issue?

[J Siva]

Hi @dmahendran 

Make sure that the approval rule on the second level approval is "Anyone approves or rejected".

Regards,

Siva

[dmahendran]

Tried that, but still cant able to find the solution. Just take a look at the attachment below.
Any other suggestion would be much appreciated!

[sahiltelani]

Hi @dmahendran,

Check if theres any script that's setting the state of your request to cancelled when you are rejecting the approval. 

Also, can you just send the ss of your flow? The part where you've configured second level of approval? 

[dmahendran]

I believe this might be an out-of-the-box behavior, as I couldn’t locate any custom script that sets the state to 'Cancelled' when the approval record is rejected. Just wanted to check—have you come across any OOB script that handles this scenario?. Attached the flow here.