---
sourceDocument: Yokohama Release Notes
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/release-notes

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Release Notes

ft:clusterId :

    - rn

bundleId :

    - rn


---

# Yokohama Patch 9

# Yokohama Patch 9 {#ariaid-title1}

Release version: Yokohama  
Updated November 6, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 63 minutes to read  
The Yokohama Patch 9 release contains important problem fixes.

Yokohama Patch 9 was released on November 6, 2025.
:
    * Build date: 11-02-2025_1032
    * Build tag: glide-yokohama-12-18-2024__patch9-10-22-2025

Important:  
For more information about how to upgrade an instance, see [ServiceNow upgrades](https://servicenow-prod.fluidtopics.net/gT4zpGHCQSL790audteXjw "The upgrade process moves your instance to a new ServiceNow release version. Understand the difference between upgrading and patching, release definitions, rollback and backup options, and how to test your non-production and production instance upgrades.").

For more information about the release cycle, see the [ServiceNow Release Cycle](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547244).{#yokohama-patch-9__p_download-version}  
Note:  
This ServiceNow AI Platform major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see [KB0743854](https://support.servicenow.com/kb_view.do?sysparm_article=KB0743854). For a downloadable, sortable version of the fixed problems in this release, click [here](https://downloads.docs.servicenow.com/enus/yokohama/rn/patches/PRBs-Y09.00.xlsx).

## Overview {#yokohama-patch-9__overview}

Yokohama Patch 9 includes 208 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.  
Figure 1. Top 10 problem categories

## Security-related fixes {#yokohama-patch-9__security-related-fixes}

Yokohama Patch 9 includes fixes for security-related problems that affected certain ServiceNow® applications and the ServiceNow AI Platform®. We recommend that customers upgrade to this release for the most secure and up-to-date features. For more details on security problems fixed in Yokohama Patch 9, refer to [KB2587878](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2587878).

## Changes in Yokohama Patch 9 {#yokohama-patch-9__changes-in-patch}

[Now Assist and agentic AI release notes](https://servicenow-prod.fluidtopics.net/~e9LkFEMisO5_g8~y_7T5g "Now Assist and agentic AI product enhancements and updates in the Yokohama release.")
:   For Now Assist new features and changes, see [Now Assist and agentic AI release notes](https://servicenow-prod.fluidtopics.net/~e9LkFEMisO5_g8~y_7T5g "Now Assist and agentic AI product enhancements and updates in the Yokohama release.").

[Show borders between search result cards in portal search](https://www.servicenow.com/docs/access?context=show-borders-search-result-cards-portal-search&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US)
:   Display borders between search result cards on the search results page for portal search applications.

[Show borders between search result cards in global search](https://www.servicenow.com/docs/access?context=show-borders-search-result-cards-global-search&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US)
:   Display borders between search result cards on the global search results page.

[Show borders between search result cards in portal search](https://www.servicenow.com/docs/access?context=show-borders-search-result-cards-portal-search&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US)
:   Display borders between search result cards on the search results page for portal search applications.

[Show borders between search result cards in global search](https://www.servicenow.com/docs/access?context=show-borders-search-result-cards-global-search&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US)
:   Display borders between search result cards on the global search results page.

## Notable fixes {#yokohama-patch-9__section-notable-fixes}

The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
{#yokohama-patch-9__notable-fixes__entry__4}

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Access Control PRB1893600 [KB2178333](https://hi.service-now.com/kb_view.do?sysparm_article=KB2178333) | RecordFamilyResolver.archiveTableHasACLTerms needs more optimization | Performance issues with reports on instances with a big number of archive tables. | Refer to the listed KB article for details. |
| Access Control PRB1915184 [KB2400619](https://hi.service-now.com/kb_view.do?sysparm_article=KB2400619) | Security constraints prevent access to a requested page when visiting task.list | Failing a Deny ACL from anywhere in the hierarchy prevents table access to the list of a parent table. | Refer to the listed KB article for details. |
| Activity Stream PRB1878917 | Text doesn't persist if the user navigates away from the email composer when drafting a reply | Text in the email composer disappears when the user navigates to a different tab. This only occurs when replying via the activity stream tile, not when composing a new email. |   |
| Configuration Management Database (CMDB) PRB1930654 | The legacy health dashboard doesn't tell the user that the dashboard is deprecated/no longer supported | Users have bookmarked, saved, or edited links to the legacy health dashboard, meaning they can still access it. There's a lot of confusion on why the dashboard is no longer working as intended. There should be a message to tell the user this dashboard has been migrated to CMDB Workspace. | 1. Check out a Washington DC instance. 2. Make a favorite for Health Dashboard - CMDB view. 3. Upgrade your instance to Xanadu or beyond. 4. Select the bookmark for the CMDB view. {#yokohama-patch-9__ol_vk2_5ng_dhc} Expected behavior: When users navigate to the legacy dashboard, they should be able to see a message telling them to use the new health dashboard and that the legacy dashboard is no longer supported. Actual behavior: See that the legacy health dashboard has some broken widgets, no colors, etc. but there is no indication that this dashboard is retired or has been migrated. |
| UI Field Administration PRB1877769 [KB2182152](https://hi.service-now.com/kb_view.do?sysparm_article=KB2182152) | The info (i) icon for reference catalog variables is missing on requested items and the 'SCTASK' form under Service Operations Workspace | The issue is seen with all the workspaces since Yokohama. | Refer to the listed KB article for details. |
[ ]

{#yokohama-patch-9__notable-fixes}

## All other fixes {#yokohama-patch-9__other-fixes}

{#yokohama-patch-9__all-other-fixes__entry__4}

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Activity Stream PRB1928872 | The CanReadRepo class encounters a ConcurrentModificationException | This concurrency issue arises because the class uses a HashMap, which is not thread-safe. The HashMap should be replaced with a ConcurrentHashMap to ensure thread-safe operations and prevent the exception. |   |
| Advanced Work Assignment for Case Service channel PRB1946390 | The case task isn't working properly for CCaaS external routing | The assignment isn't happening since there's no mapping field available for CCaaS partners to use and store their external ID onto the 'Case task' table. | 1. Configure the instance to route the case tasks through external CCaaS. 2. Create a case task in the instance. {#yokohama-patch-9__ol_m22_5ng_dhc} Expected behavior: The case task should be routed to the agent using the external routing mechanism. The case task should be picked up by the CCaaS events and assigned to the identified agent. Further events should also be triggered for this task. Actual behavior: Currently the case task doesn't get assigned to the agent. |
| Advanced Work Assignment PRB1933671 | AWA (Advanced Work Assignment) uses the system locale timezone when writing to logs | The AWAEventUtil code changes the global locale setting, causing the 'localhost log' to be written in UTC rather than PST (standard). | 1. Log in to an instance. 2. Install the Advanced Work Assignment (AWA) plugin. 3. Navigate to Advanced Work AssignmentService ChannelsNew. 4. Enter the following values: 1. Name: test 2. Index order: 100 3. Table: Incident 4. Utilization condition: Short Description is not empty {#yokohama-patch-9__ol_s22_5ng_dhc} 5. Submit it. 6. Ensure that the channel is active. 7. Create a new queue. 8. Open the record created in step 3. 9. Choose the 'Queue' related list. 10. Create a new 'Queue' record. 11. Enter in all the mandatory fields. 12. Submit it. 13. Enable Logging. 14. Open the record created in step 3. 15. Select Queues and New. 16. Name it 'test-queue'. 17. Submit it. 18. Check the localhost log. 19. Have the terminal open for all the nodes. 20. Tail the localhost log. 21. Navigate to IncidentCreate New. 22. Enter in something. 23. Submit it. {#yokohama-patch-9__ol_r22_5ng_dhc} Observe that the timestamp zone has changed, and some lines are in the previous timezone and others are in UTC. |
| Advanced Work Assignment PRB1938992 | High AWA assignment cycle times for impact voice call routing | A user is uptaking in NVC and they are facing slow response times for call routing. It's taking \~12 seconds to route the call to agent. Each AWA assignment cycle is taking \~11 secs and out of which \~8 secs is being spent for Agent Map creation. Expected response times should be less than a second as there's no other load in the system. |   |
| Advanced Work Assignment PRB1942061 | Lack of ability to track end-to-end AWA Assignment times | There's currently a gap in performance measurement of the AWA offer work API and manual assignment API, where there is no way to accurately determine the time difference between when an external AWA assignment API call was made and when the work item assigned_to would be updated to the assigned agent. The admin lacks context as to when the request actually gets processed and the work item gets assigned (and by extension, the inbox card shows up in the agent's inbox). Another limitation with the current design is that it only persists the offered_on for the final API invocation, which led to work item acceptance. If there were multiple agents which were offered the work item via these APIs, this context is lost. |   |
| Advanced Work Assignment PRB1944387 | The 'Create Segment On WorkItem Accept' business rule runs unnecessarily when a previous accepted work item exists |   | 1. Call the 'Offer work' API on an interaction. 2. Accept the work item. 3. Clear out the assigned_to on the interaction. 4. Call the offer work API on the same interaction. {#yokohama-patch-9__ol_gf2_5ng_dhc} Expected behavior: The 'Create Segment On WorkItem Accept' business rule shouldn't be triggered for the old work item. Actual behavior: The 'Create Segment On WorkItem Accept' business rule is triggered for the old work item. |
| Advanced Work Assignment PRB1950558 | Advanced Work Assignment (AWA) should be able to determine if the work item is rejected due to time out or Asynchronous Message Bus (AMB) disconnection | When the work item times out, the work item reason on the awa_work_item_rejection table is 'Timed out' instead of 'AMB connection lost'. | 1. Install the Agent Chat plugin with the demo data. 2. Open the AWA assignment rule. 3. Update the timeout time to 15 seconds. 4. Open a browser (browser 1). 5. Log in to the workspace as an agent in browser 1. 6. Open another browser (browser 2). 7. Log in to the instance as a requestor. 8. Open the URL /sn-va-web-client-app.do in browser 2. 9. In browser 1, close the workspace tab completely as an agent. 10. Notice that the agent presence will not be set to offline immediately because the default idle check gives a 5 min buffer, and the agent is still available to receive work item at the moment. 11. In browser 2, start the live agent handoff. 12. Wait for 15 seconds so the work item will be timed out. 13. As an admin, navigate to the awa_work_item_rejection table. 14. Check the rejection record for the previous interaction. {#yokohama-patch-9__ol_kf2_5ng_dhc} Expected behavior: The reason should be 'AMB connection lost'. Actual behavior: The rejection reason is 'Timed out'. |
| Agent Chat PRB1839064 | Refreshing the page causes the active chat shell to disappear, but refocusing on the live agent in a separate window restores the chat shell | This issue is observed in version 24.4.2 of Workspace App Shell TD. | 1. Ensure the Agent Chat plugin is installed. 2. Open Service Operation Workspace as an admin in a window. 3. Set the admin as available as a chat agent. 4. Attempt to log in to Service Operations Workspace as Abel Tuter in an incognito window. 5. Attempt to connect to a live agent. 6. Accept the chat as an admin. 7. End the chat. 8. Keep the tab open. 9. Initiate the chat again as Abel Tuter. 10. Accept the chat as an admin. 11. Refresh the admin page {#yokohama-patch-9__ol_xf2_5ng_dhc} Observe that the active chat shell window isn't opening unless the live agent is not in focused by Abel Tuter. |
| Agent Chat PRB1846962 | Chat disappears if the user refreshes the page when a list is in the open tabs of Service Operations Workspace (SOW) | Refreshing the page causes the chat to disappear until the tab with the simple list is opened. | 1. Create a single score related to a simple list on the home page. 2. Open the instance in a browser. 3. Impersonate a system administrator. 4. Open SOW. 5. Navigate to InboxAvailable. 6. Open a new browser in incognito mode. 7. Open the instance in the incognito browser window. 8. Impersonate another user. 9. Open /esc. 10. Select Open chat Window. 11. Select Contact Live Agent, if necessary. 12. Return back to the first opened. 13. Accept the chat. {#yokohama-patch-9__ol_fg2_5ng_dhc} Observe that in the chat window opened in first browser, unexpected behaviors occur when the simple list is open in the SOW tabs. |
| Agent Chat PRB1943902 | Create a new exclusive channel to receive work items on Agent Chat | The inbox component should subscribe to a new Asynchronous Message Bus (AMB) channel other than the existing AWA/work_item channel to reduce the chance of being interfered with by other components subscribing to the same channel. The AMB publish function used in the workItemResponder should be updated to take the trace id. |   |
| AI Search (Glide) PRB1921724 | Improve ResponsePostProcessor time when the table is early binding | This is a product update. |   |
| AI Search (Glide) PRB1930534 | When used on service portals, 'Exact Match' should honor search sources | When using the 'Exact Match' feature on a service portal, the results of the exact match lookups should be limited to the sources which are included in the search profile, and honor the filters set on the search sources. |   |
| AI Search (Glide) PRB1942680 | Web search isn't working in Zurich and recent store apps |   | 1. Navigate to /esc. 2. Start the web search by selecting the Globe icon. 3. Query, 'Who is the president of the US.' {#yokohama-patch-9__ol_og2_5ng_dhc} Expected behavior: The web search query goes through. Actual behavior: The user receives a 'Sorry there was a problem' message. |
| AI Search PRB1799463 | The 'Clone' functionality fails for search applications | A clone isn't created when using the Clone UI Action, even though it asks for the name of the cloned profile. | 1. Navigate to AllSearch Applications. 2. Select any search application. 3. Select the Clone UI Action. 4. Observe that it re-routes to another form that asks for name of the cloned profile again. {#yokohama-patch-9__ol_rg2_5ng_dhc} Notice that no clone is created. |
| AI Search PRB1859870 | Removing two business rules and a dictionary attribute | This issue was observed in Xanadu and Yokohama. | 1. Provision an instance using an older glide version. 2. Apply the fix in PRB1836358 by using the script. 3. Observe that two business rules and a dictionary attribute were added. 4. Upgrade the instance to latest Xanadu or Yokohama build. {#yokohama-patch-9__ol_wg2_5ng_dhc} Expected behavior: The business rules and dictionary attributed added were removed. Actual behavior: The business rules and dictionary attribute remain on the instance. |
| AI Search PRB1940661 | The hasPendingIndex API is broken | The sn_ais.AisUtil.hasPendingIndex(tableName, recordSysId, embeddingModelName, semanticIndexName); call fails. |   |
| AI Search UX PRB1917701 | Empty suggestions are stored when the user query is '\*\*\*' |   | 1. Enable Dynamic Window. 2. Search '\*\*\*'. {#yokohama-patch-9__ol_bh2_5ng_dhc} Observe that empty suggestions are stored as queries are normalized and punctuations are stripped. |
| AI Search UX PRB1917704 | Punctuation isn't removed for languages other than English |   | 1. Turn on Spanish language. 2. Enable DW/FPE. 3. Search for '¿Qué es el spam?' {#yokohama-patch-9__ol_eh2_5ng_dhc} Observe that '¿' isn't removed in the suggestion utterances table. |
| AI Search UX PRB1930672 | Service Portal Genius Result (GR) synthesized response flashes and changes text size |   |   |
| AI Search UX PRB1935078 | Make the border for the Search Result card configurable | There are no borders for the Search Result card. |   |
| AI Search UX PRB1936251 | KG citation list view is empty | A message says 'Found no records' when a query should produce results. | 1. Navigate to /sp. 2. Query 'What asset does Abel Tuter have' in the portal search box. 3. View the assets info and multiple assets citations. 4. Select View Records. {#yokohama-patch-9__ol_hh2_5ng_dhc} Expected behavior: The user is direct to KG citation list view and assets show up in the list. Actual behavior. A message says, 'Found no records'. |
| AI Search UX PRB1937984 | The caller is not in the scope rhino.global when called from Now Assist in Virtual Agent |   |   |
| AI Search UX PRB1941065 | Response loads even after a 15 second timeout on the portal | The portal stops the loading sign, which means it's reached the 15 second timeout. The response to the user's query loads after that. | 1. Navigate to a portal with DW enabled. 2. Search for any query, such as 'How to create a new user'. {#yokohama-patch-9__ol_lh2_5ng_dhc} Expected behavior: Once the portal times out, it doesn't load the response. Actual behavior: The portal stops the loading sign, which means it's reached the 15 second timeout, but the response loads after that. |
| AI Search UX PRB1942589 | Increased timeout from 15s to resolve frequent no Genius Results on Portal | This issue occurs on Dynamic Window (DW) enabled on Portal with Model GPT OSS, and takes longer for a response to return than in any other models. |   |
| AI Service - Glide Interfaces PRB1900176 | ExtractItems() pops the solutionIds from the original array | On an instance with more than 40(JOB_REQUEST_COUNT_LIMIT) solutions in 'Waiting For Training' state at present, once the sys_trigger is triggered, all these solutions will be moved to the 'Training is Cancelled' state and new solutions will be created and retried again. |   |
| AI Service - Glide Interfaces PRB1902435 | In handleWaitingForTrainingState, there is a missing second argument in isJobSubmitted() | In handleWaitingForTrainingState, a solution ID is not passed to the isJobSubmitted() function, resulting in an execution of the 'if' condition. Even if the job is submitted, the solution is cancelled and retried until it reaches its last retry. |   |
| Analytics Data API PRB1894963 | Data Visualization drilldown doesn't follow previous filters | On Data Visualization, only the first-level drilldown honors the selected filters. This issue was observed in Xanadu and Yokohama. | 1. Navigate to an instance. 2. Open a Data Visualization. 3. Select a column. 4. Notice that it contains a drilldown. 5. Select another column. 6. Notice that it contains a drilldown with a daily view. {#yokohama-patch-9__ol_oh2_5ng_dhc} Observe that only the first-level drilldown honors the selected filters, and that subsequent drilldowns (level 2 and beyond) reset to the original selection context, rather than chaining the filters from the intermediate drilldown. |
| Analytics Data API PRB1921406 | POST /api/now/charts/data returns 500 status code when the table is not valid | POST /api/now/charts/data should return the 400 HTTP status code, with the error message 'Table is not valid: null.' Instead, it returns the 500 HTTP status code. |   |
| Analytics Data API PRB1926918 | The 'Process analytics cache pre-fetch queue' job leads to OutOfMemoryError and the node restarts | When the user runs the 'Process analytics cache pre-fetch queue' job, it loops in ChangeCheckConflictsSNC script include. | 1. Create a test_breakdown table. 2. Add a field: 1. Name: Name. 2. Type: String. 3. Length: 50. {#yokohama-patch-9__ol_uh2_5ng_dhc} 3. Populate two million records in the table with names such as Name1, Name2, etc. 4. Create a breakdown source on test_breakdown without any condition. 5. Create a breakdown of the above breakdown source. 6. Create a test_indicator table. 7. Add a field: 1. Name: ref_breakdown. 2. Type: Reference. 3. Reference: test_breakdown. {#yokohama-patch-9__ol_vh2_5ng_dhc} 8. Populate two million records in test_indicator with reference to all the records in test_breakdown, respectively. 9. Create an indicator source based on test_indicator, without any condition. 10. Create an indicator based on the above indicator source. 11. Navigate to the breakdown created in step five. 12. Add a breakdown mapping on the test_incident and ref_breakdown field. 13. Navigate back to the indicator. 14. Add the breakdown. 15. Change the system properties: 1. com.snc.pa.dc.hsql.max_row_count_indicator_source = \> 10000000. 2. com.snc.pa.dc.max_breakdown_elements_limit = \> 10000000. {#yokohama-patch-9__ol_r5h_rvf_dhc} 16. Collect 1-day score for the indicator. 17. Create a new dashboard. 18. Add a visualization: 1. Type: Single score. 2. Source: Indicator created in step 10. {#yokohama-patch-9__ol_wh2_5ng_dhc} 19. Add a filter: 1. Type: Single select. 2. Source: Breakdown created in step five. {#yokohama-patch-9__ol_xh2_5ng_dhc} 20. Open any memory inspection tool and check the current memory footprint. 21. Open the filter and select a value. {#yokohama-patch-9__ol_th2_5ng_dhc} Notice that the memory footprint steadily increases by about 800 million until the score is displayed. |
| Analytics Data API PRB1945218 | Memory leak of JSON serializer in multivis API | Each time a data request is processed, a new serializer is created and not released unless a GC is performed, which causes a memory leak. | 1. Create a dashboard. 2. Add a tab and add 50 identical single score vis: 1. Source: incident. 2. Condition: sys_id is empty. {#yokohama-patch-9__ol_p32_5ng_dhc} 3. Duplicate the tab 9 times so there are 500 visualizations in total. 4. Disable the property 'com.snc.dashboard.streaming.enabled'. 5. Stop the instance and start again, but don't access the instance in the browser. 6. Use VisualVM to capture the heapdump. 7. Search for 'IntegerDateSerializer' in the object list. 8. Observe that there are 0 results. 9. Access the dashboard created in step 1. 10. Go over all 10 tabs. 11. Use VisualVM to capture the heapdump. 12. Search for 'IntegerDateSerializer'. 13. Observe that there are \~500 results. 14. Repeat steps 8 through 11 (get the heapdump and search). {#yokohama-patch-9__ol_o32_5ng_dhc} Observe that there are \~1000 results. Each time a data request is processed, a new serializer is created and not released unless a GC is performed, which causes a memory leak. |
| App Engine Studio - Family Channel PRB1923756 | The Record Producer remains as the original template's one in a newly created app | When using the AES Template, the Record Producer remains as the original template's one, but it should be the one in the new app. | 1. Create an app (App1). 2. Create a new table in App1. 3. Create a Record Producer with the table. 4. Create a flow with the action 'Get Catalog Variables'. 5. Set the Record Producer in it. 6. Save. 7. Create a template with App1. 8. Create a new app (App2) with the template. 9. Check the Record Producer that was set in the action 'Get Catalog Variables'. {#yokohama-patch-9__ol_z32_5ng_dhc} Expected behavior: The Record Producer is the one in the new app (App2). Actual behavior: The Record Producer is the one in the original app (App1). |
| Application Install Engine PRB1936285 | During node re-start, the system downloads version expects a higher store version | After a node restarts, the user sees the soft dependencies in the dependency manager are populated by the versions. The root cause is the artifacts are loaded from a file during node restart, and that is overwriting the active plugins information in Dependency Manager. | 1. Open a multi-node instance that has 15.0.5 as a version. 2. Install 15.0.5 and other optional plugins. 3. Upgrade to 15.0.17. {#yokohama-patch-9__ol_gj2_5ng_dhc} After the node restarts, soft dependencies in the dependency manager are being populated by the base instance versions. |
| Async HTTP Client PRB1937994 | Async HTTP client connection pool isn't optimized | Connection pooling is limited to 60 per host and 180 total, when it should host 300-900. | 1. Log in to an instance. 2. Navigate to /sp endpoint. 3. Enter 'What is spam'. 4. Select New conversation after 35s. 5. Enter 'What is spam' again. {#yokohama-patch-9__ol_jj2_5ng_dhc} Notice that second set of requests don't benefit from connection pooling, and limits it to 60 per host and 180 total. |
| Automated Test Framework (ATF) PRB1874569 | Opening a form with 'view' can fail in Automated Test Framework (ATF) due to case sensitivity | This issue was observed with a new ATF test in the Performance Analytics application. | 1. Create a new ATF test. 2. Add a 'Navigate to Module' step to navigate to 'Automated Indicators' in the Performance Analytics application. 3. Add an 'Open a Record in List' step to open any record in that list. 4. Run the test. 5. Wait until the test completes. 6. View the result. {#yokohama-patch-9__ol_nj2_5ng_dhc} Expected behavior: The test passes. Actual behavior: Test fails with the output 'Expected to open the 'Automated' view of the form, but actually opened to the 'automated' view. |
| Automated Test Framework (ATF) PRB1922654 | Automated Test Framework test UI action fails due to a timeout error | There appears to be a race condition introduced in Yokohama. Tests that previously passed in Xanadu are now failing some of time when waiting for a response from the intent channel. | 1. Navigate to Automated Test Framework (ATF)Tests. 2. Create a test. 3. Add test step by opening an existing record with values: * Form: SOW Workspace * Table: sc_task * Record: Select any record {#yokohama-patch-9__ul_uj2_5ng_dhc} 4. Add test step by: 1. Select a UI action or UI action visibility. 2. Select Save for the UI action. {#yokohama-patch-9__ol_vj2_5ng_dhc} 5. Clear the instance cache and browser cache. 6. Using an incognito browser session. 7. Log in. 8. Navigate to the test. 9. Run the test. {#yokohama-patch-9__ol_tj2_5ng_dhc} Expected behavior: The test should pass every time. Actual behavior: The tests fails intermittently due to an 'Timed out waiting for intent feedback' error. |
| Case and Knowledge Management for HR Service Delivery PRB1880009 | Attachments aren't uploaded in the 'Agent Chat' window from HR Agent Workspace | This is happening for HR Core. |   |
| Case and Knowledge Management for HR Service Delivery PRB1933236 | Add RCA to support 'Ask a question' with enhanced chat | This is a product update. |   |
| Client Scripts PRB1889628 | List declarative actions aren't working |   | 1. Create a list declarative action. 2. Implement as a client script. 3. Set the client script to 'console.log(''Test'')'. 4. Set the table as 'incident'. 5. Navigate to the incident list. 6. Select the declarative action. {#yokohama-patch-9__ol_ck2_5ng_dhc} Notice that no console logs are outputted. |
| CMDB Data Manager PRB1892066 [KB2217546](https://hi.service-now.com/kb_view.do?sysparm_article=KB2217546) | Policy form doesn't honor retirement definitions correctly in enforced conditions when multiple retirement definitions are enabled |   | Refer to the listed KB article for details. |
| Condition Builder PRB1927599 | The condition builder on the presentational list displays all the options instead of the one that was searched | When the user searches for an option, the condition builder displays all the options in a list and highlights the one that was searched. Instead, only the option that was searched should be displayed. | 1. Create a UI Builder page. 2. Configure the presentational list component. 3. Open the page in run time. 4. Select the Filter icon. 5. In one of the fields, search for an option. {#yokohama-patch-9__ol_hk2_5ng_dhc} Expected behavior: The list displays only the option that was searched. Actual behavior: The list displays multiple options and highlights the one that was searched. |
| Condition Builder PRB1943552 | dotWalkConnectedDataBehavior cannot be imported in version 27.0.4 | The behavior source files aren't where exports exists after the import. | 1. Open a project where now-dot-walk 27.0.4 is a dependency. 2. Attempt to import dotWalkConnectedDataBehavior from/now-dot-walk. {#yokohama-patch-9__ol_lk2_5ng_dhc} Expected: The import provides the consuming application with the behavior. Actual: The import doesn't provide the behavior source files where exports exist. |
| Configuration Management Database (CMDB) PRB1846249 | Identification and Reconciliation Engine (IRE) throws a NullPointerException (NPE) when there is a cache flush during IRE processing |   | 1. Run the payload with a break point after'setIndependentQueryFromPayload' method locally. 2. Create a new break point after the 'setIndependentQueryFromPayload' to stop the thread. 3. Open another window. 4. Log in to /cache.do. 5. Perform the cache flush. 6. Resume the execution of thread stopped in step 2. {#yokohama-patch-9__ol_pk2_5ng_dhc} Observe NPE. |
| Contract Management PRB1913448 [KB2310704](https://hi.service-now.com/kb_view.do?sysparm_article=KB2310704) | The payment amount and total amount are incorrectly displayed in the local currency value under USD currency | When the user sets a payment amount using a local currency (for example, NOK) when selecting Adjust on the Contract, the payment amount gets saved on the XML. When re-opening the record in Form view, it defaults to USD, but shows the amount that originally belonged to NOK. This behavior applies to both payment_amount and total_cost fields. | 1. Open a contract from the ast_contract table. 2. Select Adjust. 3. Enter a new payment amount and currency, for example, NOK 966.00. 4. Search and view the same Contract on List view. 5. Notice that payment amount and total amount are both reflected as (NOK)966.00 and (USD)96.7669 when selecting Toggle currencies. 6. Open the record in Form view. {#yokohama-patch-9__ol_zk2_5ng_dhc} Notice that the payment amount is USD 966. |
| Database Persistence - Data Access PRB1792470 | Some alters to increase max length are running twice during an upgrade | Multiple updates happen because a sys_dictionary record has an incorrect field length after finishing the bootstrap batcher. |   |
| Database Persistence - Data Access PRB1923704 | Due to an ordering change on Raptor post migration, certificate authentications for API calls may fail and cause '500' errors | When mutual authentication is configured using both protocol profile and system properties, the system property takes precedence. This causes the SSL exchange to utilize the socket factory for client certificate provisioning, bypassing the keystore defined in the protocol profile. Additionally, when mutual authentication is enabled via property configuration, all certificates from the sys_certificate table are loaded. This can lead to intermittent outbound call failures if expired certificates are cached and used for mutual authentication, resulting in HTTP 500 responses. |   |
| Database Persistence - Data Access PRB1930031 | The user doesn't get results from a Child table (sn_lg_cnt_repository) of Parent (ast_contract) |   |   |
| Database Persistence - Data Access PRB1934684 | getForTables on KG Global Graph isn't returning all the edges from contribution graphs | WDF tables that do not have a primary key when included in a knowledge graph schema causes query failures, even for queries that are only referencing to other glide tables present in that schema. The presence of this table can block all query execution within the graph. | 1. Create a contribution graph 'cont1' having sys_user and cmn_schedule nodes. 2. Save the edge by using the script. {#yokohama-patch-9__ol_gl2_5ng_dhc} Notice the error that occurred while getting cypher to result, 'com.snc.db.graph.GraphToGtopSerializationException: No element descriptor found for column on table u_df_wdf_without_pk: no thrown error.' |
| Database Persistence - Data Access PRB1936199 | Apostrophe in the cypher query causes an error |   |   |
| Database Persistence - Data Access PRB1944376 | Order tables in the view deterministically | Currently, when constructing the view to return from a cypher call, it creates the view from the set of the tables being requested based on enumerating the keyset. This has a non-deterministic order that depends on the underlying structure and the table prefixes. While that wouldn't be an issue at some layers, it means the ACL evaluation differs based on the ordering, which is hard for debugging and also hard to configure around. Instead, it should sort the order of the tables in the view alphabetically by the table name. | 1. Do a cypher query with more than one return node. 2. Examine the view definition to see which table comes first. {#yokohama-patch-9__ol_kl2_5ng_dhc} |
| Database Persistence - Data Access PRB1944805 [KB2552260](https://hi.service-now.com/kb_view.do?sysparm_article=KB2552260) | getDisplayValue() throws NullPointerException on many types of catalog variable |   | Refer to the listed KB article for details. |
| Database Persistence - Data Access PRB1946286 | Failing Workflow Data Fabric (WDF) queries when trying to execute on connection for trino_primary | When trying to get specific column instead of the entire record, the error occurs in the response. | 1. Log in to the instance. 2. Impersonate a user. 3. Run the script. {#yokohama-patch-9__ol_ul2_5ng_dhc} Notice the error which includes, 'FAILED TRYING TO EXECUTE ON CONNECTION trino_primary'. |
| Database Persistence - WDF PRB1938101 | The 'Database' view for Workflow Data Fabric (WDF) incorrectly assumes the sys_id when caching underlying glide records | add/getCache in the 'Database' view has a hardcoded assumption that there's a sys_id element in the source and doesn't check for a null result. The copyValue code calls into GlideElement, which short circuits due to the WDF table being a foreign table. This needs to skip the cross scope check but still copy the value. |   |
| DevOps (Family) PRB1920798 | Updating the sn_devops.table_ auto_archive_duration system property doesn't update all archive rules as there are some in other scopes |   | 1. Navigate to sys_properties. 2. Update sn_devops.table_ auto_archive_duration to another number (something to test with). {#yokohama-patch-9__ol_xl2_5ng_dhc} Observe that only tables with the DevOps Data Model scope are available for archival. |
| Discovery PRB1843863 [KB2061931](https://hi.service-now.com/kb_view.do?sysparm_article=KB2061931) | Shazzam Insights doesn't display any data in Discovery Admin Workspace | Shazzam Insights information isn't populated in the table 'Shazzam_Insights' and an error appears in the system logs related to 'com.glide.util' usage. | Refer to the listed KB article for details. |
| Discovery PRB1862106 [KB2436326](https://hi.service-now.com/kb_view.do?sysparm_article=KB2436326) | Global IP exclusion isn't working for a cloud VM schedule | Not all the global exclusions are working for a cloud discovery. | Refer to the listed KB article for details. |
| Discovery PRB1902780 | The log pattern cloud errors only once | Currently, the cloud pattern errors are incorrectly being logged twice. It ends with two separate errors for the same pattern, one for the exception in the log and one for the 'Pattern Failed'. |   |
| Discovery PRB1930200 [KB2474013](https://hi.service-now.com/kb_view.do?sysparm_article=KB2474013) | Protected Tables Plugin will block DiscoverySensorJob logging, and cause warnings about syslog inserts from ProtectedTableAccessHandler instead | When the Protected Tables Plugin is active, which is recommended, the source= DiscoverySensorJob GlideRecord inserts made directly to the syslog table by Discovery's 'DiscoverySensorJob' script include are blocked, and flood the syslog table with logs from source=ProtectedTableAccessHandler instead. | Refer to the listed KB article for details. |
| Discovery PRB1933785 | A Cloud Discovery schedule incorrectly maps all related service accounts even when the 'Discover all Related accounts' toggle is unchecked | When creating a Cloud Discovery schedule for a project and un-checking the 'Discover all Related accounts listed below' toggle, the schedule still maps to all service accounts under that folder level. This behavior is intermittent and has been reproduced on multiple environments. The UI script logic doesn't correctly handle timing between setAllSubAccSelected and getSubAccountsOfMasterAccount. As a result, subAccountsList is reset incorrectly, leading to unintended account mappings. |   |
| Discovery PRB1937992 | Discovery Schedule doesn't support the discovery of more than 5000 IPv6 addresses | If the user creates a Discovery Schedule with over 5000 IPv6 addresses, the Discovery Status is instantly canceled and an error message appears. | 1. Create a Discovery Schedule with over 5000 (X) IPv6 addresses to disocvery_range_item_ip. 2. Select Discover Now. {#yokohama-patch-9__ol_em2_5ng_dhc} Observe that the Discovery Status is created and instantly canceled with the following error message under the Discovery logs related list: 'IP lists with IPv6 addresses can only contain 5,000 IPs but have X'. |
| Dynamic Translation for Agent Chat PRB1942231 | The agent_translated_msg column is overwritten with empty value when the agent is in English and the chat requester is non-English |   | 1. Enable and configure Dynamic Translation for Agent Chat (DTAC). 2. Log in to Service Operations Workspace as an English speaking agent. 3. In another browser, log in as chat request in non-English language. 4. Initiate an agent chat. 5. Type an English phrase as an agent. {#yokohama-patch-9__ol_im2_5ng_dhc} Expected behavior: The agent_translated_msg on outbound message should be populated with English text. Actual behavior: The agent_translated_msg gets overwritten with empty values. |
| Event Management PRB1639714 | Alerts on an Application Service have empty PRCs | Alerts on an Application Service appear in the list of 'Impacted Services/CIs' of some change requests. These alerts have empty PRCs and they have only one change request instead of two. | 1. Define the Manual Application Service. 2. Define the Change Request for the Application Service. 3. Send the event to some CI of the Application Service. 4. Open the generated alert. 5. Navigate to the PRC. 6. Observe that the alert has the PRC 'Change on Application Service.' 7. Send the event to the Application Service. 8. Open the generated alert. 9. Navigate to the PRC. 10. Observe that the alert has the PRC 'Change on Application Service.' 11. Create another change request on a different CI. 12. Add the defined Application Service to the list of Impacted CIs of the change request. 13. Send the event to the Application Service. 14. Open the generated alert. 15. Navigate to the PRC. {#yokohama-patch-9__ol_om2_5ng_dhc} Observe that the alert has only one change request, but it should have two. |
| Event Management PRB1934096 | There's a regex preview mismatch in Enrich due to Java vs JavaScript engine differences | In the 'Enrich' page, the regex preview incorrectly shows no match even when the regex is valid and works correctly on actual events. This discrepancy, caused by differences between Java and JavaScript regex engines, has been observed by multiple users and leads to confusion when building enrichment rules. |   |
| File-based Discovery PRB1936524 | File-based Discovery doesn't capture the content when the filename contains spaces | Discovery throws an below error in the Discovery logs for a filename that contains spaces: 'Error(s) during file based discovery: base64: extra operand '/usr/share/.../IOP' Try 'base64 --help' for more information'. |   |
| Flow Engine PRB1925181 [KB2407160](https://hi.service-now.com/kb_view.do?sysparm_article=KB2407160) | The Script API inForeground run a subflow that calls another subflow that has mid action step throws an exception before the outputs are ready with a message | The flow should complete and the outputs displayed in Scripts - Background. However, the flow executes, but an exception is thrown: 'The current execution is in the waiting state and the subflow outputs are not available'. | Refer to the listed KB article for details. |
| Flow Engine PRB1941990 | Trigger inputs aren't accessible after a do-until loop execution | This issue is caused by the changes to GlideFlowStages Updater.java (older name GlideStage UpdateListener.java). It's observed that, in this specific flow structure, the 'in.request_item' flow input isn't passed to the 'Create Catalog Task' action. Querying the sys_flow_value table, there are 2 entries for 'in.request_item' one for the flow input and another with the parent loop associated. As the same key 'in.request_item' is now associated with parent loops, it can only be accessed in the loop body (and for the specific iteration), and all other references to it out side the loop aren't available. | 1. Import the flow XML. 2. Open Service Portal. 3. Place a request for 'iPad Pro' with the color set to 'Silver'. 4. Retrieve the RITM. Open Flow Designer. 5. Test run the flow XML with the copied RITM as the input. 6. Open the RITM when the flow waits at the AFA. 7. Approve the request created for Abel Tuter. {#yokohama-patch-9__ol_thq_wtx_2hc} Expected behavior: The flow resumes, exits the loop, and reached the 'Create Catalog Task' and will be in the 'Waiting' state. Actual behavior: After exiting the loop, it is errored at 'Create Catalog Task' with an error executing the instruction. |
| Form Controller PRB1812174 | The glide form saves the previous date | The report generates for the previous day. |   |
| GRC Platform Plugins PRB1941250 | In Yokohama and Zurich, assessment reporting views aren't displayed |   | 1. Create and publish a RAM. 2. Select the View reporting button. {#yokohama-patch-9__ol_fn2_5ng_dhc} Observe that the reporting view is not displayed. |
| HR Service Delivery PRB1880661 | The task_sla records aren't visible to the user for the records created in the 'Employee relations' table | After upgrading to Yokohama, a script is added which fails for 'Employee Relations' table records. |   |
| HR Service Delivery PRB1920738 [KB2525534](https://hi.service-now.com/kb_view.do?sysparm_article=KB2525534) | HR Case description (rich_description) doesn't copy over data, and the rich description is left empty | Rich Description appears as null in List View but displays correctly in the case record. The reverse works as expected when updating the rich_description field in the HR case form, the value will appear in the rich_description field in the list view. | 1. Log in to the instance. 2. Create an HR case. 3. Navigate to sn_hr_core_case.LIST. 4. Open the newly created case. 5. Select the Hamburger icon. 6. Configure the form layout. 7. Add the Description field. 8. Save the changes. 9. Return to the HR case form. 10. Enter a message in the Description field, but don't enter anything in the rich_description field. 11. Save the changes. 12. Observe that the same value is automatically updated in the rich_description field due to a business rule that syncs values between the two fields. 13. Open the list view. 14. Add the Description and rich_description columns. {#yokohama-patch-9__ol_in2_5ng_dhc} Notice that the rich_description field doesn't contain a value. |
| HR Service Delivery PRB1943958 [KB2570781](https://hi.service-now.com/kb_view.do?sysparm_article=KB2570781) | There's a 'You do not have permission to read the created record' error when creating an HR Case | A race condition in the UI happens when a form is submitted before the GUID is created and an empty sys_is is passed. The server-side code was not handling this. It happens intermittently. | 1. Open Create New via Agent Workspace. 2. Select the Benefits Management HR service. 3. Select Create case. {#yokohama-patch-9__ol_sn2_5ng_dhc} Notice the error, but the case gets created in backend with an empty case number. |
| Integration Hub PRB1931168 | SSE step does not run on MID |   | 1. Create an action with an SSE step and check the run on the MID checkbox. 2. Test the action. {#yokohama-patch-9__ol_wn2_5ng_dhc} Notice the error 'SSE is only available on instance'. Individual chunks are not processed by the handler. |
| Investment Portal PRB1920188 | Can't open or filter users/groups when there are a lot of records in the sys_user table | In the Investment Portal, when the user opens 'Users/Groups' and add a new user, it takes about 30 seconds to load. Search doesn't work. | 1. Navigate to Filter NavigatorInvestment Portal. 2. Open any of the bookmarked records. 3. Select the User icon to open 'Users/Groups'. 4. Select Add users. 5. Wait for it to load, about 30 seconds. 6. Try to add some letters in input. {#yokohama-patch-9__ol_zn2_5ng_dhc} Observe that it doesn't work and doesn't search anything. |
| Language and Translations PRB1910767 | The question_choice field is displaying 'um' instead of 'A' for Brazilian Portuguese language | This issue was observed when upgrading to Xanadu. | 1. Navigate to a base Xanadu or Yokohama instance. 2. Install the I18N Brazilian Portuguese Translations plugin. 3. Navigate to sys_translated.LIST. 4. Filter the table as 'question_choice' is value 'a'. {#yokohama-patch-9__ol_f42_5ng_dhc} Observe in Brazilian Portuguese language Label (translate) is displaying as 'um'. |
| Lifecycle Events PRB1926997 | Lifecycle events (LE) aren't getting if the activity set isn't created in an LE scope, and the LE uses a flow to launch activity sets | This issue occurs when Lifecycle Event and its associated activity sets are configured within an HR scope other than Human Resources: Lifecycle Events. Additionally, the sn_hr_le.use_flow property is set to true. When an HR case is submitted and fulfilled by a Lifecycle Event created outside the standard LE scope, the activity set fails to launch. The related subflow, HR Activity Launcher, ends with a status of 'Completed (error caught)'. The failure occurs in the first flow action, 'Look Up Record', which attempts to retrieve the sn_hr_le_activity_set defined in the Lifecycle Event. However, because no ACLs are defined for this table outside the scopes 'Human Resources: Lifecycle Events' or 'Human Resources: Lifecycle Enterprise', the lookup fails with an error. | 1. Create a Lifecycle Event and its activity sets in a non-LE scope. For example,'Human Resources: Employee Relations'. 2. Create an HR Service in sn_hr_er_case Centers of Excellence (COE). 3. Set the fulfillment type to 'Lifecycle Event'. 4. Use the Lifecycle Event created in step 1. 5. Complete the other HR Service setup. 6. Submit a new HR case from the new HR Service. 7. Notice there are no Activity Sets attached. 8. Open the Flow Designer. 9. Check the operations of the 'HR Activity Launcher' subflow related to the test. {#yokohama-patch-9__ol_k42_5ng_dhc} Notice that the error 'Look Up Record action, 'The requested flow operation was prohibited by security rules'' occurs in the first step. |
| Lifecycle Events PRB1945674 | Improve logging and validation in glidefix_deprecate_le_workflow for when the 'sn_hr_le.use_flow' property fails to update | The logs for the fix script doesn't re-validate the property. | 1. Install the following on a WDC instance: * HR Core * HR Lifecycle Event (HR LE) * HR Lifecycle Event for enterprise (HR LE Ent) {#yokohama-patch-9__ul_t42_5ng_dhc} 2. Upgrade the instance to Yokohama. 3. Examine the logs for the glidefix_deprecate_le_workflow fix script. {#yokohama-patch-9__ol_s42_5ng_dhc} Notice that it doesn't re-validate that the property was successfully updated. |
| List Administration PRB1847244 | Fixed filters in the Condition Builder (CB) aren't displayed after refreshing the page with the updated URL | After refreshing the page with the updated URL, the fixed filters don't appear in the CB. | 1. Log into any Yokohama instance. 2. Navigate to Service Operations Workspace (SOW). 3. Open a page with a predefined filter. 4. Select IncidentsOpen. 5. Open the Condition Builder (CB). 6. Notice that the CB should appear with the fixed filter as expected. 7. Copy the URL up until the listID. 8. Append the URL to the end of the instance's address bar. 9. Select Enter to refresh the page. 10. Open the CB again. 11. Check the filter conditions. {#yokohama-patch-9__ol_x42_5ng_dhc} Expected behavior: The fixed filters should be visible in the Condition Builder. Actual behavior: The fixed filters don' appear in the Condition Builder. |
| List Administration PRB1932703 [KB2543882](https://hi.service-now.com/kb_view.do?sysparm_article=KB2543882) | Display values aren't showing for reference fields within the 'List' component | When including a table on the 'List' component that contains reference fields, it's showing empty. Where as in platform, it shows a value. | Refer to the listed KB article for details. |
| List Administration PRB1944139 | Uptake allowExtended fields property on the lists side for the sn-field-select component | Tracking the changes for PRB1935534. | 1. Create a system property 'glide.ui.list.allow_extended_fields'. 2. Set it to 'true'. 3. Create a UI Builder page with a list component configured. 4. Set the table property 'task'. 5. Open the runtime page. 6. Select the Personalize columns button in the header. {#yokohama-patch-9__ol_fp2_5ng_dhc} Expected behavior: The fields from all tables extending from the task are displayed. Actual behavior: Only fields from the task table are displayed. |
| List Controller PRB1937947 | Additional logging for Splunk to build more context around legitimate use cases |   |   |
| List Views PRB1886477 | Selecting a 'Presentational' list component in a UI Builder (UIB) panel causes some issues | This issue was observed in Xanadu. | 1. Log in to any instance. 2. Navigate to the UIB page. 3. Create an experience with the List Page template. 4. Select Save. 5. Open in runtime. 6. Notice that the Select checkboxes are shown as expected. 7. Select Presentational list component on the UIB page configured. {#yokohama-patch-9__ol_kp2_5ng_dhc} Notice that the Select checkbox disappears and the Save button is enabled, even when there have been no changes. When selecting Save and Open the page, the Select checkbox aren't present. |
| Memory: Heap Space PRB1636231 | Memory exhausted by the Archiver Job Consumer due to syslog records stored in memory, and syslog_awa is not configured as a rotated table | Memory exhausted by the Archiver Job Consumer reparenting records from syslog table due to a problem observed when syslog_awa, which is a child table of syslog, is created without table rotation. The archiver job reparents records for the archive rules it triggers for, and will reparent a table that's not rotated. When syslog_awa isn't configured as a rotated table, the reparenting process will execute on it and its parent table syslog. Query to syslog shards are then observed, and memory is consumed as the records on these shards are stored into memory. Due to the size of it, it will cause memory to become depleted. When the archiver job is running, the localhost logs will have a large query to a syslog shard where the function reparentDocumentIDRecords is running. |   |
| MID Server PRB1923497 | Deadlock occurred due to two threads | The issue is caused by a conflict between two internal processes that manage and refresh OAuth credentials and MID Server connections. The platform periodically checks and refreshes expired OAuth tokens using a scheduled job. When this happens, the system reloads the credentials and resets all related connection data to ensure security and consistency. At the same time, if a Discovery probe or integration is trying to establish a new connection, it might attempt to access the same shared connection resources. This overlap can lead to both processes waiting for each other to finish, resulting in a temporary deadlock where neither process can proceed. |   |
| Mobile Platform PRB1951413 | Search cards based on external content can't be configured on fields created on the external content table | Creating a search card based on an external connector based table allows only certain fields to be visible. After the configuration of the mobile search card, find that the created field for mobile_url can't be used in the card for navigation. | 1. Navigate to the instance. 2. Impersonate a user. 3. Navigate to the portal. 4. In the global search, search for the keyword 'lays'. 5. Notice that the results are displayed. 6. Navigate to the 'News' tab to view the results. 7. Open the Now mobile app. 8. Log into the mobile app. 9. Impersonate Abel Tuter in Now mobile. 10. Search for 'lays' in global search. {#yokohama-patch-9__ol_qp2_5ng_dhc} Notice that no results are seen under the 'News' tab. |
| Now Assist Panel PRB1867538 | Copy for synthesized responses (auto start) on Now Assist panel (NAP) doesn't work and copies 'undefined' | When using the Now Assist panel (NAP) and entering 'Summarize a record', the Copy icon on the auto-started synthesized response does not copy the content, and instead, 'undefined' is copied. When 'Undefined' is copied instead of the content and the synthesized response is not auto-started, there is no Copy icon and a Like/dislike button is shown instead. |   |
| Now Assist Panel PRB1938963 | Text is cut off in Now Assist panel (NAP) in the text area in Spanish |   | 1. Impersonate a user. 2. Set the language as Spanish. 3. Select the NAP icon. {#yokohama-patch-9__ol_wp2_5ng_dhc} Notice that the message in the text area is cut off. |
| Now Assist Panel PRB1941558 | Now Assist panel (NAP) Assistant Information sources changes aren't saved in the guided setup | The NAP assistant default schema is set to 'None'. | 1. Navigate to Conversational interfaceAssistantsNAP assistantInformation Sources. 2. Change the KG schema to an NLQ user graph. 3. Select Save and continue. 4. Return back to the tab to ensure the changes are saved. {#yokohama-patch-9__ol_zp2_5ng_dhc} Expected behavior: The changes made in Information Sources saved. Actual behavior: The KG schema returns to 'None'. |
| Now Assist Panel PRB1942697 | The Now Assist Panel (NAP)/NASS window can't be found after closing and not pinning it | On the header, the NAP icon should be visible, but there's no option for opening it. |   |
| OneExtend PRB1938158 | Providers are restored to the default when plugins are repaired or when a new version is updated | After updating the provider to another, it gets set to the default again. | 1. Log in to the instance as an admin. 2. Navigate to Now Assist adminSettingsManage Model Providers. 3. Select Edit Model ProviderCustomizeEdit provider for skill. 4. Select a skill such as 'Incident summarization'. 5. Update the provider to any other provider, such as Google or Amazon, except for the default one. 6. Verify that the provider has been updated for the record summarization to Google in sys_one_extend_capability. 7. Repair the UXC plugin or install the latest version. {#yokohama-patch-9__ol_fq2_5ng_dhc} Notice that the provider is set to the default again. |
| OneExtend PRB1938406 | QnA Planner2 call failing with the path /v2/models/ llm_generic_large_v2/infer |   |   |
| OneExtend PRB1938474 | Entitlement_active isn't activated in the sys_geo_routing table |   |   |
| OneExtend PRB1938540 | Strange JSON format sources displayed in Now Assist Virtual Agent (NAVA) chatbot for certain queries | Issue is intermittent. | 1. Navigate to/sp. 2. Enter the utterance Create incident in the NAVA chatbot. {#yokohama-patch-9__ol_oq2_5ng_dhc} Observe the Planner 2 response displayed but with unexpected JSON style sources output at the bottom. |
| OneExtend PRB1939640 | Incident summarization doesn't work if the user enables Guardian in znowassiststable |   | 1. Enable offensiveness, block and log. 2. Enable Prompt Inject Block and log. 3. Navigate to any incident and update the short description as 'Lets kill all.' 4. Select the Summarize button. 5. Verify that it should get blocked with the error code in generative AI log table. {#yokohama-patch-9__ol_rq2_5ng_dhc} Observe that summarizing the record in the incident is stuck and works fine if disabled. |
| OneExtend PRB1940891 | The Prompt field in the 'Generative AI Log' table has extra escaped characters when using Java subflow implementation | In Java, a Prompt is converted to a string even though it's already a string before inserting it into the Generative AI Log table. There's extra escaped characters in the Prompt field. | 1. Run a capability. 2. Navigate to the sys_generative_ai_log table. 3. Check the Prompt fields. {#yokohama-patch-9__ol_wq2_5ng_dhc} Expected behavior: Users shouldn't see extra escaped characters in the prompt. Actual behavior: Valid escaped sequences are escaped unnecessarily. |
| OneExtend PRB1941124 | Claude and streaming yields significantly malformed the output | When the user enters the query in French for the first time, the streamed output has words stuck together. For example, 'basede' should be 'base de' and 'vousavez' should be 'vous avez'. When the user runs the query again, the issue doesn't persist. | 1. Ensure the instance has Claude, has streaming on, and has Dynamic Translation off. 2. Navigate to /sp. 3. Open the Now Assist Virtual Agent (NAVA) chatbot. 4. Enter the utterance, Quelles sont les options pour créer une base de connaissances?. 5. Observe that the streamed output has several words mashed together. 6. Observe that in the sys_generative_ai_log planner 2 output, the response from LLM itself is this way 7. Disable streaming. 8. Repeat the query. {#yokohama-patch-9__ol_zq2_5ng_dhc} Notice that there is no issue with the words being stuck together in the output. |
| OneExtend PRB1942490 | KB generation isn't working when requested from Now Assist panel (NAP) |   | 1. Log in to the instance. 2. Activate all FSM skills. 3. Ensure the credentials for Now LLM are updated with proxy. 4. Navigate to NAP. 5. Select Generate KB Article. {#yokohama-patch-9__ol_hr2_5ng_dhc} Expected behavior: KB generation happens successfully. Actual behavior: Notice the error message, 'Sorry, there was a problem on my side trying to complete this request. Try asking again later' and that there's an error in the sys_generative_ai_log. |
| OneExtend PRB1942618 | Script include-based capabilities aren't executed as a subflow though the required sys property is enabled |   | 1. Create a Gen AI capability with it's definition pointing to script include. 2. Ensure the sys prop 'com.glide.oneapi.run_ script_include_on_fdih _engine' is set to 'True'. 3. Ensure flow debugging is turned on for the subflow. 4. Run the script include as a FDIH subflow. 5. Execute the capability from 1 using OneExtendUtil.execute API. {#yokohama-patch-9__ol_mr2_5ng_dhc} Expected behavior: The script include is executed as a subflow and subflow executions should execute. Actual behavior: The subflow 'Run script include as FDIH subflow' won't show any executions. |
| OneExtend PRB1944861 [KB2566151](https://hi.service-now.com/kb_view.do?sysparm_article=KB2566151) | Assists Consumption for Custom Skills created in Now Assist Skill Kit |   |   |
| Platform Analytics Filters PRB1832303 | The option to select a one-day range on the calendar grid is blocked for the NextGen Dashboard | There is no option to select a one-day range on the calendar grid. The grid allows a minimum range of two days. However, if the user manually enters the end date, the filter applies without any restrictions. | 1. Log in to the UXA dashboard. 2. Select a custom range. 3. Select November 29 as the start date. 4. Attempt to select November 29 as the end date. {#yokohama-patch-9__ol_sr2_5ng_dhc} Expected behavior: A one-day range is available to the user when using the calendar grid and when entering it manually. Actual behavior: A one-day range selection is blocked on the calendar grid, but the user can manually enter November 29 as the end date and the Apply button becomes active so the user can apply a one-day range to the filter. |
| Playbook Experience Core PRB1929896 | The playbook lane isn't translated to Italian | This is an issue with record generator. It can also be reproduced by going to 'Playbook Preview' and selecting the record generator for the record. | 1. Log in to any instance. 2. Switch the language to Italian from the menu preference. 3. Open WorkspacesRisk workspace. 4. Select the List icon. 5. Select Risk assessment planningScheduled assessment. 6. Select New. 7. Observe that the playbook lane is still coming in the English language. {#yokohama-patch-9__ol_wr2_5ng_dhc} Expected behavior: The playbook lane should be translated to Italian. Actual behavior: The playbook lane isn't translated to Italian. |
| Playbooks (Family Channel) PRB1934746 [KB2592048](https://hi.service-now.com/kb_view.do?sysparm_article=KB2592048) | Playbooks archived in Xanadu don't work in newer releases | New fields that get added to the deserializer need to handle the keys not existing, which, as of now, is snapshot_id and variant_id. | Refer to the listed KB article for details. |
| Predictive Intelligence PRB1936441 | Prediction fails when a new advanced parameter is used during training |   |   |
| Project Management PRB1905989 | The Create Expenseline button from the new Costplan split button doesn't create a system generated costplan | The widget is updated, but no new system generated costplan is created. | 1. Create any planning item. 2. Add a costplan intially. 3. Select New Expenseline on theCostplan split button. 4. Add the details but don't associate it with any costplan. 5. Save the expenseline side panel. {#yokohama-patch-9__ol_gs2_5ng_dhc} Notice that the actuals widget is updated, but no new system generated costplan is created. |
| Project Management PRB1918462 [KB2532380](https://hi.service-now.com/kb_view.do?sysparm_article=KB2532380) | The system throws an error and a Resource Allocation record is not created upon creation of a Resource Assignment record on a Project Task | The user observes an error while generating a resource allocation record during the creation of a resource assignment record. | Refer to the listed KB article for details. |
| Reporting PRB1892170 | A table isn't able to select from the sys_report_source form | The table doesn't show in the list. |   |
| Security Customer Actions PRB1922115 [KB2414937](https://hi.service-now.com/kb_view.do?sysparm_article=KB2414937) | A completed user action with a canceled playbook is set to 'open' after upgrading | The user action is reset to 'Open' and the latest playbook snapshot is canceled. The action should remain in a 'Complete' state when there's no active playbook snapshot to work on. | Refer to the listed KB article for details. |
| Seismic Framework PRB1836265 | Seismic P2 Scheduler remains in an infinite loop | Performance issues on the 'Schedule' page. When switching from daily to weekly to monthly, it takes more time. After creating the schedule, sometimes the user can't see the created schedule before publishing the plan. | 1. Navigate to WorkspacesWorkplace Central. 2. Select the Preventive Maintenance icon on the side bar. 3. Navigate to All Plans. 4. Select New. 5. Select the start date and future end date. 6. Select any building. 7. Select Next. 8. Select one or more maintenance items. 9. Select Next. 10. Select Create schedule. {#yokohama-patch-9__ol_ls2_5ng_dhc} Observe it will take more time to open the 'Schedule page' and sometimes it doesn't open. |
| Seismic Framework PRB1919027 | Document requests end up using outstanding child prefetch promise | In certain scenarios, the Service Worker incorrectly fulfills a main page request using a pending iframe request. This occurs when the Service Worker matches the main page request to an existing pending iframe request, resulting in the main page loading the iframe's content instead of its own. This leads to incorrect rendering and potential functional issues on the main page. | 1. Open any UI16 page on a Next Experience enabled instance. 2. Wait for the page to load. 3. Reload the same page several times (5+). {#yokohama-patch-9__ol_ss2_5ng_dhc} Expected behavior: The navigation bar and shell to show up with UI16 content all the time. Actual behavior: Only UI16 content is shown on the page. The navigation bar and shell are missing. |
| Service Catalog PRB1831404 | Multiple dynamic behavior records are generated for a regenerate action | The ability for dynamic behavior enables the creation of AI-generated properties for questions. The design should include a clear indication when these properties are generated by AI. |   |
| ServiceNow Studio (Legacy) PRB1831690 | Progress keeps displaying 'In progress' while publishing the app | The 'In progress' state at 0% progress keeps showing when publishing the app, when the actual progress should be displayed. Once the app has finished publishing, the 'In progress' state should close out. This issue occurs on a Yokohama instance with MFA enabled and connected to pipeline. | 1. Log in as an admin user. 2. Navigate to Legacy Service Studio. 3. Create an app. 4. Publish the app. {#yokohama-patch-9__ol_vs2_5ng_dhc} Expected behavior: Progress should display the progress and close once the deployment is finished. Actual behavior: It keeps showing 'In progress' with 0% progress. |
| Service Portal PRB1839297 [KB1925168](https://hi.service-now.com/kb_view.do?sysparm_article=KB1925168) | A SPEntry page error 'Execute operation on script include 'SPEntryPage'' from scope occurs | Switching the scope and refreshing the page gives the error, 'Execute operation on script include 'SPEntryPage' from scope 'Knowledge Management - Service Portal' was denied'. | 1. Log in to a Xanadu instance. 2. Create the glide.entry.first.page.script system property. 3. Give it the value: new SPEntryPage().getFirstPageURL(). 4. Make'Knowledge Management - Service Portal' as the current scope. 5. Refresh the browser page. 6. Notice the error, 'Execute operation on script include 'SPEntryPage' from scope'Knowledge Management - Service Portal' was denied. The application ' Knowledge Management - Service Portal' must declare a cross scope access privilege. Please contact the application author to update their privilege requests.' 7. Repeat step 2 and step 3 with the scopes 'CI Landing Experience' and 'Conversational Interfaces - Diagnostics'. {#yokohama-patch-9__ol_zs2_5ng_dhc} Notice that the same error message occurs. |
| Service Portal PRB1935238 | Portal page shifts occasionally when 'Ask a follow-up' is selected |   | 1. Ensure Agentic AI is set up on the instance. 2. Enable Dispatcher Workspace (DW) on portal. 3. Search for 'Loaner Laptop'. 4. Wait for the response to load. 5. Select the Loaner laptop citation. 6. Select Request in chat. 7. Wait for the chat to open. {#yokohama-patch-9__ol_jt2_5ng_dhc} Notice that the Portal page shifts occasionally. |
| Software Asset Management PRB1771094 | A default value isn't set for some of the content tables | The default value isn't set in the dictionary for some content tables, causing it not to push the content data from stage columns to actual columns if the 'SAM - Apply latest content' job isn't run. |   |
| Software Asset Management Workspace (Glide) PRB1939252 | Backport UI changes for Software Assest Management (SAM) AI agent | Multiple UI fixes from Zurich to Yokohama. This includes message displays, navigation, and changes to the activity center. |   |
| Software Discovery PRB1579663 | File-based discovery populates the version only on the first software install record for a DM |   | Run file based discovery. Notice the software install record (cmdb_sam_sw_install) only has Publisher and Product (display names) populated. It would be good to also populate version with the normalized version if available. Some users have use cases that require a version on the install records. |
| Standard Change Catalog PRB1850616 | On Service Operations Workspace (SOW), change request template values aren't auto-populated when they are modified or retired | This issue also occurs when 'Retire an existing template' is selected. | 1. Open any instance with SOW. 2. Open SOW. 3. Select Create new change request. 4. Select Propose a new templateon the right top corner. 5. Change the field Proposal type to Modify an existing template. 6. Fill any template to modify/retire. {#yokohama-patch-9__ol_ot2_5ng_dhc} Notice that the change request values will be still empty. |
| Telemetry Glide Infrastructure PRB1920545 | CDC replication disables batch DB update operations on replicated tables causing increased upgrade time on instances |   |   |
| Tier 2 Storage Offload PRB1877226 | Conflict on a field name when creating an offload rule | When configuring an offload rule, there's a conflict if a system field is set as an indexed field. |   |
| UI Field Administration PRB1833290 | Performance issues with List field type referencing an attachment table in Workspace | A List type field that is based on the sys_attachment table shows selected attachments that have already been attached to the parent record, but there is a difference in behavior between the backend and Workspace when adding records to the field. This results in a performance issue in Workspace that is dependent on the number of records present in the sys_attachment table, which is not seen in the backend. | 1. Open a Xanadu base instance. 2. Add the List type field on incident.for for default view and workspace. 3. Configure it so that it displays only attachments associated with the parent record. 4. Enable 'Detailed SQL debugging'. 5. View an active Incident record in the backend. 6. Associate some attachments to it. 7. Select an attachment in the new List field. 8. Review the generated SQL 9. Observe the query for the sys_attachment record. 10. Repeat step 5 through step 9 using CSM/FSM Configurable Workspace. {#yokohama-patch-9__ol_ut2_5ng_dhc} Expected behavior: The user sees the query for the sys_attachment record. Actual behavior: The same querying approach for the sys_attachment record is seen, there's an additional query on sys_attachment on the File name field using the record's SysId as the value. This results in a whole table scan that returns no records. |
| UI Field Administration PRB1877769 [KB2182152](https://hi.service-now.com/kb_view.do?sysparm_article=KB2182152) | The info (i) icon for reference catalog variables is missing on requested items and the 'SCTASK' form under Service Operations Workspace | The issue is seen with all the workspaces since Yokohama. | Refer to the listed KB article for details. |
| UI Field Administration PRB1942077 | The field_list field type in workspaces should support extending child table columns | This is a product update. |   |
| UI Form Administration PRB1847354 | There's no facility for setting the default encryption of attachments to 'None' in the configurable workspace | With CLE attachment encryption enabled, if a user adds an attachment, there isn't a way to configure the UI to use 'None' as the default. If the user has access to an encryption module, it will always be the default option in the workspace UI. It's possible to customize the platform UI for this, but the workspace doesn't have this adaptability. | 1. Install CLE Enterprise. 2. Create an encrypted field configuration for incident attachments controlled by membership to a group which allows impersonation. 3. Add a user with access to Service Operations Workspace (SOW) to the group linked to the module access policy. 4. Impersonate that user. 5. Open an incident in the workspace. 6. Add an attachment. {#yokohama-patch-9__ol_c52_5ng_dhc} Observe that the list for 'Encrypt with module' will always default to the module it has access to. |
| UI Form Administration PRB1870603 | A read-only HTML field displays a horizontal and vertical scroll | The field shouldn't have a scroll bar. |   |
| Upgrade Center PRB1933942 | Skipped error after upgrading | The user gets a skipped error after upgrading the instance from Xanadu to Yokohama. The reason is 'Skipping unavailable system property glide.db.df_engine.enabled. Customers cannot configure this property.' It's included in the plugin 'com.snc.db.df_engine'. |   |
| UXF Components PRB1919730 [KB2505771](https://hi.service-now.com/kb_view.do?sysparm_article=KB2505771) | UXF page components aren't loading properly post-upgrade due to a page fragment not updating during the upgrade | When users upgrade minor patches, if there are no changes to the metadata related to macroponents, page fragment caches won't be flushed. During the upgrade process, if any user accesses pages that have asset bundles, a problem occurs. During the upgrade, asset bundling is turned off, so the macroponent page fragment doesn't have assetsInBundle, but once the upgrade is completed, asset bundling will be turned on. However, the backend is serving the old page fragment without the asset bundle context, and the macroponent asset bundle is not loaded, so components in the page won't load. | Refer to the listed KB article for details. |
| UX Framework PRB1892094 | An ATF test UI action fails due to a timeout error | The intent library delivers context on generator registration for translators that don't exist on the page. |   |
| UX Framework PRB1918913 | The js_atf_instrumentation.js script is missing when asset bundling is turned on | js_atf_instrumentation.js script, which instruments pages for component load detection and rollback during Automated Test Framework (ATF) testing, is missing when asset bundling is turned on. | 1. Navigate to MenuAutomated Test FrameworkTests. 2. Select Create your own new testGive a nameSave. 3. Add a test step to open a form in the workspace sc_taskFormOpen a new form. 4. Choose Form UISOW workspace. 5. Choose Tablesc_taskSave the test step. 6. Add Test stepFormUI action visibility. 7. Choose Visible close taskSave the test step. 8. Navigate to the test page where it lists the 2 steps. 9. Right click on the display name of the UI action visibility display name and select Add breakpoint. 10. Select Debug Test. 11. Notice that this opens the test runner in a new window. 12. Wait for the test to stop at the break point and inspect the DOM to notice the script tag for js_atf_instrumentation.js is missing. 13. Turn off asset bundling using glide property glide.uxf.lib.asset_bundle_enabled. {#yokohama-patch-9__ol_p52_5ng_dhc} Notice js_atf_instrumentation.js is available. |
| Virtual Agent Designer Legacy PRB1928396 | Date time input when used in a topic block returns null on output parameters |   | 1. Navigate to an instance. 2. Create a topic block (nlu/keywords) with data time input. 3. Add date time input to the output parameters. 4. Run the topic block and the data time returned in the output parameters in {}. {#yokohama-patch-9__ol_fv2_5ng_dhc} |
| Virtual Agent PRB1911010 | With DTAC enabled and an agent name showing in the Virtual Agent Header, VA uses an incorrect name | From the end-user perspective, an Agent's full name is displayed. | 1. Modify the 'Name' column for an Agent (for example, Abel Tuter) in the live_profile table. 2. Verify that the Live Profile name is changed to something like 'abel@example'. 3. With the Agent user, navigate to CSM/FSM or SOW. 4. Make the agent 'Available for chat' with the agent's language set to English. 5. Connect with another user in another window with the language preference set to a language other than English. 6. Navigate to /sp. 7. Open Virtual Agent. 8. Start a Live Agent conversation. 9. Check the title on the chat window. 10. Accept the chat as the agent. {#yokohama-patch-9__ol_nv2_5ng_dhc} Observe the chat title is changed from 'Abel@example' to 'ABEL TUTER'. |
| Virtual Agent PRB1915544 | The Virtual Agent (VA) topic execution returns a tool response instead of a main skill | The VA topic execution should return a main skill response or provide a way for the user to configure the topic to return a main skill response. Instead, the VA topic execution returns RAG response. |   |
| Virtual Agent PRB1936820 | Lock exceptions are noticed for Now Assist Portal (NAP) and Now Assist Virtual Agent (NAVA) |   | 1. Set up the latest ynowassiststable instance for NAP/NAVA. 2. Execute load tests for any use case of Virtual Agent. {#yokohama-patch-9__ol_fw2_5ng_dhc} Notice the exceptions are logged in the log. |
| Virtual Agent PRB1937290 | The New conversation button disappears when using certain custom branding colors | . |   |
| Virtual Agent PRB1937589 | Abnormal Generative AI Controller (GAIC) Async submission duration | SkillDetailsCache is reclaimed and cache building can be as high as 3.5s. |   |
| Virtual Agent PRB1938022 | AI Agent (AIA) Unified Planner 1 is taking up to 1.5 to 2 seconds in the Gen AI log with a single user. | The Hybrid queue take up to 500 ms. |   |
| Virtual Agent PRB1938273 | Multi-intent utterances are not working in Now Assist panel (NAP) | This issue was observed when using Azure and Gemini. Workflows are available for example both utterances, and individually both utterances are work as expected. | Enter the utterance 'Book a flight and order coffee.' Notice that the first workflow completed for both Azure and Gemini, but general react responses occur instead of triggering the next flow in Azure, and a message occurs that the workflow can't proceed in Gemini. |
| Virtual Agent PRB1938620 | The Go to search results button isn't visible in Dynamic Window (DW) | The Go to search results button isn't visible for chat-to-search transition. It should be visible, as this functionality worked in the previous release. |   |
| Virtual Agent PRB1938658 | Second intent is not going to planner 1 in continuous conversations |   | 1. Navigate to the/esc portal. 2. Open Virtual Agent (VA). 3. Enter utterance which can match multiple agents. 4. Instead of selecting an agent, enter the next utterance that can give fallback options such as 'What is ServiceNow stock price'. 5. Select Web search in the fallback option. {#yokohama-patch-9__ol_iw2_5ng_dhc} Observe that web search gives an answer for incident resolution, and not for ServiceNow stock price. |
| Virtual Agent PRB1941025 | Conversation doesn't end after catalog execution completes on standard chat |   | 1. Execute the Miro access catalog item in standard chat. 2. Finish the flow. {#yokohama-patch-9__ol_ow2_5ng_dhc} Expected behavior:The conversation ends after the execution completes. Actual behavior: The conversation doesn't ended. |
| Virtual Agent PRB1941206 | Cloned metrics aren't appearing in the list after creation | The metric appears to be created successfully, but the cloned metric doesn't appear up in the list in the home page. | 1. Create a custom metric. 2. Open the created custom metric. 3. Select Copy on the top right corner to clone the metric. 4. Select Finish setup. 5. Navigate to the home page. {#yokohama-patch-9__ol_rw2_5ng_dhc} Observe that the metric is not available. |
| Virtual Agent PRB1941593 | Using vaSystem.executeSkillWithResumeBehavior in a topic causes resume conversation to fail |   |   |
| Virtual Agent PRB1941618 | The same workflow is displayed twice in Now Assist panel (NAP) | There is only one workflow with the 'Order items' name. | Enter the utterance, 'I want to order below list of items: Coffee, Laptop, Book a flight, Pizza.' Notice that the coffee agent is completed and the same workflow is displayed twice as the following, 'To place your laptop request, use either of the available ordering workflows: it Order items -- order a laptop for you and Order items -- order a laptop for you.' |
| Virtual Agent PRB1942159 | Conversations that already have diverted to Live Agent are timing out |   | 1. Start a NAVA chat with a search phrase. 2. While waiting for the result, select the Contact Live Agent (Contextual Action) button. 3. Conduct a live agent chat. 4. Within 30-60 seconds, the conversation times out. {#yokohama-patch-9__ol_vw2_5ng_dhc} |
| Virtual Agent PRB1943087 | AI Search for semantic filters shouldn't be executed if no filters are returned | With semantic filters enabled, no filters are configured for the assistant. AI Search is getting executed for semantic filters. |   |
| Virtual Agent PRB1943466 | Now Assist Skill executing twice when running in sync mode | The main skill should execute only once. The main skill is executing twice. Please check the GenAI log and find two execution records. |   |
| Virtual Agent PRB1943976 | Need to add expensive caches as hard reference caches to avoid GC |   |   |
| Virtual Agent PRB1947698 | Only one agentic workflow executes successfully when the same trigger fires simultaneously | When a workflow trigger fires simultaneously multiple times, only one of the resulting agentic workflows executes successfully. The other workflows terminate immediately with an error indicating that no session ID could be found. Each trigger correctly creates a new execution plan and a new conversation record, but only one conversation proceeds, while the others fail at the start. | 1. Create the agentic workflow named 'Test multiple case executions'. 2. Select three or more case records and update them simultaneously so that the trigger fires for all at once. 3. Notice that the three execution plans (sn_aia_execution_plan) and three conversation records are created. Only one conversation and execution plan executes successfully. The other conversations don't continue after the first task with the error ''No session ID found'. {#yokohama-patch-9__ol_cx2_5ng_dhc} Expected behavior: Each triggered workflow should independently create or resolve its own valid session so that all conversations execute successfully, even under concurrent trigger conditions. Actual behavior: Only one conversation executes successfully. The other conversations either terminate immediately or don't continue after the first task with 'No session ID found' error. |
| Virtual Agent PRB1948321 | The send history is not returning the sequence field for the Virtual Agent (VA) API | The script should return the sequence field in response. | 1. Send history messages using the VA API. 2. Start the conversation. 3. Retrieve the history messages using the script. {#yokohama-patch-9__ol_kx2_5ng_dhc} Observe that the sequence field isn't returned. |
| Virtual Agent PRB1948603 | The DateTimePicker component breaks for the Japanese language |   | 1. Change language to Japanese. 2. Open an instance. 3. Open the /esc portal. 4. Select the date time picker demo topic. {#yokohama-patch-9__ol_ox2_5ng_dhc} Notice that the time fields are showing 00:00. |
| Virtual Agent third-party integrations PRB1941102 | Typing a response before a previous response has completed can lead to a 'technical error' in the conversation |   |   |
| Virtual Agent Web Client PRB1893104 | In Now Assist Multi-Turn Catalog Ordering, the 'Data/Time' type variable isn't showing the current time, but as 00:00AM in Virtual Agent for non-English language mode | The 'Data/Time' type variable should be displayed as the current time across all language modes. | 1. Activate the following plugin/store apps to last version: 1. UXC Generative AI (sn_uxc_gen_ai) 2. Now Assist for IT Service Management (sn_itsm_gen_ai) 3. I18N: Japanese Translations (com.snc.i18n.japanese) {#yokohama-patch-9__ol_vx2_5ng_dhc} 2. Navigate to Conversational InterfacesAssistants. 3. Enable Now Assist for Virtual Agent with 'Now Assist Multi-Turn Catalog Ordering' skill active in the Service Portal. 4. Create a catalog item with one'Data/Time' type variable. 5. Navigate to AI Search IndexIndexed Sources. 6. Open 'Catalog Item Table'. 7. Select Index All Tables so that the newly created catalog item will be included in the Virtual Agent search via AI Search. 8. Switch to the Japanese language mode after the reindex is done. 9. Navigate to Service Portal. 10. Open Virtual Agent. 11. Search the newly create catalog item. 12. Start the request. 13. Check the 'Data/Time' type variable display. {#yokohama-patch-9__ol_ux2_5ng_dhc} Expected behavior: The 'Data/Time' type variable should be displayed as the current time, which is the same in the English language mode. Actual behavior: The 'Data/Time' type variable displays as 00:00AM in the Japanese language mode. |
| Virtual Agent Web Client PRB1936255 | Turn off audio notifications by default in Now Assist Portal and Virtual Agent | As processing execution occurs, there's continuous beeps. The audio should be turned off by default. |   |
| Virtual Agent Web Client PRB1937016 | Fixing VX spacing issues | This is a product update. |   |
| Virtual Agent Web Client PRB1937432 | Fixing VX spacing issues | Issues with spacing observed Assist Virtual Agent (NAVA) and Dispatcher Workspace (DW). In issue 1, there's an extra space under 'Generating a response' for NAVA while it seems to be fixed for DW. In issue 2, spacing between the processing message container and the Sparkle icon should be 24px but it's 12px in NAVA and 24px in DW. In issue 3, processing step spacing should be 8px at the top and bottom in both NAVA and DW. |   |
| Virtual Agent Web Client PRB1940018 | Spacing not matching Figma for Conversational UX enhancements | Spacing issues in Now Assist Virtual Agent (NAVA), Dispatcher Workspace (DW), and Now Assist panel (NAP). | 1. Enter Hello. 2. Notice that the space between 'Hello' and the sparkle icon should be 12px, and is currently 24px in both NAVA, DW and NAP. 3. Notice the space between 'Let me look up for information'. 4. Hover the Copy icon to next Sparkle icon. 5. Notice that it should be 12px, has a 4px margin in DW and NAP. 6. Select Show Sources. {#yokohama-patch-9__ol_iy2_5ng_dhc} Notice that the space between the Synthesized results and the links should be 8px, and that it's 4px in DW and NAP. |
| Virtual Agent Web Client PRB1940975 | Support more markdown for text messages and synthesized responses |   |   |
| Virtual Agent Web Client PRB1941763 | The New chat button is turned off after a flow execution is complete |   | 1. Call one of the HR flows that results in successful case creation which is the end of the flow. 2. Try to start a new conversation. {#yokohama-patch-9__ol_py2_5ng_dhc} The New chat (plus button) is turned off. |
| Virtual Agent Web Client PRB1941773 | Portal page shifts occasionally when Ask a follow-up is selected | The portal page shifts to the left then returns back to its original place when the user dismisses the popup. | 1. Ensure Dynamic Window (DW) is enabled for Service Portal (SP) from the 'Assistants page' 2. Navigate to SP portal. 3. Enter What is spam in portal search. 4. Select Ask for follow up once the Results page displays. {#yokohama-patch-9__ol_sy2_5ng_dhc} Notice that DW opens with the pop-up 'Your previous chat was saved' and the portal page shifts to the left, but when the user when the user dismisses the Your previous chat was saved button, the page returns to its original place. |
| Virtual Agent Web Client PRB1948623 | Uptake new versions of Unified Experience Framework (UXF) | UXF intent library changes to Zurich and Yokohama chat-components to uptake these versions. |   |
| Web UX Runtime PRB1879187 | In Upgrade Console, the 'Guided Upgrade' page is blank for a long time when users log in for the first time | Opening 'Guided Upgrade' for the first time takes a long time to load the page. | 1. Navigate to Admin MenuUpgrade Management. 2. Select Get started from the Overview page. {#yokohama-patch-9__ol_xy2_5ng_dhc} Notice that the 'Verify Guided Upgrade' loads forever when it's the first time to log in to the instance. |
| Work Order Management PRB1920024 | Team Calendar isn't displaying events |   | 1. Impersonate as a manager. 2. Create an event to make sure that an event is there. 3. Check the Team Calendar for events. {#yokohama-patch-9__ol_bz2_5ng_dhc} The created event isn't displaying. |
| Work Order Management PRB1935240 | Duplicate events appear when the schedule of a personal event changes | When using the flat table for personal events, duplicate events appear when the schedule of a personal event changes. The old user still has the personal event displayed on DW. | 1. Make sure the flat table is turned on. 2. Open the cmn_schedule_p table. 3. Add the Schedule field on the form (if needed). 4. Open DW. 5. Create a personal event for the user. 6. Double-click (or use the keyboard shortcut) on the event. 7. Observe that the cmn_schedule_p record opens in a new tab. 8. Change the schedule to a user's personal schedule. 9. Navigate to DW. 10. Select the Refresh button. {#yokohama-patch-9__ol_ez2_5ng_dhc} Expected behavior: The personal event is only shown for the user based on the update. Actual behavior: Two personal events are shown. After the schedule changes to a different user, the old user still has the personal event displayed on DW. |
| Zing Text Indexing and Search Engine PRB1943229 | Exact match always returns the same KB on Service Portal | Exact match should only show KBs that pass certain conditions, but queries always lead to one specific KB number. |   |
[ ]

{#yokohama-patch-9__all-other-fixes}

## Fixes included {#yokohama-patch-9__fixes-included}

Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release.
Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.

* [Yokohama Patch 8 Hotfix 1](https://servicenow-prod.fluidtopics.net/q4H2r2lO16dnpC2aHXcvGw "The Yokohama Patch 8 Hotfix 1 release contains fixes to these problems.")
* [Yokohama Patch 8](https://servicenow-prod.fluidtopics.net/d6f5kXcWfwp1HgaFexLdIA "The Yokohama Patch 8 release contains important problem fixes.")
* [Yokohama Patch 7 Hotfix 4](https://servicenow-prod.fluidtopics.net/k45tyK4cqrTgLPd5LAYXKw "The Yokohama Patch 7 Hotfix 4 release contains fixes to these problems.")
* [Yokohama Patch 7 Hotfix 2a](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2556027)
* [Yokohama Patch 7](https://servicenow-prod.fluidtopics.net/Gs2iWPbHpHMxHq8yOoBAsQ "The Yokohama Patch 7 release contains important problem fixes.")
* [Yokohama Patch 6](https://servicenow-prod.fluidtopics.net/BNjEZmwQIcYFm~7CXtuiIA "The Yokohama Patch 6 release contains important problem fixes.")
* [Yokohama Patch 5](https://servicenow-prod.fluidtopics.net/Aff4QuTPpkrqeTYFQvvOuw "The Yokohama Patch 5 release contains important problem fixes.")
* [Yokohama Patch 4](https://servicenow-prod.fluidtopics.net/0NZMP7lTOVEOXCW5pwnSdQ "The Yokohama Patch 4 release contains important problem fixes.")
* [Yokohama Patch 3 Hotfix 5](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2579293)
* [Yokohama Patch 3](https://servicenow-prod.fluidtopics.net/jXrkPnnmOuaGleV7JYQPtA "The Yokohama Patch 3 release contains important problem fixes.")
* [Yokohama Patch 2](https://servicenow-prod.fluidtopics.net/gTw0R2nzVMQBcbdPC0soDw "The Yokohama Patch 2 release contains important problem fixes.")
* [Yokohama Patch 1](https://servicenow-prod.fluidtopics.net/HPuS6cI3Q9FclhqSglkLPQ "The Yokohama Patch 1 release contains important problem fixes.")
* [Yokohama security and notable fixes](https://servicenow-prod.fluidtopics.net/zY12c3el4NQneYtiA4kD1A "The Yokohama release contains important problem fixes.")
* [All other Yokohama fixes](https://servicenow-prod.fluidtopics.net/xk4JxNj~_l2ZYEt921KFzA "The Yokohama release contains important problem fixes.")
{#yokohama-patch-9__ul_o1y_kh4_dhc}

*[\>]: and then