Security Operations Threat Lookup does not run, or capability executions stay in Queued state, after adding an observableIssue After an observable is added to a Security Incident, the Security Operations Threat Lookup capability does not run. Running Threat Lookup manually from the observable record also fails. The Threat Lookups and Threat Lookup Results related lists stay empty. Depending on the instance, one of the following is seen: No Capability Execution (sn_sec_cmn_capability_execution) record is created.A Capability Execution record is created but stays in the Queued state and never completes. The Threat Lookup capability, the integration implementation (for example, VirusTotal) and the Threat Lookup flow are active and match the out-of-box configuration. Symptoms After you add an observable to a Security Incident, the Threat Lookups and Threat Lookup Results related lists stay empty.Running Threat Lookup manually from the observable record also does nothing.Depending on the instance, one of these is seen: No Capability Execution (sn_sec_cmn_capability_execution) record is created.A Capability Execution record is created but stays in Queued state and never completes. The Threat Lookup capability, the implementation (for example, VirusTotal) and the Threat Lookup flow are active and match the out-of-box configuration. Release All Cause The Threat Lookup flow depends on two scheduled records. If either is missing or inactive, Threat Lookup stops working, with a different symptom in each case. Missing scheduled trigger "Threat core events process": This trigger ships with Threat Intelligence Support Common and processes the sn_ti_queue event queue. Without it, Threat Lookup events stay in the Ready state. The flow never starts, so no capability execution record is created.Inactive scheduled job "Process Capability Implementations": The flow starts and creates the capability execution record. With the job inactive, nothing processes the execution, so it stays in the Queued state. Resolution Scenario 1: No Capability Execution records are created The scheduled trigger Threat core events process is missing. It ships with Threat Intelligence Support Common and processes the sn_ti_queue event queue. Open the Threat core events process record (sys_trigger) on a healthy instance that has the same setup.Export the record as XML (right-click the form header > Export > XML (This Record)).Import the XML into the affected instance (System Definition > Load Update Set).Confirm the trigger is present and active. Scenario 2: Capability Execution records stay in "Queued" The trigger is present and the execution record is created, but the scheduled job Process Capability Implementations (sysauto_script) is inactive. Open the Process Capability Implementations scheduled job.Set Active to true and save.Verify that the queued capability executions are processed. Verification Add an observable to a Security Incident, or run Threat Lookup from the observable record.Confirm that the Threat Lookup API call succeeds.Confirm that the Capability Execution (sn_sec_cmn_capability_execution) record reaches Completed.