Discovery Date disappears after clicking Refresh in Discovery Admin Workspace Run HistoryDescriptionIn the Discovery Admin Workspace, the Discovery Date field (start_date) is a client-computed value derived from the sys_created_on timestamp of each discovery status record. This value is not stored on the server and is calculated by the "Process statuses data" client script when status data is loaded. When the Refresh button is clicked on the Schedule View page, a REFRESH_COMPONENT event triggers a MACROPONENT_STATE_UPDATE_REQUESTED event that overwrites the selectedStatus state with raw server data. Since the server response does not include the client-computed start_date field, the title binding that displays the Discovery Date reads an undefined value, causing the date to disappear from the UI. As a result, the Discovery Date shown next to the Discovery ID in Run History disappears immediately after clicking the Refresh button. The issue only affects the Schedule View page; navigating via the Status tab does not exhibit this behavior.Steps to Reproduce Navigate to Discovery Admin Workspace → Schedules → IP-based\Cloud discoveryOpen any scheduleUnder Run History, select any execution recordObserve the Discovery Date displayed next to the Discovery ID in the headerClick the Refresh button in the top-right cornerObserve that the Discovery Date immediately disappears from the UI Note: The issue does not occur when navigating via the Status tab.WorkaroundImportant: After applying these changes, follow the ServiceNow documentation to mark the modified files as "Overwrite on Upgrade": Overwrite Customizations During Upgrades Navigate to UX Client Scripts (sys_ux_client_script) table and search for Process statuses data (sys_id: 5c6f6c7f4318aa10181df57c0ab8f2f2)Open the record and locate the following line in the script (approximately line 100): api.setState('statusesDataForHeader', statusesDataForHeader); Add the following code immediately after that line: // Re-inject start_date onto selectedStatus so the title CONCAT binding // renders correctly after REFRESH_COMPONENT overwrites selectedStatus with // raw server data that lacks the client-computed start_date field. var currentSelectedStatus = api.state.selectedStatus; if (currentSelectedStatus && currentSelectedStatus.sys_id) { var matchedEntry = statusesDataForHeader[currentSelectedStatus.sys_id]; if (matchedEntry && matchedEntry.start_date) api.setState('selectedStatus', Object.assign({}, currentSelectedStatus, { start_date: matchedEntry.start_date.displayValue })); } Save the recordClear the browser cache and refresh the Discovery Admin Workspace to verify the fixRelated Problem: PRB1979627