ServiceNow - QRadar Stuck in Running StateIssue If nodes get restarted and your QRadar Profile becomes stuck in a "Running' state, you can follow the steps below to reconcile the scheduled job.CauseThe QRadar Profile contains the Schedule for the import for the Offenses. If you navigate to the Outbound HTTP logs, you no longer see the API Path for /api/siem/offenses You have verified all plugins and dependent plugins are installed. You see that Nodes have been restarted during the time of your outage (Node restarts can be seen by going to stats.do and looking for the 'Started' value) ResolutionNavigate to the QRadar Profile stuck in a 'Running' stateOpen the Profile and Export to XMLOpen the XML and set 3 fields:--- state: waiting--- next_poll_time: set this to 5-6 minutes in the future--- active: falseImport the XMLSet the Profile to 'Active' Wait for 60-90 seconds after the trigger time and then verify you see records being created