Even approver has not approved it is showing "No longer required" nothing is configured for that

Prathamesh Chav
Tera Contributor

Hi Team,

 

We have flow for RITM in which after submitting RITM we are sending 1st level approval and if that gets approved we are sending 2nd level approval and its a group approval, only anyone from the group approves then task should get created,

Issue here is for few RITM's task is getting created even though the 2nd level approval is not approved, showing the status "No longer required" showing updated by system.

but when we see the flow context it is showing approval completed true

 

Attaching screenshot

PrathameshChav_0-1739193353611.png

 

 

Thanks

 

 

5 REPLIES 5

Jon Hogland
Tera Guru

Hi Prathamesh. I just recently worked on another question that had a very similar issue. You can see that post here: https://www.servicenow.com/community/workflow-automation-forum/question-regarding-quot-flow-designer...

Based off the information you've given, I suspect your issue is caused by the same item. In your test execution log, check to see if the value of the approval is being set to 'cancelled'. If it is, I'm 99% sure it's caused by the [task] business rule "Moot Approvals Upon Cancellation." Test disabling that BR and then see if your flow waits for approval appropriately.

For a more detailed explanation of the above, please review the post I've linked. I hope this is helpful for you. If not, let me know and I'm happy to look into it further!



If I've at all helped, please return the favor by clicking the thumb next to my post. Thanks!

Hello Jon

Thanks for the response.

I checked the Output data, value of the approval is not set to 'cancelled'.

 

rajjconsult_0-1739197594158.png

 

If you disable the BR "Moot Approvals Upon Cancellation", does it change any of the flow's behavior?



If I've at all helped, please return the favor by clicking the thumb next to my post. Thanks!

Prathamesh Chav
Tera Contributor

Hello Jon

 

We can disable the BR , But we can not test the behavior of the flow. because there are only two ticket which showed this behavior and other ticket are working fine as expected.