Configuration Compliance: Remediation Tasks are not resolved even after resolving it

sath
Tera Expert

‎03-18-2026 10:22 AM

Hi,

 

We have implemented configuration compliance on our lower instance and kept everything OOB, haven't made any customizations. I have clicked resolve button on remediation task (which was on awaiting implementation state) and input the resolution notes and then the form loads and the state still shows awaiting implementation.

The active field on record shows false but the state still reflects awaiting implementation. I have checked business rules, client scripts, UI actions and don't find any discrepancies. 

Also, state field on test result record is not editable and only assigned to and assignment group are editable. Is that the expected behavior? So, the only way to close the test records is by closing the associated remediation task?

Appreciate any inputs on this.

 

 

0 Helpfuls
  • 405 Views
1 REPLY 1

cobiillian
ServiceNow Employee

yesterday

Hi!

 

Two things:

  1. Did you reload the form manually to verify the state is not advancing to Resolve? 
  2. To your second point, it is expected and by design that the fields are mostly read-only. In summary, 

    Test results in CC are scan-driven artifacts — they represent the result of a policy test against a CI from the SCA scanner. The state reflects ground truth from the scan, not a workflow you can manually drive. That's why only assignment fields are editable; assignment is a workflow concern, state is a data concern.

    The closure path for test results is not "close the remediation task." Closing the rem task does not auto-close associated test results OOB. The actual closure paths are:

    • Next SCA scan re-tests the CI and returns pass → test result state updates to closed
    • An exception is applied → the test result is effectively suppressed for remediation purposes
    • The CI drops out of scope (decommissioned, group membership change, etc.)
0 Helpfuls