cmdb_ci_automation records created after Australia upgradeIssue <!-- /*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: ; } } Following the upgrade to Australia, new records appeared in the cmdb_ci_business_process table, visible in the OpRes Workspace Business Process View. These records belong to the child class cmdb_ci_automation and their names match specific Service Catalog items used by the organisation, such as Account Move Request – Within a Hub (RoW), Access to Calendar, Access to Mailbox, Admin Account Password Reset, and Audit – Access Review. Investigation steps included identifying that the records were added by admin during plugin updates, confirming their origin from cmdb_ci_automation, reviewing their XML (showing sys_class_name = cmdb_ci_automation, sys_created_by = admin, sys_mod_count = 0, and identical timestamps), and noting that the cmdb_ci_automation package is CMDB CI Class Models Tables in ServiceNow. The user is seeking confirmation on what created these cmdb_ci_automation records during app updates and guidance on preventing this in production. 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: ; } } Australia 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: ; } } Firstly, what created these entries?The flow "Summary Configuration for Catalog item" (sys_hub_flow), which runs on a daily schedule at 22:00. It isn't an install script or a data load in an update set — it's a scheduled flow that run daily. That explains the fingerprint you're seeing: a single bulk execution produces one uniform creation timestamp and sys_mod_count = 0 across every record, and the flow runs in a system/admin context so sys_created_by shows as admin.This flow is scoped withing Automation Center, available in v14.x and v15.x with 3 versions.Secondly, why catalog items?Any catalog item which got executed is auto populating in cmdb_ci_automation this then starts to get tracked in Automation Center Dashboards on the fly.Thirdly, is it Expected behaviour?Yes, expected, and gated by a single system property: sn_ac.auto_onboarding_catalog_items When true, the job onboards all catalog items in bulk. Catalog Item tracking became available in Automation Center v15, so if your Australia upgrade also moved AC to 14.x, the first scheduled run afterwards would have created the full set. However, in v15.1.0, we came up with a way to disable it via a system property. Check the property's current value.Lastly, Preventing recurrenceSet sn_ac.auto_onboarding_catalog_items to false. The flow then takes its Else branch and only summarises Automation Attribute records that already exist — it stops creating new CIs for catalog items.Two things to watch:Validate in a sub-production instance first, since turning this off also stops automatic onboarding for any catalog items you do want tracked.Capture the property change in an update set so it isn't reverted on a future upgrade, and re-verify the value post-upgrade as part of your regression checks.If you don't intend to use Automation Center's catalog-item tracking at all, deactivating the flow is the firmer control.