Yokohama Patch 4 Hotfix 1

  • Release version: Yokohama
  • Updated July 1, 2025
  • 2 minutes to read

    • The Yokohama Patch 4 Hotfix 1 release contains fixes to these problems.

    Build information:
    Build date: 06-28-2025_2229
    Build tag: glide-yokohama-12-18-2024__patch4-hotfix1-06-24-2025
    Important:
    For more information about how to upgrade an instance, see ServiceNow upgrades.

    For more information about the release cycle, see the ServiceNow Release Cycle.

    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.

    Fixed problem

    Problem Short description Description Steps to reproduce

    Process Mining

    PRB1903878

    KB2229304

    		 After upgrading from the Xanadu to Yokohama release, process mining filter sets and scheduled tasks are deleted During the upgrade from Xanadu to Yokohama, the process mining filter set conditions and scheduled tasks are being deleted. Due to a backend issue, the upgrade script execution unintentionally deletes saved filter sets and scheduled tasks of Process Mining Projects. This particularly affects configurations with 'transition filters' linked to scheduled tasks. Although no other user data was affected, this issue may disrupt functionality where the deleted filter sets or scheduled tasks were actively used.

    Refer to the listed KB article for details.

    Agent Chat

    PRB1900981

    KB2226265

    		 Inbox audio is delayed when the 'Workspace' tab is inactive or out of focus before receiving the first work item When the work item assigned, audio isn't heard. Audio is heard only after switching back to the workspace. The agent may not get notified at the time of assignment due to this issue, and the work item may expired by the time agent is back on the workspace tab.

    Refer to the listed KB article for details.

    Asynchronous Message Bus (AMB)

    PRB1910946

    		 The Record Watcher (RW) Asynchronous Message Bus (AMB) message censor doesn't work when AMB lazy load is disabled When glide.amb.message. lazy.load is set to 'false', having a record open in two browsers and updating it in one doesn't update it in the other browser.
    1. Set glide.amb.message.lazy.load to 'false'.
    2. Open a record in two different browsers.
    3. Update the record in one browser.
    4. Notice that the Record field in the other browser window isn't updated.

    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.