Query on glide.cmdb.sysObjectSource_cleanup Property and Stale records in sys_object_source table<!-- /*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: ; } } Q1: Do we have logic to remove stale records in sys_object_source table? No we do not. See question 3 for a better explanation.Q2: What value should property "glide.cmdb.sysObjectSource_cleanup" be set to to not cause any issues on the instance?The glide.cmdb.sysObjectSource_cleanup property is not used to remove the stale records in sys_object_source. CMDB Sys Object Source Cleanup" is a standard Scheduled Script Execution, defined in sysauto_script is a sys_object_source cleanup job to remove INVALID records, not stale records. When certain tables delete a record there is no business rule to delete the corresponding sys_object_source record (cmdb_sam_sw_install being a common violator). As a result there is a record in sys_object_source that has a doc id reference to a record in cmdb_sam_sw_install that doesn't exist anymore. This record is invalid and needs to be deleted. This is what the scheduled job and property is for. This property will not effect removing stale records. For more information on tuning this (even though it won't effect stale records) there is KB1198927Q3:Why do we persist sys_object_source for records that are not used for licensing and will never be used as part of sys_object_source lookup? Stale records are still important and shouldn't necessarily be deleted. As an example of why these records could be important;Let's say that a discovery source does differential pulls of data, let's say it is computer data. The first time that discovery source runs it will pull in all of the data, but after that initial run it will only pull in the data that has changed. Something like a server probably isn't changing very often. The hardware should remain the same, the operating and system software may not change frequently, etc. In this case the server record could still be actively used and supporting critical infrastructure but not changing. Therefore, Just from lack of inactivity doesn't mean that a source isn't actively still reporting a device. Also to mention all of the reporting, reconciliation, etc that multisource and the CMDB Workspace is based on sys_object_source and other related tables