The Service Dashboard under Service Operations Workspace (SOW) fails to load<!-- /*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: ; } } .kb-wrapper { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; max-width: 100%; } .kb-wrapper h2 { font-family: 'Lato', sans-serif; font-size: 14pt; font-weight: 900; color: #032D42; border-bottom: 2px solid #e8fce4; padding-bottom: 4px; margin-top: 24px; margin-bottom: 10px; } .kb-wrapper p, .kb-wrapper li { font-family: 'Lato', sans-serif; font-size: 12pt; line-height: 1.7; } .kb-wrapper ul, .kb-wrapper ol { padding-left: 24px; margin: 8px 0; } .kb-wrapper .callout-info { border-left: 4px solid #52B8FF; background: #e6f4ff; padding: 10px 14px; margin: 14px 0; font-size: 12pt; font-family: 'Lato', sans-serif; } .kb-wrapper .callout-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 14px; margin: 14px 0; font-size: 12pt; font-family: 'Lato', sans-serif; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 5px; border-radius: 3px; font-size: 11pt; } .kb-wrapper ol.steps { list-style: none; counter-reset: step-counter; padding-left: 0; } .kb-wrapper ol.steps li { counter-increment: step-counter; display: flex; align-items: flex-start; gap: 12px; margin-bottom: 10px; } .kb-wrapper ol.steps li::before { content: counter(step-counter); background-color: #032D42; color: #63DF4E; font-weight: 900; font-size: 11pt; min-width: 26px; height: 26px; border-radius: 50%; display: flex; align-items: center; justify-content: center; flex-shrink: 0; margin-top: 2px; } .kb-wrapper table { width: 100%; border-collapse: collapse; margin: 12px 0; font-size: 12pt; font-family: 'Lato', sans-serif; } .kb-wrapper table th { background-color: #032D42; color: #FFFFFF; padding: 8px 12px; text-align: left; } .kb-wrapper table td { padding: 8px 12px; border-bottom: 1px solid #d0d0d0; } .kb-wrapper table tr:nth-child(even) td { background-color: #e8fce4; } .kb-wrapper a { color: #032D42; } Issue The Service Dashboard under Service Operations Workspace (SOW) fails to load. Navigating to the dashboard via the sidebar icon or directly via URL causes the landing page to load indefinitely and the dashboard never renders. Symptoms Accessing Service Operations Workspace and navigating to the Service Dashboard, results in a perpetually loading page.The issue occurs when accessing the dashboard via the sidebar icon or directly via URL: https://<instance>.service-now.com/now/sow/service-dashboard No error message is displayed; the loading spinner continues indefinitely.The issue affects all users, including those with the admin role. Facts This issue is not role-dependent — it affects users regardless of their assigned role, including admin. Release All Versions Cause The noc_user_view table contains multiple records with a View Name of default and an empty User ID. Only one such record should exist. When more than one default view without a User ID is present, the system retrieves multiple default view records and cannot resolve which one to use. As a result, no view is rendered and the dashboard loads indefinitely. The duplicate default view records are typically created unintentionally at a later stage, alongside the original default view created by the admin. Note: A user-specific view (a record with a User ID populated) is distinct from the shared default view. When multiple default views without a User ID exist, the system may fail to fall back to the user-specific view, causing no view to be returned at all. Resolution Identify and remove the duplicate default view records from the noc_user_view table, retaining only the single default view record created by the admin. Access the table list by typing noc_user_view.list in the application navigator filter and pressing Enter.Filter the records by View Name = default and User ID = (empty).Confirm that more than one record matches this filter. Multiple matching records confirm the duplicate condition.Identify the original default view record — this is the record created by the admin (visible in the Created by field as the admin user).Delete all duplicate default view records, keeping only the single original admin-created record.After deletion, verify that only one record remains with View Name = default and an empty User ID.Return to Service Operations Workspace and navigate to the Service Dashboard to confirm it loads successfully. Warning: Do not delete the original admin-created default view record. Removing all default view records will prevent the dashboard from loading for any user without a personal view configured.