"Closed by" field on Vulnerable Item is not populated during the auto approval processIssue ‘Closed by’ on vulnerable item is empty for VIs with risk rating ‘4 - Low’ & ‘5 - None’. Steps to Reproduce: Navigate to a Vulnerable Item record for which Risk rating is ‘4 - Low’ and State is not Closed.Click on ‘Close/Defer’ UI action.Select State as ‘Closed’ and Reason as ‘Result Invalid’.Click on Submit.Wait for 30 seconds and reload the form.Navigate to ‘Close’ section and you can view that ‘Closed by’ is empty.ReleaseAny VersionCauseCustomization in regard the execution of the workflow "WOW Vulnerable Item State Approval" in comparison with the OOTB functionality. The customer has configured the workflow on the approval record to trigger based on the conditions of the Workflow.In OOTB, we have a business rule "Begin state approval workflow" which will create the context for the VI approval.There is a race condition would have occurred between the execution of the BR "Update Vulnerabilities" and the workflow context execution.ResolutionCreated another Business rule similar to "Begin state approval workflow" and called their custom workflow sys_id(we can get from wf_workflow table).