Completing control tests with 'success' is saving with incorrect value of '3' when saved first time.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Control tests are not saving with correct value when saved first time. If a control test is completed with a state of 'Success', after saving the record, the status goes to "3" on the first save, and then when saved again goes to "complete". TO REPRODUCE: Go to any control test definition.Select "execute now" and create a new control test instance, then navigate to the control test instance which will be at the state of pending. Change the state to "success" on saving it changes to "3" if you then select success and save again it stays at success. Expected Behavior: After Completing the Control Test, the State field should show 'Success' ( Value : 650) Release Jakarta Cause Identified this is caused by OOTB 'Task Closer' BR which has been defined with Action: Set State to Closed Complete https://xxxxxxxxxx.service-now.com/nav_to.do?uri=grc_control_test.do?sys_id=ff3424e5db5d37405e47cc2c0b9619f2 Debug Extract: business rule13:38:12.502: Execute before update business rules on grc_control_test:CTST0010074 before engines (order <1000) business rule13:38:12.503: Global ==> 'Task Active State Management' on grc_control_test:CTST0010074 log13:38:12.504: : CTST0010074: State changed (Pending->Success), setting task to inactive business rule13:38:12.504: Global active: 1 => 0 business rule13:38:12.504: Global <== 'Task Active State Management' on grc_control_test:CTST0010074 business rule13:38:12.510: Global ==> 'Set Close Data on Inactive' on grc_control_test:CTST0010074 business rule13:38:12.523: Global work_end: => 2019-05-08 12:38:12 business rule13:38:12.523: Global <== 'Set Close Data on Inactive' on grc_control_test:CTST0010074 business rule13:38:12.532: Global ==> 'Update Planned Date from Current' on grc_control_test:CTST0010074 log13:38:12.532: : Updating Planned Dates from current dates - WorkStart -> business rule13:38:12.533: Global <== 'Update Planned Date from Current' on grc_control_test:CTST0010074 business rule13:38:12.534: Global ==> 'task closer' on grc_control_test:CTST0010074 business rule13:38:12.534: Global state: 650 => 3 business rule13:38:12.534: Global u_status: 1 => 5 business rule13:38:12.534: Global <== 'task closer' on grc_control_test:CTST0010074 13:38:12.590: Global ==> 'Set Closure Fields' on grc_control_test:CTST0010074 This BR is set to run based on certain conditions which were met when the Control Test Instance was closed e.g. Active is False Active Changes from True see below screenshot Resolution Review the current conditions on the Br: Task Closer Modify the conditions so the BR does not run on this task, for e.g. you may want to add a condition based on Task Type.