---
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 12

# Yokohama Patch 12 {#ariaid-title1}

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

Yokohama Patch 12 was released on February 06, 2026.
:
    * Build date: 02-03-2026_1624
    * Build tag: glide-yokohama-12-18-2024__patch12-01-20-2026

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-12__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-Y12.00.xlsx).

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

Yokohama Patch 12 includes 139 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-12__security-related-fixes}

Yokohama Patch 12 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 12, refer to [KB2720387](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2720387).

## Changes in Yokohama Patch 12 {#yokohama-patch-12__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.").

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

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

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Activity Stream PRB1973244 | Texts do not clear out from Journal fields, such as comments/work notes, after selecting Save in workspaces | When inserting a text in the Journal fields and going to save the records, the journal entry is created but the text remains in the box. This happens only when using the Save button, but works correctly when using the Post button. | 1. Open any active case, problem, incident in CSM/FSM or Service Operations Workspace (SOW). 2. Insert text into the Internal Info (work notes) and Comments. 3. Select Save. {#yokohama-patch-12__ol_sg4_lhs_c3c} Expected behavior: The text disappears after the user saves it. Actual behavior: The text remains in text box after the user saves it. |
| Application Manager PRB1981044 [KB2719949](https://hi.service-now.com/kb_view.do?sysparm_article=KB2719949) | The latest version in the sys_store_app table is updated to the installed version after an install, which causes the Upgrade button to be unavailable in App Manager | Two functions (_fixLatestVersionFor WithdrawnInstalledApps, _fixLatestVersionFor WithdrawnInstalledCustomizations) in Application Manager's UpdateChecker.checkAvailableUpdates API (aka Sync in the UI) were missing a required GlideRecord.addQuery constraint when the 'sn_appclient.enable_app_ manager_checksums_cache' sys_property was set to 'true' (default). This regression led to the 'latest_version' being set to the incorrect values on Install/Sync. | Refer to the listed KB article for details. |
| Configuration Management Database (CMDB) PRB1909893 | The 'Run' filter can apply an old condition and not pick up the newly applied filter conditions | In the CMDB Relationship editor, the filter can apply old conditions and not pick up the newly applied filter conditions. This issue isn't consistently reproducible but there's a problematic API call made. |   |
| Database Persistence - Data Access PRB1829096 | There's an incorrect timeref display value for ISO week 53 | It's cosmetic as only the axis labels are affected and the real values are preserved. |   |
| Email Notifications PRB1952527 | An email template isn't applied when users select Apply template in the mini/full composer | The template isn't applied. | 1. Log in as an admin user. 2. Navigate to CSM/SOW workspace and open an incident/case record. 3. Navigate to the email tab in the activity stream. 4. Select the Apply templates icon. 5. Select a template. 6. Select Apply. {#yokohama-patch-12__ol_ij4_lhs_c3c} Expected behavior: The template should be applied. Actual behavior: The template isn't applied. |
| Internationalization Features PRB1892286 [KB2277705](https://hi.service-now.com/kb_view.do?sysparm_article=KB2277705) | A non-admin user can't change a dashboard name by specific steps when the system language is set to Japanese | The dashboard name should be updated correctly and reflected in both the primary record and its translated fields, as it is in the Washington and Xanadu versions. In the Yokohama version, the update to the dashboard name fails silently when the Japanese language is enabled and the sys_translated record exists. | Refer to the listed KB article for details. |
| Server-side scripts PRB1972733 | Field translations for security integrations are failing and return a null value | The field translations aren't working. On changing the field evaluator.withEnforcedSecurity(false), field translations work as expected. |   |
[ ]

{#yokohama-patch-12__notable-fixes}

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

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

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Advanced Work Assignment PRB1982818 | After removing a service channel, the current universal capacity of the agent isn't decreased | After removing a service channel from the 'Available' presence state, the universal capacity for the existing documents related to that channel shouldn't be considered. | 1. Create a service channel ('Chat-test'). 2. Add it to the 'Available' presence state in awa_presence_state. 3. Create related queues and assignment eligibility pools. 4. Create a universal capacity record for the agent ('Beth Anglin'). 5. Make the agent 'Available'. 6. Create documents for that and let those be assigned to the agent.Observe that the current universal capacity of the agent is increased. 7. Remove the service channel from the 'Available" presence state in awa_presence_state. {#yokohama-patch-12__ol_m31_wsr_c3c} Observe that the current universal capacity of the agent stays the same. In Xanadu and Zurich, the current universal capacity gets decreased. |
| Agile Development PRB1968771 | /sn_safe_$safe_board.do #/teamBacklog is broken | Loading different PIs in the SAFe team backlog board in Zurich isn't working. The data in the board doesn't always change and can take multiple tries to change the PI on the board. |   |
| AI Agents (Glide Family) PRB1970081 | Agent/Workflow Access not working for elevated roles | Although the user is shown to have the elevated roles, the user appears to be blocked from accessing the agent after testing the Agent Access. | 1. Create an instance with the latest track or znowassist. 2. Run the December deployment plan. 3. Create an agent. 4. Restrict the access and roles to couple of elevated roles. 5. Create a user. 6. Assign these elevated roles to the user. 7. Test the Agent Access from the Agent Studio against the user. {#yokohama-patch-12__ol_xg4_lhs_c3c} Observe that the initial screen shows the user has these elevated roles. However, after running the test, the results show that the user is blocked from accessing the agent. However, the ACL check fails, but the role masking still passes. |
| AI Agents (Glide Family) PRB1972747 | Ten assists for catalog execution in the fully agentic should be charged |   |   |
| AI Search (Glide) PRB1926964 | E5 encoding does not work when a non-base instance English (EN) record is created in the sys_language table | The issue occurs because E5 model config references sys_language records for supported languages. It saves sys_id of the record. However, if the user's instance has a non-base instance language record, it will not work with E5. |   |
| AI Search for Service Portal PRB1956814 | Pressing the 'Enter' key doesn't open the link | When the tab focus is on the link and the 'Enter' key is pressed, the link doesn't open. However, if the user presses the Tab key, the focus moves to hidden and pressing Enter opens the link. | 1. Open any base instance with AI search enabled. 2. Navigate to the Service portal. 3. Navigate to the Search edit field. 4. Search for 'email'. 5. Navigate to the search results. 6. Select a filter. 7. Navigate to any links in the 'Results' section. 8. Press the Enter key to select. 9. Verify whether it opens. {#yokohama-patch-12__ol_bh4_lhs_c3c} Expected behavior: The tab focus is on the link, and pressing the Enter key opens it. Pressing the Tab key moves the focus to the next interactive element. Actual behavior: When the tab focus is on the link and the 'Enter' key is pressed, the link doesn't open. However, if the user presses the Tab key, the focus moves to hidden and pressing Enter opens the link. |
| AI Search for Virtual Agent PRB1945491 | Tags should be passed as 'Array of Strings' not 'String' |   |   |
| AI Search UX PRB1962691 | AI Search doesn't populate sys_search_source_event with sources that weren't returned |   | 1. Enable AI Search for a portal. 2. Search for a query that doesn't return documents from a search source. {#yokohama-patch-12__ol_fh4_lhs_c3c} Observe that only the tables from search results that were returned were added to sys_search_source_event. |
| AI Search UX PRB1973402 | Genius results are stacked vertically instead of horizontally in Service Portal | This issue occurs in Yokohama and Washington DC. |   |
| Appointment Booking PRB1940645 | If users load an appointment booking on a portal home page and then use the Service Portal (SP) date picker in a different portal page, the datepicker isn't selectable until a page reload |   |   |
| Appointment Booking PRB1973793 | Blackout schedule isn't honored | Users are able to book an appointment during the blackout schedule period. | 1. Impersonate the user Ruaa Kuecken. 2. Navigate to the Credentials page. 3. Select Fingerprinting. 4. From the location drop-down list, select San Diego - Linda Vista Campus. 5. Answer the question 'What is your reason for visiting?' with 'Fingerprinting'. 6. Select the calendar icon next to Appointment. {#yokohama-patch-12__ol_ih4_lhs_c3c} Notice that appointment slots are available during the blackout schedule (for example, December 31). |
| Authentication PRB1927594 [KB2423799](https://hi.service-now.com/kb_view.do?sysparm_article=KB2423799) | Oauth token calls fail from an API authenticated sessions | As part of multi-factor authentication enforcement for local internal user logins, adaptive authentication is enabled and configured the MFA context policy. Once an API authenticated session is established, it's expected to make only API integration (or non-interactive) related calls, and the '/oauth_token.do' call falls outside of integration calls. | Refer to the listed KB article for details. |
| Case and Knowledge Management for HR Service Delivery PRB1963168 | The HRSD Knowledge Graph is unavailable after an upgrade | There's an issue with the Now Assist Knowledge graph. The user receives the error 'An unexpected error occurred. Please try again.' | 1. Impersonate a user who has access to the HR Portal. 2. Navigate to the HR Portal: https://\<instance\>.service-now.com/hr. 3. Initiate a Virtual Agent Chat. 4. Enter the prompt: 'Show me my open HR cases'. {#yokohama-patch-12__ol_mh4_lhs_c3c} Expected behavior: Information about the user's open HR Cases is displayed. Actual behavior: The user receives the error 'An unexpected error occurred. Please try again.' |
| Case and Knowledge Management for HR Service Delivery PRB1965782 | RCA created during case summarization/resolution notes generation | RCAs are generated when modifying any fields in an HR case and its child tables, which causes test failures. |   |
| Case Management PRB1821909 | RecordReferenceConnected GQL query is seen on createCase flow, which wasn't the case in Xanadu |   | 1. Open any instance on main or track/perfintegrations where CSM is installed with demo data. 2. Impersonate any user with the sn_customerservice_agent role. 3. Navigate to the CSM workspace. 4. Navigate to the case list view. 5. Select New to create a case. 6. Enter a random string in the short description. 7. Set the value of the Account field. 8. Set the Short Description field a random string. 9. Select Save. {#yokohama-patch-12__ol_ph4_lhs_c3c} Expected behavior: The user doesn't see the call to snRecordReferenceConnected. Actual result: The user sees a GQL call to snRecordReferenceConnected. |
| Change Management PRB1953175 [KB2675721](https://hi.service-now.com/kb_view.do?sysparm_article=KB2675721) | The 'Notify assessment' user notification is triggered unnecessarily for change risk assessments | The email notification is triggered by the subflow 'Notify Assessment user' at the time when a risk assessment is opened (where in theory the user completes the risk assessment). By the time the email notification is received, this message becomes unnecessary. | 1. Navigate to a change request. 2. Save the change request. 3. Open a risk assessment and complete it. {#yokohama-patch-12__ol_vh4_lhs_c3c} Observe a notification saying the user has been assigned an assessment (event 'assessment.received' in the 'sysevent' table). |
| CMDB Data Manager PRB1943938 | The Data Manager policy jobs experience increasing slowness creating tasks when processing large data sets | The CMDB Data Manager policy for running jobs keep running for a long time because the underlying SQL query has pattern of LIMIT and OFFSET on the CMDB table. The table has a lot of data, and thus those SQL queries start showing increased execution time, effectively slowing the job running them. |   |
| Communities PRB1952833 | Blog posts within Community forums have all been reformatted | The HTML code not showing properly on blog in community portal. |   |
| Configuration Management Database (CMDB) PRB1894727 | Duplicate approvals are created for the same users for CMDB Data manager tasks while in the 'Requested' state | This issue shows up when there are multiple archive policies generating each at least one task. It might be applicable for retire or delete policies too. |   |
| Data Archiving to Object Store PRB1890833 | Corrupted attachments cause repeated offload failures, chunk starvation |   | 1. Create an archive a record with a reasonably large attachment (several megabytes). 2. Delete one of the sys_attachment_doc records for this attachment. 3. Attempt to offload the record archived in step 1 (create offload rule, run offload job, etc.). {#yokohama-patch-12__ol_xh4_lhs_c3c} The offload errors out both now and on every subsequent reattempt. If enough attachments get corrupted, it can have broken chunks on every reattempt, preventing anything being offloaded for this rule. |
| Data Archiving to Object Store PRB1893485 | If a related record hasn't finished offloading, 'Restore from Tier 2' can cause unpredictable results | This is hard to reproduce without a large backlog to offload. | 1. Archive a record and its related record. 2. Serialize the related record to a string and retain for now. 3. Offload the record (and the related record). 4. Simulate that the offloaded record is incomplete by changing its chunk status in sys_archive_tier2_chunk to 'running'. 5. De-serialize the string from step 2 back into the 'Archive' table. 6. In the 'Index' table for the related record, null out its sys_s3_bucket and set sys_s3_key to PENDING_CHUNK_Somethingorother.Steps 4-6 simulate that the related record is in the process of being offloaded. 7. Restore the parent record to Tier 1. {#yokohama-patch-12__ol_a34_lhs_c3c} Notice that when restoring offloaded record, it's not being added to SYS_ARCHIVE_TIER2_SKIP table, even though the un-offload operation is successful. |
| Database Persistence - Data Access PRB1924708 | Show Matching a list and order by ref_ fields throws NPE | After the user orders the list, the records disappear. | 1. Navigate to task.list. 2. OpenConfigureList Layout. 3. Add the planned start date \[change request\] to the list of columns. 4. Save. 5. Add watch list to the view. 6. Populate the watch list of some records. 7. Show Match watch list. 8. Order by the planned start date \[change request\]. {#yokohama-patch-12__ol_i34_lhs_c3c} Expected behavior: The records show. Actual behavior: The records disappear. |
| Database Persistence - Data Access PRB1944597 | Multiple applications under the same sys_scope create an invalid GraphMetadata Object | An error occurs. | 1. Install CCOE-Global custom application or any application that is within a global scope. 2. Create a new knowledge graph under CCOE-Global. 3. Perform new sn_db.GraphMetadata ('global.graph_name').get();. {#yokohama-patch-12__ol_m34_lhs_c3c} Notice the error, 'No graph named global.graph_name was found.' |
| Database Persistence - Data Access PRB1968109 | When glide.db.aggregate. groupby_display_optimize is true, group by reference fields display value is a sys_id |   |   |
| Database Persistence - Data Scale PRB1889276 | deleteMultiple fails for PG for IN conditions larger than 1000 | A NullPointerException is thrown: 'Exception attempting to delete from: u_cstask_multiple_delete: java.lang.NullPointerException: Cannot invoke 'java.util.List.addAll(java.util.Collection)' because 'this.fPlaceHolders' is null: com.glide.db.conditions.ASetCondition .formatFieldSet(ASetCondition.java:265) com.glide.db.conditions.ASetCondition .formatSet(ASetCondition.java:157)'. | 1. Create a table 'u_cstask_multiple_delete'. 2. Add a single string column 'end_of_life_item'. 3. Generate around 10,000 items. 4. Try to delete them using Glide record and IN condition. 5. Make sure to put more than 1,000 values into the addQuery IN values. {#yokohama-patch-12__ol_p34_lhs_c3c} Observe that a NullPointerException is thrown. |
| Database Persistence - Data Scale PRB1945816 | A connection pool should properly handle errors during expansion | This issue was observed in a user's production instance where the PRI database connection pool became exhausted. The exhaustion occurred because several threads were holding PRI DB connections while executing queries on the RR database. During this time, the RR database went down (due to a hardware failure), and these threads remained blocked for approximately 10--15 minutes, resulting in pool exhaustion. | 1. Create an instance that has a read-replica DB. 2. Execute repeated transactions that result in routing some, but not all, of the queries to the read replica. 3. While these queries are running, the read-replica database must go down (either kill -9 or unplug the box). {#yokohama-patch-12__ol_s34_lhs_c3c} Observe that the system becomes unavailable for 10-15 minutes until the transactions begin to timeout. |
| DevOps (Family) PRB1974768 | Duplicate pull requests are created due to a concurrency problem | Database level uniqueness isn't present and, as a result, a duplicate record is created when a race condition happens. |   |
| Discovery PRB1895238 [KB2249032](https://hi.service-now.com/kb_view.do?sysparm_article=KB2249032) | Cloud Application Patterns are launched sequentially and contribute to the long discovery schedule | The launching time of massive number of probes should be improved. | Refer to the listed KB article for details. |
| Discovery PRB1903928 | Slow query with primary_hash= -865319141 runs 60k times per day, consuming reasonable time from the database | Users with a relatively high number of records on cmp_discovery_ldc_config may be affected by query primary_hash= -865319141. It can run thousands of times, reading the entire table. |   |
| Discovery PRB1969791 | The Discovery Pattern logs say Warning CI Pattern is completed, even though the pattern failed completely | Even though the classification is successful, if the pattern fails to get the basic identification details such as name, serial number, etc., the pattern fails completely. However, the Discovery Pattern logs say that the Warning CI Pattern was completed but failed some post-processing steps. | Run an SNMP Discovery. Observe that the pattern fails if it fails to get the basic identification details. However, the Discovery Pattern logs say the Warning CI Pattern was completed but failed some post-processing steps. |
| Discovery PRB1974425 | Make the Discover Now button primary in the workspace 'Form' view | Update the button style on the existing UI action record for Discover now to mark it as primary. | 1. Navigate to Discovery Admin WorkspaceSchedules. 2. Select any IP-based schedule. 3. On the 'Schedule Details' page, select the 'Schedule Details' section. {#yokohama-patch-12__ol_x34_lhs_c3c} Expected behavior: As one of the main UI actions on each schedule form is Discover Now, it should be displayed as a primary button. Actual behavior: Notice that the style of the Discover Now action button displayed isn't 'primary'. |
| Document Viewer PRB1947203 | After upgrading to Yokohama, there's an issue during the generation of a PDF file for a custom audit process using the PDFGenerationAPI library | The URL of an image or some function of the style of the HTML text used as the basis for the PDF file isn't converted or supported. | 1. Take the Corporate FSQ Audit engagement field (engagement_type) with the status (state) as 'Follow Up' (5). 2. Verify that the Report field (kb_article) is populated. 3. Verify that the Audit Report State field (u_audit_report_state) is 'Final Report Delivery' (final_review). 4. Select the Preview Audit Report UI action that appears. {#yokohama-patch-12__ol_aj4_lhs_c3c} An attachment should automatically be generated and be attached to the engagement in question, but nothing happens. |
| Email Notifications PRB1942395 | The cursor moves to the end of an input field when the CPU throttling is 4\* slower and 6\* slower |   | 1. Log in as an admin user. 2. Navigate to CSM Workspace. 3. Open a case record. 4. Navigate to Compose email. 5. Change CPU throttling in the 'Network' tab to 4\*slower/6\*slower. 6. Type continuously. {#yokohama-patch-12__ol_fj4_lhs_c3c} Expected behavior: Drafting an email shouldn't encounter unexpected cursor placement to the end. Actual behavior: The cursor jumps to the end while typing. |
| Event Management PRB1953971 | There are two columns named 'text' in the table sa_agg_alert_filter, but one of them should be network_traffic | The label is 'Network Traffic', but the column name is 'text', so there's no separated flag for network traffic. |   |
| Event Management PRB1954172 [KB2615509](https://hi.service-now.com/kb_view.do?sysparm_article=KB2615509) | Automated group is created even if some of the alerts don't match the aggregated alerts filter | Defined alert aggregation filter sa_agg_alert_filter isn't working and alerts are still grouped. | Refer to the listed KB article for details. |
| Event Management PRB1978591 | PRC list contains new and outdated change requests that should be filtered out |   | 1. Set sa_analytics.rca_use _legacy_query to true. 2. Create a change request on a CI and leave it in a 'new' state. 3. Create another change request on the same CI with an implementation date set to one week ago. 4. Generate an alert on the same CI. 5. Verify the Probable Root Cause list. {#yokohama-patch-12__ol_lj4_lhs_c3c} Expected behavior: Both CRs should be filtered out (one for being in 'new' state, one for being outdated). Actual behavior: Both CRs appear in the PRC list. |
| Flow Engine PRB1971237 | Unable to run 65M Load Test |   | 1. Log in to the instance. 2. Under CISP Test suites, select NMA_Mock: 65M_NMA_MT_Equip_Data_Update. 3. Select Execute Tests. 4. Select Execution Profile as Nested Payload. 5. Select OK. 6. Check CISP executions for the results. {#yokohama-patch-12__ol_qj4_lhs_c3c} Observe that certain executions didn't run. |
| GRC Platform Plugins PRB1972072 | The P95 response time for task page loading across all the workspaces exceeds SLA of 4 seconds |   | 1. Log in to an instance. 2. Navigate to Risk/Audit/Compliance/ESG/Privacy WS. 3. Select Task Page Widget. {#yokohama-patch-12__ol_uj4_lhs_c3c} Observe that the P95 response time exceeds SLA of 4 seconds. |
| Horizon Image Component PRB1803287 | The 'Fit' property doesn't work with max-width attribute | The now-image tag calculates to new resize events, but the 'img' tag remains the full width despite the values is in the 'Fit' property. | 1. Open a UI Builder page. 2. Place a carousel component. 3. Add 2 to 3 now-images components with some default photos within the carousel content slot. 4. Navigate toNavigation and interactionCarousel configuration. 5. Set 'Number of items in view' to 'Single content item'. 6. Attempt to resize the window. {#yokohama-patch-12__ol_xj4_lhs_c3c} Observe that the now-image tag has max-width dynamically calculated to new values on resize events, but the 'img' tag inside now-image still keeps the full width despite the options specified in now-image's 'Fit' property. |
| HTTP Client PRB1959206 | Introduce Mechanism to Set Connection Pool Timeout on the Instance to Prevent Semaphore Exhaustion | This is a product update. |   |
| Install Base Management Store PRB1972327 | Instance Performance issue due to No NULL checks in the InstallBaseUtilSNC base instance script include | 'sn_customerservice .unified_consumer role' was added to a group, causing a cascading change to 27 child groups containing over 7000 users. Subsequently, users with this new role who didn't have a corresponding entry in the consumer table were caused to run a 'select \*' query on 'sn_install_base' tables. This results in queries of tables containing over 2 million records being continuously executed. | 1. Open a base instance. 2. Try to assign 'sn_customerservice .unified_consumer role' to a high number of users (or any group with a lot of members). 3. Try to open any case as any user from the above list. {#yokohama-patch-12__ol_ck4_lhs_c3c} Observe the slowness. Global.CSManagementUtils.getConsumerID() returns null for a user who doesn't have a record in csm_consumer table and has a unified_consumer role. This method is used in other methods, which are used in dynamic filters. |
| Instance Data Replication (IDR) PRB1821656 | A carriage return character (\&#13;) is added | A carriage return character is added when work notes or additional comments are synced to an instance. | 1. Navigate to a producer instance. 2. Make a multi-line comment. 3. Save. 4. Navigate to a consumer instance. {#yokohama-patch-12__ol_fk4_lhs_c3c} Observe that the carriage return character (\&#13;) is added to the new line. |
| Internationalization Features PRB1912273 | After a Yokohama upgrade, catalog admins can't create new sys_translated records | Since the upgrade to Yokohama, it's no longer possible for catalog_admin users to create records in table \[sys_translated\], only update existing ones. | 1. Provision a Yokohama base instance with a language plugin installed. 2. Create a testuser with the role catalog_admin to access the catalog items and their variable sets and variables (but not the sys_translated table directly). 3. As sys_admin, create two variables for any catalog item. 4. Add a translation for one of the two variables. 5. Switch to testuser. 6. Open the catalog item. 7. Change the preferred language to the one associated with the plugin (make sure that the translation exists). 8. Change the English value to a translation for the variable that wasn't translated yet. 9. As sys_admin, check on the sys_translated table directly.Observe that the change is instantly reverted after trying to save it and isn't saved. 10. As testuster, adjust the existing translation of the variable question text for the translation that already exists. {#yokohama-patch-12__ol_ik4_lhs_c3c} Observe that the adjustment is saved correctly and can be found in the sys_translated table, with 'updated' and 'updated by' correctly updated to the testuser. |
| Key Management Framework (KMF) PRB1906571 | Password2 system properties return an encrypted value after a node restart for on-prem instances | In on-premises environments, database (DB) properties aren't being correctly decrypted and remain encrypted in memory. |   |
| Key Management Framework (KMF) PRB1906606 [KB2601723](https://hi.service-now.com/kb_view.do?sysparm_article=KB2601723) | SEK rekey fails for records with undefined or invalid sys_id or invalid table | Bagheera should handle undefined/null/empty sys_id records. | Refer to the listed KB article for details. |
| Language and Translations PRB1978639 | Translations merge for Yokohama to fix an issue introduced in a previous patch | This is a GenAI translation update. |   |
| Multi-provider Single Sign-on (SSO) PRB1920554 | The 'Check certificate expiration' job fails daily | If the user runs the job 'Check certificate expiration' on an instance with multiple certificates, the localhost_log shows an issue for every certificate that got null. |   |
| Next Experience Unified Navigation PRB1975305 | AI Engagement Experience (AIEX) upgrade issue | When a user upgrade Yokohama, they won't get any of the new AIEL changes. This occurs when upgrading from version 27.0.29, which has UXR components, to version 27.0.28-aiex.13. |   |
| Now Assist for Software Asset Management (SAM) PRB1951872 | The user resolution rule is created in a global domain instead specific domain | The user resolution rule is created in the global domain instead of the child domain 'A1'. | 1. Created a parent domain 'A'. 2. Create child domains 'A1' and 'A2'. 3. Create an integration profile in domain A1. 4. Create a custom field as Work Email in the sys_user table in domain A1. 5. Run the scheduled job to pull the subscriptions in domain A1.Notice that the user resolution rule creation schedule job is triggered, and rule is getting created. {#yokohama-patch-12__ol_sk4_lhs_c3c} Expected behavior: The user resolution rule is created in domain A1. Actual behavior: The user resolution rule is created in the global domain. |
| Now Assist Panel PRB1985088 | Link in NASS doesn't open in a new tab |   | 1. Navigate to full page. 2. Search 'What is spam?'. 3. Select the source link for the KB. {#yokohama-patch-12__ol_jvv_x1g_d3c} Expected behavior: The KB link opens in a new tab. Actual behavior: The KB link doesn't open at all. |
| On-Call Scheduling PRB1909337 | No response after selecting On-Call Calendar if there's no shift in cmn_rota | When the user tries to select On-Call Calendar, there's no response and no message, but a green border is displayed for an unknown reason. It seems related to the presence or absence of shift(cmn_rota). Instead, the system should display a meaningful message on the page when no shifts are available. | 1. Execute cmn_rota.list. 2. Confirm that there are no records. 3. Navigate to On-Call Scheduling. 4. Select On-Call Calendar. {#yokohama-patch-12__ol_xk4_lhs_c3c} Observe that there's no response and no message, but a green border is displayed for an unknown reason. |
| On-Call Scheduling PRB1938628 | When adding a coverage to a shift, the user is displayed two times on the 'day' view of the on-call schedule |   | 1. Create two or more shifts for a group. 2. Ensure that one shift is using new schedule engine, and the other one with the old schedule engine. 3. Add coverage to users in the new schedule engine. 4. Select the shift in the classic calendar to view the on-call persons. {#yokohama-patch-12__ol_zk4_lhs_c3c} Observe that users are displayed twice. The user should be displayed only once. |
| On-Call Scheduling PRB1967490 | OnCallRotation.getPrimaryUser returns null for across day shift time while using 2024_schedule_engine | The script to get the primary on-call doesn't return valid data. Instead, it returns a null value. |   |
| OneExtend PRB1925002 | Agentic Workflow's trigger sys_user is taking precedence over run as 'AI User' | When trigger conditions are met, the workflow should be executed with workflow's 'Run As' user for the new incident. However, the workflow is actually executed with the trigger's sys_user and the execution is terminated with the error 'Access Denied'. |   |
| OneExtend PRB1971589 | cypher2Results API is broken with glide record dynamic | A Null Pointer Exception is coming from OneExtend: 'Couldn't decipher the stack trace resulting from the following JavaScriptException.' |   |
| OneExtend PRB1973586 | A newly changed LLM provider setting is reset after upgrading | After upgrading an instance to Zurich but not upgrading Generative AI Controller and Now Assist Admin apps to the compatible latest available versions, the LLM provider setting reverts to its pre-upgrade value within two hours or less after being changed through the 'Edit Model Provider' option in Now Assist Admin. This behavior may cause configuration instability after the upgrade. |   |
| OneExtend PRB1974084 | Error during zboot due to a 'where' clause on sys_db_view_table |   |   |
| OneExtend PRB1978709 | Now Assist panel and AI Agents fail because outbound URLs ignore the project ID of the connection URL (sys_alias) | In the Gemini BYOK integration, outbound requests made by Now Assist panel and AI Agents fail because the generated outbound URLs don't include the project ID from the connection URL (sys_alias). These features rely on the Java proxy to construct outbound URLs, but the proxy doesn't append the project ID. As a result, calls are sent to an incorrect or incomplete Gemini endpoint, and the user gets the error 'Invalid HTTP response 404: Not Found'. In contrast, Incident Summarization and Code Generation features work correctly because they use the Flow Designer, which properly constructs outbound URLs and includes the project ID as part of the request path. Because Now Assist panel and AI Agents bypass Flow Designer and instead use the Java proxy that omits the project ID, their outbound calls fail consistently. |   |
| OneExtend PRB1981515 | Add enhanced debug logging around async client call | Debug logs need to be added when each streamed chunk is received, when the final callback is received (VAStreamConsumer), before enqueueing in the hybrid queue, and after enqueueing in the hybrid queue and the callback is complete. |   |
| Platform Analytics Migration API PRB1797363 | Scheduled reports are migrated even if they aren't active |   | 1. On track/dataanalytics, change the 'com.glide.par.unified_analytics.enabled' property to false to trigger migration. 2. Open a report. 3. Schedule a report. 4. Open the scheduled report. 5. Set the active field to false so the scheduled report isn't sent automatically. 6. Run migration from the migration center. 7. After migration is complete, activate migration. 8. Navigate to the 'Scheduled Export' library. {#yokohama-patch-12__ol_dl4_lhs_c3c} Expected behavior: The scheduled report isn't migrated. Actual behavior: The inactive scheduled job is migrated as active. |
| Platform Analytics Migration API PRB1962944 | Duplicate records are created in the analytics_category_m2m table when using UnloadDashboard before and after Platform Analytics migration | In the Zurich release, when a Core UI dashboard is exported from a source instance using UnloadDashboard before a Platform Analytics migration, and then the same dashboard is migrated to a Platform Analytics dashboard and exported again using UnloadDashboard after migration, duplicate category records are created in the analytics_category_m2m table upon importing to the target instance. This issue occurs when both the source and target instances perform the migration process and the migrated dashboard is re-imported through an update set. As a result, the migrated dashboard in the target instance displays two identical categories, with duplicate links in the analytics_category_m2m table. | 1. In the source instance, create a new update set and set it as current. 2. Create a Core UI dashboard and assign it to a dashboard group. 3. Use the UnloadDashboard functionality to record the dashboard into the current update set. 4. Mark the update set as 'Complete' and export it to an XML file. 5. In the target instance, upload, preview, and commit the update set XML file. 6. In both the source and target instances, migrate the Core UI dashboard to a Platform Analytics dashboard using Migration Center. 7. In the source instance, create an update set and set it as current again. 8. Use UnloadDashboard again (this time after the Platform Analytics migration) to capture the Platform Analytics dashboard into the update set. 9. In the target instance, upload, preview, and commit this new update set XML file. 10. In the target instance, open the migrated Platform Analytics dashboard and verify its category. {#yokohama-patch-12__ol_jl4_lhs_c3c} Observe that duplicate records are created in the analytics_category_m2m table. |
| Platform Licensing PRB1980200 | True-up of SM and LE 6.0.2 | This is a product update. |   |
| Process Mining Workspace PRB1916916 | When datetime is selected as Activity Definition, the grouping of activities isn't working |   |   |
| Process Mining Workspace PRB1949520 | Users aren't able to view processes if they have access to only some of the records from that table |   | 1. Impersonate abel.tuter. 2. Open the 'Process config' list from Process Mining Workspace. 3. Select the wrench icon on the sidebar. 4. Select the kb_knowledge record from the list. {#yokohama-patch-12__ol_em4_lhs_c3c} Observe that a 'You don't have required access to the Knowledge table for viewing this configuration' error displays even though the user has access to some records in the kb_knowledge table. |
| Process Mining Workspace PRB1955632 | The 'Top 5 opportunities type' graph isn't displaying the improvement opportunity type with the highest records |   | 1. Navigate to the 'Summary and insights' page after adding findings. 2. View the 'Top 5 opportunities type' graph. {#yokohama-patch-12__ol_hm4_lhs_c3c} Observe that the data is not sorted with highest record frequency. |
| Procurement PRB1970134 | 'Receive by' isn't populated when receiving through the stockroom import flow | In a normal PO flow, 'Received by' is populated by the user who received the assets. However, in the import flow, it's shown as empty. | 1. Log in to the instance. 2. Create a purchase order. 3. Create a purchase order line with Apple Mac, with quantity set to 3. 4. Open the stockroom page. 5. Complete the import flow for the above POL. 6. Provide the details for 3 assets. 7. Select Receive. {#yokohama-patch-12__ol_jm4_lhs_c3c} Observe that 'Receive by' isn't populated on the receiving slip. |
| Resource Management PRB1941447 [KB2552237](https://hi.service-now.com/kb_view.do?sysparm_article=KB2552237) | The assignment FTE falls to an incorrect value due to lack of availability adjustment to 24 hours in the monthly view of RMWS | The issue is caused by not adjusting availability to 24 hours. It should adjust availability to 24 hours and redistribute hours evenly. | Refer to the listed KB article for details. |
| Server-side scripts PRB1974676 | Guest sandbox logging can potentially overwhelm system logs |   |   |
| Server-side scripts PRB1974683 | Rules for static analysis feature are locked behind no_db_override |   |   |
| Service Catalog Builder PRB1982503 | In Yokohama, the Continue button doesn't work and the Preview button is missing in the canvas view of t2c- 6.0.7 |   | 1. Open a Yokohama instance with NAFC 27.6.1. 2. Enable the T2C skill. 3. Navigate to Catalog Builder. 4. Select Build with Now Assist. 5. Enter any utterance. {#yokohama-patch-12__ol_om4_lhs_c3c} Observe that the Preview button is missing and the Continue button doesn't work. |
| Service Portal PRB1935624 | Hide filters and Clear All in a facet search aren't properly aligned | The Hide filters and Clear All options are showing, but they aren't aligned. There are a few pixel mismatches. | 1. Search for something in ESC portal.Observe the facets on the right side. 2. Choose one of the sources so Clear All shows up. {#yokohama-patch-12__ol_rm4_lhs_c3c} Expected behavior: The Hide filters and Clear All options are aligned. Actual behavior: The Hide filters and Clear All options are showing, but they aren't aligned. There are a few pixel mismatches. |
| Software Asset Management PRB1968916 | Fetch transactionId by failed job name and profile Sys ID |   |   |
| Software Asset Management PRB1974875 | Job failure troubleshooting for family releases | This is a product update. |   |
| Software Asset Management Publisher Pack for Microsoft PRB1871730 | The 'Collect CAL Info' extension section causes a huge payload for Windows discovery | When running Windows OS - Servers patterns, if the server has a large amount of records in the MsftUal_DeviceAccess and MsftUal_UserAccess through WMI queries, then the payload is substantial. Such large payloads may cause mutex locks and impact performance. |   |
| Software Asset Management Publisher Pack for SAP PRB1887429 | Automatic software model isn't created | An automatic software model isn't created for the Default Named User Type in the Default Price List as specified in the SAP connection. | 1. Set the 'com.snc.samp.automaticsmrcreation' system property to true. 2. Create a SAP Connection and SAP Client. 3. Create different types of SAP System Users. 4. Verify that the discovered user records were created. 5. Run recon. 6. Verify that only SAP system users of user type 'Dialog' are reconciled. {#yokohama-patch-12__ol_tm4_lhs_c3c} Observe that an automatic software model isn't created for the Default Named User Type in the Default Price List as specified in the SAP connection. |
| Software Discovery PRB1967095 | Software Asset Connections doesn't set the last scanned on cmdb_sam_sw_install | Synch installed software pattern pre/post script should get the discovered date from cmdb_ci_appl. |   |
| Software Entitlements PRB1943125 [KB2541050](https://hi.service-now.com/kb_view.do?sysparm_article=KB2541050) | Total cost calculation in software entitlements for workspace is different than on the form | The total cost displayed for software entitlements in the Software Asset Workspace (SOW) view is incorrect when compared to the form view of the same entitlement. The SOW is adding additional decimals on some occasions, which isn't consistent with the form view, which would have a rounded number. For example, Workspace: 10,441.5591 compared to Form: 10,440. This issue arises from the different outputs of the UI scripts CalculateTotalCostWS .getTimeSpan() and CalculateTotalCost .getTimeSpan(), which should, but doesn't yield consistent results. This issue impacts the visibility of accurate cost information in software asset workspace. | Refer to the listed KB article for details. |
| Source-to-Pay Operations (Glide) PRB1978443 | Integer to decimal changes, Java level changes |   |   |
| UI Field Administration PRB1881510 | The category under 'change request values' on the standard change template isn't reflected in Service Operations Workspace | This issue is present in the base instance as well. The Category field is visible, but the value set for the category isn't visible under 'change template values'. | 1. In the application navigator, navigate to ChangeStandard ChangeMy ProposalsNew. 2. Create a new template with the change request values filled in. 3. Request approval. 4. In Service Operations Workspace, navigate to ListTasksAssigned to you (remove the filter if required). 5. Open the standard change template. {#yokohama-patch-12__ol_ym4_lhs_c3c} Observe that the category under 'change request values' isn't reflected. |
| UI Field Administration PRB1937530 | Reference fields do not display correctly | When creating an incident using the Create Incident UI Action from a record page that uses UI Builder form components, reference fields may not display correctly. | 1. Navigate to Service operations workspace. 2. Select the plus icon. Notice that the interaction form page appears. 3. Populate the below fields in the interaction form. 1. Caller: Select any caller. 2. Configuration item: Select any CI. 3. Service: Select any service. {#yokohama-patch-12__ol_fn4_lhs_c3c} 4. Select Save. 5. In the interaction form view, populate the Short description field. 6. Select Create incident. {#yokohama-patch-12__ol_en4_lhs_c3c} Notice in the incident workspace view under the assignment section that the Configuration item field and Service field are missing. |
| UI Field Administration PRB1945077 | Click-to-call ignores the E.164 country code and defaults to +1 | The 'Click-to-call' feature is incorrectly dialing US numbers instead of international numbers like the UK or India, regardless of the country code. Dialing from the contact card works correctly, but using the Click-to-call icon always defaults to US numbers. | 1. Navigate to the CSM Workspace 2. Open a Case record. 3. Select the Information icon of the Contact field. The User account will open. 4. Select the Phone icon of the Business phone field. {#yokohama-patch-12__ol_ln4_lhs_c3c} An outbound call is placed, and an interaction record is created. |
| UI Form Administration PRB1953177 | now-stylized-text is not supported in Yokohama so the tagline component is not rendered in workspace | This issue occurs in Yokohama. | 1. Log in to a ynowassist instance with GenAI setup. 2. Open UI Builder. 3. Select any of the configuration workspaces (example: CSM/SOW). 4. Open an SRP record page. 5. Add a tagline component. 6. Generate a record with a GenAI agent or attached background script. 7. Open the same record in the configuration workspace. {#yokohama-patch-12__ol_on4_lhs_c3c} Expected behavior: The tagline component is displayed in the workspace. Actual behavior: The now-stylized-text isn't supported in Yokohama so the tagline component isn't rendered in the workspace. |
| Usage Analytics PRB1963094 | Users aren't able to interact with the Unified Navigation menu when the web SDK configuration becomes empty | Unified Navigation Menu interaction is stopped when the legacyConfig in sessionStorage is emptied by some scripts, causing errors related to trackingConsent and page freezing upon interaction. This restores smooth navigation between menu items. | 1. Load the home page. 2. Open 'Inspect' mode in the browser. 3. Navigate to the 'Application' tab. 4. Delete the session storage. 5. Try to interact with Unified Nav or other section of the page. {#yokohama-patch-12__ol_tn4_lhs_c3c} Check that there's an error for tracking consent and the page is freezing. |
| Virtual Agent PRB1768573 | Profanity filter keyword issues | Profanity filter keyword mode flags non-profane words that contain otherwise profane words. |   |
| Virtual Agent PRB1975277 | The actual status of the additional chat features isn't reflected in the base instance NAVA assistant test window | In the test panel, the values of 'Allow web search', 'Allow response streaming', and 'Allow document uploads' are shown as 'Inactive'. This doesn't reflect the values set in the 'sys_now_assist_deployment _config_attributes' table. | 1. Navigate to AllAssistant Designer. 2. Ensure that you have active assistants 'Now Assist Panel - Platform (default)' and 'Now Assist in Virtual Agent (default)'. 3. Navigate to the settings of 'Now Assist in Virtual Agent (default)'. 4. In the 'Additional chat features' section, select the Allow web search, Allow response streaming, and Allow document uploads options. 5. Save the assistant. 6. Make sure the same options are selected for 'Now Assist Panel - Platform (default)'. 7. Navigate to the table 'sys_now_assist_deployment _config_attributes'. 8. Search for 'doc_qna', which is responsible for 'Allow document uploads'. 9. Verify that it is set to 'true' for both assistants (since it was selected in the earlier steps). 10. In the same table, search for 'streaming_enabled' and 'web_search_enabled'. 11. Verify that they're also set to 'true' for both assistants. 12. Navigate to AllDesigner. 13. From the 'Select assistant' drop-down list, select Now Assist Panel - Platform (default) assistant. 14. Select the Test assistant button. Observe that the test panel opens, and the values of 'Allow web search', 'Allow response streaming', and 'Allow document uploads' are shown as 'Active'. 15. From the 'Select assistant' drop-down list, select Now Assist in Virtual Agent (default) assistant. 16. Select the Test assistant button. 17. Select one of the available chat options. {#yokohama-patch-12__ol_a44_lhs_c3c} Expected behavior: In the assistant test panel, the values of 'Allow web search', 'Allow response streaming', and 'Allow document uploads' are shown according to the actual values set in the 'sys_now_assist_deployment _config_attributes' table. Actual behavior: The test panel opens, and the values of 'Allow web search', 'Allow response streaming', and 'Allow document uploads' are shown as 'Inactive'. |
| Virtual Agent PRB1975617 | Failing to send an agent joined message |   |   |
| Virtual Agent PRB1982735 | Handle an unknown document_id field in the sys_cs_provider_application |   | 1. Set up Glide NLU or Now Assist. 2. Set up the appropriate Teams version. 3. Start a conversation from a bot. {#yokohama-patch-12__ol_rd1_1sr_c3c} Logs have an unknown field document_id in sys_cs_provider_application exception for every Teams request. |
| Virtual Agent Web Client PRB1927910 | When initiating a chat with Enhanced Chat active in a portal, the + button to start a new chat remains disabled after the chat times out | Users must refresh the page to re-enable the + button. | 1. Ensure that the Enhanced Chat bot is added to the portal by navigating to Conversational InterfacesAssistantsNow Assist in Virtual AgentDisplay Experience. 2. Confirm that the portal (for example, Employee Center) has Enhanced Chat enabled. 3. Navigate to Employee Service Center. 4. Initiate a chat session.Observe that the + button for starting a new chat is disabled. 5. Leave the chat open until the abandon timeout occurs, or manually trigger the timeout.After timeout, observe that the + button remains disabled. {#yokohama-patch-12__ol_r44_lhs_c3c} Expected behavior: The + button is enabled after a chat times out, allowing users to start a new conversation without refreshing the page. Actual behavior: The + button remains disabled after timeout, and users must refresh the page to initiate a new chat. |
| Virtual Agent Web Client PRB1974007 | Synthesized responses disappear on Now Assist Virtual Agent (NAVA), Now Assist panel, Dynamic Window (DW) | Responses disappear after they're produced. |   |
| Virtual Agent Web Client PRB1981024 | Markdown link \[label\](https://servicenow-prod.fluidtopics.net/url) renders an incorrect URL when the URL contains a dollar sign ($) |   |   |
| Walk-Up Experience PRB1965546 | In SOW, navigating to location kiosks doesn't return any results | This is an issue with the Walk-up Experience. | 1. Provision a Yokohama instance with the latest version of the Walk-up plugin installed with demo data. 2. Add two kiosks for walk-up location 'Santa Clara Tech Lounge'. 3. Impersonate a user who is part of the group 'Santa Clara Tech Lounge'. 4. Access either SOW or Platform. {#yokohama-patch-12__ol_y44_lhs_c3c} Expected behavior: Two kiosks are returned. Actual behavior: No results are returned. |
| Web UX Runtime PRB1968992 | There's a blank page in the custom workspace when users log in for the first time, or after they clear the cache | This issue occurs after upgrading Yokohama. The user notices that the Verify Guided Upgrade take a while to load when it's the first time logging in to the instance. | 1. Navigate to Admin MenuUpgrade Management. 2. Select Get started from the Overview page. {#yokohama-patch-12__ol_cp4_lhs_c3c} Notice that the Verify Guided Upgrade takes a long time to load when it's the user's first time logging into the instance. |
| Word Document APIs PRB1967960 | Custom fonts in Word documents throw an error |   | 1. Identify contract documents with custom fonts embedded into XML. 2. Upload the contract into the contract request. {#yokohama-patch-12__ol_qmx_gbg_d3c} Note that the upload fails and the file isn't visible in the contract request. |
| Zing Text Indexing and Search Engine PRB1972145 | The query is slow from the TS Index Stats job from the getTableList method | The TS Index Stats job executes some code to get a list of extension tables to index for a given base table. To do this, it executes an expensive aggregate query against the base table, grouping by the sys_class_name field. This doesn't scale well and can cause queries to run long, which impacts overall database and instance performance. | 1. Navigate to a large CMDB or SYS_IMPORT_SET_ROW table. 2. Run the TS Index Stats job. {#yokohama-patch-12__ol_fp4_lhs_c3c} Expected behavior: The job runs quickly. Actual behavior: The job runs slowly as these extended tables grow in size. |
[ ]

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

## Fixes included {#yokohama-patch-12__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 11](https://servicenow-prod.fluidtopics.net/o~Ty6nl6ETxZAE_DIVoJJw "The Yokohama Patch 11 release contains important problem fixes.")
* [Yokohama Patch 10 Hotfix 1a](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2711334)
* [Yokohama Patch 10 Hotfix 1](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2695212)
* [Yokohama Patch 10](https://servicenow-prod.fluidtopics.net/SDBJsFWBor16OZ4hsKA_gg "The Yokohama Patch 10 release contains important problem fixes.")
* [Yokohama Patch 9](https://servicenow-prod.fluidtopics.net/4JW8R28rn3fgnNmdc68clw "The Yokohama Patch 9 release contains important problem fixes.")
* [Yokohama Patch 8](https://servicenow-prod.fluidtopics.net/d6f5kXcWfwp1HgaFexLdIA "The Yokohama Patch 8 release contains important problem fixes.")
* [Yokohama Patch 7 Hotfix 3b](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2693894)
* [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](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-12__ul_ymn_wvr_qhc}

*[\>]: and then