Control moves automatically to Retire when clicked on Attest UI actionIssue When the Control got to retire, it can be returned back to unretire means any other state rather than retire. This functionality is not working.ReleaseOrlando Patch 9bCauseA "control" record is a combination of 'Control Objective' and 'Entity'. If either one of those associations is changed then the control would be invalid and it should be set to a retired state.ResolutionThe controls were automatically created when an "entity type"(which contains group of entities) is added to the 'Policy' (which cascades down to 'control objective'). This can be confirmed by referring to the 'Created Manually' field in the control records associated with the 'control objective'. If the value is 'false' it was created automatically as mentioned above. So when the association breaks, (i.e) 'entity type' is removed, then the controls are no longer valid and would be set to 'retired'. When a new 'entity type' is added to the Policy, then a new set of controls would be automatically created associated the entities in the entity type and control objectives within the policy. This doesn't apply to manually create control records and that is the reason newly created controls aren't set to 'retired' when we move to the 'attest' state.