--- 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 6 Hotfix 1 # Yokohama Patch 6 Hotfix 1 {#ariaid-title1} Release version: Yokohama Updated August 8, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read The Yokohama Patch 6 Hotfix 1 release contains fixes to these problems. Build information: : Build date: 08-05-2025_2351 : Build tag: glide-yokohama-12-18-2024__patch6-hotfix1-08-01-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-6-hf-1__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). ## Fixed problem {#yokohama-patch-6-hf-1__section_vgx_4ts_fgc} {#yokohama-patch-6-hf-1__all-other-fixes__entry__4} | Problem | Short description | Description | Steps to reproduce | |-|-|-|-| | Activity Stream PRB1923345 | Activity Response Generation (ARG) updates for workspace are not included in Yokohama | ARG changes are missing in workspace. | 1. Set up Activity Response Generation. 2. Enable the configuration. {#yokohama-patch-6-hf-1__ol_ygg_s5s_fgc} | | Analytics Data API PRB1845187 [KB2238953](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2238953) | Drilling down on KPIs in a Performance Analytics dashboard produces the error 'No internet connection' | Drilling down on any value redirects the user to the KPI details page with a 'No Internet connection' error. | Refer to the listed KB article for details. | | Application Manager PRB1924202 [KB2397128](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2397128) | 'My Company Application' ($mycompany appsmgmt.do) page isn't found | The 'My Company Application' page isn't found after upgrading Yokohama. | Refer to the listed KB article for details. | | Cache PRB1922845 | File handlers are left open if a LazyInputStream is closed before being read by LargeContentDiskCache | If LazyInput#close is called before the internal StreamSupplier is opened by LazyInput Stream#stream, the InputStream remains open until finalizers are calling during garbage collection. File handles are leaked when using LargeContent DiskCache and only call getMetadata() or contentExists(). Because the supplier is never invoked and the stream is never opened, closing the LazyInputStream doesn't close the underlying FileInputStream. These leaked file handles are only released when the garbage collector runs finalizers. | 1. Start glide. 2. Run java Process Status (JPS). 3. Get the Process ID (PID) of the glide process. 4. Run LSOF. 5. Take note of the file descriptor entries. 6. Flush the cache. 7. Load the Service Operations Workspace home page. 8. Repeat step 3 through step 6. {#yokohama-patch-6-hf-1__ol_vjz_f5s_fgc} Expected behavior: File descriptor entries is close to the original number. Actual behavior: Notice the 10's or 100's of additional file descriptor entries, indicating that the file handlers are left open. | | UX Framework PRB1923311 | UX dependency tracing should use LargeContentDiskCache. getMetadata to avoid file touching | File descriptors should not increase when there is a cache hit. | 1. Access a workspace homepage (for example: CSM, SOW, or Case Record). 2. Re-load the page multiple times. 3. Monitor open file descriptors for LSOF. 4. Notice the file descriptor entries. {#yokohama-patch-6-hf-1__ol_gkp_m5s_fgc} Notice that the file descriptors increase even when there's a cache hit. | [ ] {#yokohama-patch-6-hf-1__all-other-fixes} ## Fixes included {#yokohama-patch-6-hf-1__section_wgx_4ts_fgc} 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 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-6-hf-1__ul_kh5_jvs_fgc}