Frequent job run for CloudResourceDashboard scheduled job is causing high CPU on the DBIssue Scheduled jobs for Cloud Resource Dashboard are causing high CPU on the DB and this is set to repeat every 30mins but the job runs for a longer time. List of scheduled jobs in Cloud Resource Dashboard: 1. AWSResourcePopulateScheduledJob2. AzureResourcePopulateScheduledJob3. VMwareResourcePopulateScheduledJob Example of failure in system logs:worker.1 txid=2c8e5ac5dbf4 SEVERE *** ERROR *** sn_disco_cd: AzureResourcePopulateScheduledJob with sys_id: 248e5ac5dbf4745c31df7a43e2961996 failed. Job exceeded the max allowed timeCause1. There might be large number of records (lets say 'N' records) in the cloud resource tables for a given cloud provider.2. By default, timeout for Scheduled jobs mentioned above is 120 mins, i.e., 2 hours. And the scheduled job interval is 30 mins. If any job is in running active, the next job will not be triggered (it's the functionality).3. As the number of records to be processed by the scheduled job is more, the scheduled job starts processing these 'N' records.4. The scheduled job is not successfully completed within 2 hours. It gets timed out. No data in 'N' records is processed.5. So after failing in this scheduled job run, it get re-triggered in next 30 mins.6. When it re-triggers, its processing the records from the beginning, i.e., it processes 'N' records.7. This loops continues forever and so the DB is having regular load (as it is processing the same number of records).So if we increase the scheduled job timeout, it will be able to process all 'N' records in one go instead of retrying it again and again. Once all the records are processed for one time, for next time there will be lesser records to process and it will not get timed out.ResolutionGo to 'System Properties'.Search for 'sn_disco_cd.scheduled_job_time_out_in_mins'.You would notice, it's default value to be '120' in mins.You can increase it to '360' mins (6 hours) and re-trigger the AzureResourcePopulateScheduledJob scheduled job.This will be for only one job run so that it completes. After the job succeeded it can be reverted to default 120 mins as only the delta are picked in the next runs.Related LinksQ) If in future we add new Cloud accounts in Cloud Discovery for AWS or Azure, should we expect similar issues with these jobs?A) You don't have to increase it the next time. We suggested you to increase the timeout because this issue mostly occurs only during for the first run because we might have a large number of CIs to process it.Once the schedule job runs successfully, subsequent jobs will not look for all records but only for those records which has been updated between the present and last job run time (the delta records).Enhancements in July 2022 release1. In the previous release, records are individually inserted/updated into cloud analytics table. In July 2022 release, records are inserted and updated batch wise. The batch size is fetched from glide.db.max_view_records system property that is defaulted to 100002. If a scheduled job times out while processing N number of records, the next job would process the records from beginning. In July 2022 release, the next job starts from the table where last job was ended3. The value of sn_disco_cd.scheduled_job_time_out_in_mins system property is changed from 120 minutes to 360 minutes