"HAM - Hardware Lifecycles" Scheduled Job Running for Excessive DurationIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The "HAM - Hardware Lifecycles" scheduled job is running for more than 18 hours before completing even with: A relatively small CMDB footprint.Minimal user activity.No known customizations related to the Hardware Lifecycles process. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Search for the "HAM - Hardware Lifecycles" scheduled job in the asset_job_log tableObserve the long-running executionsOpening one of the logs should display data like: LIFECYCLES_CREATED: 4 LIFECYCLES_DEACTIVATED: 0 ACTIVE_LIFECYCLES_PROCESSED: 6273031 DEACTIVATED_LIFECYCLES_PROCESSED: 762918 The above data will give insight into the amount of data being processed. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Zurich Patch 9 Hot Fix 3 Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When the HAM - Hardware Lifecycles job runs, it updates the asset_property record "com.sn_hamp.lifecycle.lastRunDate" with a date value:https://<instance_name>.service-now.com/asset_property.do?sys_id=fdf6b4a453d01010249addeeff7b127b&sysparm_record_target=asset_property&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=keySTARTSWITHcom.sn_hamp.lifecycle.lastRunDate The com.sn_hamp.lifecycle.lastRunDate property gives the date the HAM - Hardware Lifecycles scheduled job last ran. Assuming a previous execution completed successfully (regardless of the excessive duration), this value would be successfully marked with a date. That date value is supposed to serve as the delta value. The job then takes that value and queries over the sn_hamp_lifecycle_definition table and checks for the sys_updated_on value for the records:https://<instance_name>.service-now.com/sn_hamp_lifecycle_definition_list.do For all records with a sys_updated_on date that falls after the date in the asset_property record, these get processed. In a scenario where the sn_hamp_lifecyle_definition table isn't fully populated (likely because a full CDS Content pull hadn't yet been initiated for the "Download Hardware Content: Lifecycle CDS" job in the cds_client_schedule table), the execution would be quick for this run. In a scenario where the sn_hamp_lifecyle_definition table is fully populated, the job runs for an extended time. Sometimes the job may error or time out during the long execution. When this happens, records will be updated in the sn_hamp_lifecycle_definition table, but the job will never update the asset_property record "com.sn_hamp.lifecycle.lastRunDate" with a date value. Thus, the next run will not have a delta value to refer to, and will again attempt a fresh pull. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Assuming your Download Hardware Content: Lifecycle CDS job has already run and populated your HAM - Hardware Lifecycles table with data (Last updated on time should have a recent date):https://<instance_name>.service-now.com/cds_client_schedule_list.do Then you can re-run your HAM - Hardware Lifecycles job as this should run to completion.https://<instance_name>.service-now.com/sysauto_script.do?sys_id=7df6b4a453d01010249addeeff7b12a9 Assuming this still does not work, then your transaction quotas may need to be reviewed, see "Transaction quotas" documentation:https://www.servicenow.com/docs/r/platform-administration/platform-performance/c_TransactionQuotas.html