Approvals are getting deleted automatically on Requested ItemIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .title { color: #D1232B; font-weight:normal; font-size:28px; } h1{ color: #D1232B; font-weight:normal; font-size:21px; margin-bottom:-5px } h2{ color: #646464; font-weight:bold; font-size:18px; } h3{ color: #000000; font-weight:BOLD; font-size:16px; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> Symptoms Approvals are getting deleted automatically on Requested Item. Release Kingston and earlier Cause No approval records are returned when the workflow hits the approval coordinator the second time, so all the approval records are deleted. Resolution The second time the workflow hits the approval coordinator, the script inside the "Approval - group activity" returns no approvers. So when the there are no approvers returned for the second time, the workflow engine would assume that there should not be any approvers and so it goes and deletes all the approvers. This issue occurs since the same approval coordinator activity is being hit by the workflow for the second time. The behavior is present in Jakarta as well. This is an expected behavior. When we are hitting the same approval coordinator twice, and when we add the same approval group the second time, then the approval records will not be deleted and the workflow engine would know that approvers have already been approved and it would move to the next activity. But in our case, we are adding no approvers the second time, so the workflow engine would assume that there should not be any approval records and so all the approval records will be deleted.