Unable to view newly created index on the UI - Support and Troubleshooting

Unable to view newly created index on the UI Summary .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: ; } } After a database index creation completes successfully, the newly created index may not appear in the ServiceNow UI . This occurs even though the index exists on the underlying database. The root cause is a stale platform cache that has not yet reflected the updated schema.

Symptoms Index creation completes without errors at the database level. The index is not visible under the Related List, Indexes tab in the Table details . Refreshing the browser or navigating away and back does not resolve the issue. The index is confirmed to exist when checked directly on the database. Confirm the Index Exists on the Database Before applying the fix, verify that the index was successfully created on the database but is missing from the UI.

Navigate to sys_db_object.LIST in the ServiceNow application navigator. Filter the list using the Table Name of the table on which the index was created. Open the relevant table record. Scroll to the Related Lists section and open the Indexes tab. Check whether the newly created index name appears in this list. If the index is absent from the UI but confirmed present on the database, proceed with the resolution steps below.

Resolution Invalidate the table cache using GlideTableManager to force the platform to rebuild metadata for the affected table.

Navigate to the Scripts – Background module: sys.scripts.DO Ensure the scope is set to Global . Run the following script, replacing {tablename} with the actual table name: GlideTableManager.invalidateTable("{tablename}");

Navigate back to sys_db_object.LIST and re-open the table record. Verify that the newly created index is now visible under the Indexes tab. Example If the index was created on the sys_audit table:

GlideTableManager.invalidateTable("sys_audit");