CMDB archive runs fail with "failed to acquire mutex while creating archive table for cmdb_ci" in sys_archive_run<!-- /*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: ; } } Issue One or more CMDB archive runs fail when archiving cmdb_ci and its extension tables, with a mutex-acquisition error recorded on the archive run. Symptoms sys_archive_run records show the error "failed to acquire mutex while creating archive table for cmdb_ci" and its extension tables.The individual archive tasks show no errors themselves; the error appears only on the run record.When multiple archive runs execute concurrently, one run may complete while others fail to acquire the mutex.The relevant sys_mutex record shows the lock as available (acquired field blank), indicating the lock is not permanently stuck. Cause Creating the archive table for cmdb_ci and its extension hierarchy is serialized behind a mutex (sys_mutex). When several archive runs touch the same cmdb_ci and extension tables concurrently, they contend for the same mutex. Because the lock is held only transiently during table creation and is shown as available afterward, the failures are mutex contention/starvation under concurrency rather than a stuck or orphaned lock - one run acquires the mutex and proceeds while the others time out trying to acquire it. Resolution Open an errored sys_archive_run record and read the full inner error text; the list view shows only the short "failed to acquire mutex" line. Confirm it names cmdb_ci / its extension tables and is not reporting a permanently held lock.Check the corresponding sys_mutex record. If the acquired field is blank, the lock is available, which rules out a stuck mutex and points to contention during concurrent runs.Reduce concurrency on the affected archive rules so that runs touching cmdb_ci and its extension tables do not execute simultaneously - stagger their schedules rather than running them in parallel.Re-run the archive after staggering and confirm the runs complete without the mutex error.If contention persists, review the archive mutex spin and timeout behavior with the owning dev team. There is no targeted product fix for this at present, so the practical remediation is scheduling and concurrency tuning rather than a patch.