Start Flow Launcher is leaving huge queries to the database, and "Populate Unassigned resources count" is firing bad query causing long running job "Cloud Event Scheduler". - Known Error

Start Flow Launcher is leaving huge queries to the database, and "Populate Unassigned resources count" is firing bad query causing long running job "Cloud Event Scheduler". Description Issues:

The 'Populate Unassigned resources count' script is firing bad query and causing long running job "Cloud Event Scheduler". Long running queries triggered from OOB BR 'Start Flow Launcher' impacting database performance. Root Cause: Every time after discovery is complete, the 'Populate Unassigned resources count' sys event is triggered. The event queries CMDB CI tables. If the tables contain a huge amount of data, the query is causing performance issues.

Applicable from 4.0.x release onwards.

Steps to Reproduce

Issues are detected after the following plugins are activated: 1. Tag governance (sn_itom_tag) 1.1.3 2. Cloud Insights Azure (sn_clin_azure) 4.0.0

Workaround Follow these steps to disable the 'Populate Unassigned resources count' sys event.

Go to the sysevent_script_action table. Select 'Populate Unassigned resources count'. Deselect the Active checkbox and select Save. The above script runs everyday at midnight, so there will not be any functional impact.

For Long running queries triggered from OOB BR "Start Flow Launcher" impacting DB performance, indexing is done for cmdb_ci tables by the Support team.