Yokohama Patch 12 Hotfix 1

  • Release version: Yokohama
  • Updated February 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Yokohama Patch 12 Hotfix 1

    The Yokohama Patch 12 Hotfix 1, released on February 12, 2026, addresses critical issues to enhance system performance and application management. This release is applicable to ServiceNow's Regulated Market environments.

    Show full answer Show less

    Key Features

    • Fix for Database Persistence: Resolves synchronization issues during migration to RaptorDB which may cause delays in archive table synchronization.
    • Application Manager Improvement: Addresses the problem where new application versions do not appear in 'My Company Applications' after publishing an update.
    • Word Document APIs Issue Resolved: Fixes a syncing error that occurs when paragraph properties are missing in documents generated by AI tools.

    Key Outcomes

    Customers can expect improved performance in data management and application visibility following the upgrade. It is recommended to upgrade to this hotfix from any prior Yokohama versions to ensure all relevant fixes are included.

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

    Build information:
    Build date: 02-09-2026_2259
    Build tag: glide-yokohama-12-18-2024__patch12-hotfix1-02-06-2026
    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

    Database Persistence - Data Management

    PRB1939498

    		 Migration to RaptorDB brings column length changes, which could impede archive table synchronization The synchronization should run quickly, but this scenario can occur and slow down the process.
    1. Provision an instance on MariaDB.
    2. Create some archive rules.
    3. Archive some data.
    4. Migrate the instance to RaptorDB.
    5. Install a plugin that will cause many table schema updates that propagate to archive tables, such as 'Discovery and Service Mapping Patterns.'

      Observe what happens during archive table synchronization.

    Expected behavior: The synchronization shouldn't be vulnerable to caches that take a long time to build.

    Actual behavior: The synchronization could become vulnerable to caches that take a long time to build.

    Application Manager

    PRB1986694

    		 App Manager and 'My Company Applications' incorrectly shows available updates after update checker When publishing a new version of the app, it doesn't appear in 'My Company Application'.
    1. Log in as an admin user on an instance (TD1).
    2. Navigate to My Company Application.

      Notice that as soon as the user lands on this page, it will automatically start the sync.

    3. Wait for the sync to complete.
    4. Search for the application to install, such as 'Test MyCompany App1'.

      Notice that 'Test MyCompany App1' shows up with available versions.

    5. From another instance (TD2) publish a new version of 'Test MyCompany App1'.
    6. As an admin user on instance TD1, navigate to My Company Application.
    7. Wait for the sync to complete.
    8. Search for the application 'Test MyCompany App1'.

      Notice that the new version of the application is not showing under 'My Company Application'.

    Expected behavior: The new version of the app is visible.

    Actual behavior: The new version of the app is not showing up.

    Word Document APIs

    PRB1987850

    		 Issue with document sync when paragraph properties do not exist An error occurs when attempting to sync the document. This issue occurs when the document was generated using ChatGPT or other AI tools, or when content controls are positioned on blank text.
    1. Make changes to the content control fields with 'Track Changes' on.

      Observe that the selected paragraph should not have any styling.

    2. Attempt to replace the value.

    Notice that it will throw an error.

    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.