Australia Patch 2 Hotfix 1

  • Release version: Australia
  • Updated June 17, 2026
  • 6 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 Australia Patch 2 Hotfix 1

    The Australia Patch 2 Hotfix 1 release, built on May 24, 2026, addresses multiple critical issues across different ServiceNow platform components. This update is essential for customers using Australia releases to fix known bugs impacting instance performance, authentication, data integrity, and user experience. The hotfix is applicable to various modules including Access Analyzer, Authentication, Change Management, Instance Scan, Live Archive, and more.

    Show full answer Show less

    Key Fixes and Improvements

    • Access Analyzer: Resolved instance scan jobs hanging due to inefficient checks, which previously caused job accumulation and performance degradation.
    • Authentication: Fixed login screen performance issues on iOS 26.2 and Zurich instances, improving responsiveness and login success in the Now Mobile and Agent apps.
    • Change Management: Corrected licensing control enforcement and plugin rollback issues within Australia instances to prevent improper license restrictions and enable plugin management.
    • Database Persistence: Addressed text search failures in non-English languages when specific database properties are set, ensuring accurate search results irrespective of language.
    • Instance Scan: Fixed scanning jobs stuck in sleep loops due to asynchronous database write issues, preventing indefinite scan hangs without error notifications.
    • Live Archive: Resolved silent data loss occurring during attachment migration caused by cascade deletes on related child tables, safeguarding attachment metadata and compliance history.
    • Platform Analytics Dashboard API: Prevented overwriting of translation records which caused loss of non-English tab names in dashboards.
    • Platform Analytics Migration API: Enabled configuration to redirect Core UI Performance Analytics widget navigation to the Analytics Hub instead of KPI details, improving user navigation consistency.
    • Related Lists: Fixed strict ACL checks preventing users with necessary roles from adding records in related lists, improving usability for catalogadmin, delegateddeveloper, and ITIL roles.
    • Upgrade Center: Addressed version mismatch issues between Appnode and Database that caused instances to fail to start after upgrades when certain properties are enabled.
    • Virtual Agent: Mitigated memory pressure caused by high cache usage in nodes with limited memory, reducing events process job failures due to memory exhaustion.

    Practical Implications for ServiceNow Customers

    By applying this hotfix, customers can expect improved stability and performance in critical platform areas, especially related to security scanning, user authentication, plugin management, multilingual support, and attachment management. The fixes prevent silent data loss and enhance user interaction with dashboards and related lists. Additionally, this update supports smoother upgrade processes and reduces memory-related issues on smaller nodes.

    Customers should review the specific problem records (PRBs) and knowledge articles referenced for detailed reproduction steps and impact, and plan upgrades accordingly to maintain compliance, functionality, and optimal instance performance.

    The Australia Patch 2 Hotfix 1 release contains fixes to these problems.

    Build information:
    Build date: 05-24-2026_0242
    Build tag: glide-australia-02-11-2026__patch2-hotfix1-05-05-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

    Access Analyzer

    PRB1993028

    KB2820230

    Instance scan jobs can hang and are not terminated due to checks not being optimized

    Instance scan jobs triggered by the Access Auditor Suite, which is a part of the Access Analyzer (sn_access_analyzer) store application, may hang or fail to terminate. This may cause multiple jobs to accumulate over several days, consuming multiple workers and preventing  other jobs from running. This may cause performance issues on the instance. This issue affects Access Analyzer (sn_access_analyzer) versions 6.0.0 through 6.0.5, as well as version 6.1.0.

    Refer to the listed KB article for details.

    Authentication

    PRB1969882

    KB2718536

    Login screen performance issues on iOS 26.2 RC and in Zurich instances After upgrading to iOS 26.2, users are unable to log in to any instance using the Now Mobile app. The login page is extremely slow or unresponsive, and it can fail to load or accept credentials. The issue affects multiple users and device models. It's reproducible across different instances, and it also impacts the Agent app.
    1. On iOS, navigate to the Now Mobile App.
    2. Connect to a Zurich or later family release instance.

    Observe that the screen loads slowly and is non-responsive.

    Change Management

    PRB2021436

    Instances should not get license restriction ACLs

    This issue was observed in Australia. Licensing controls are enforced when there are entries in subscription_entitlement.

    Log in to any Australia non-prod instance.

    Notice that the licensing controls are enforced when there are entries in subscription_entitlement, even if the instance is open.

    Change Management

    PRB2021441

    KB3032668

    Unable to rollback the plugin 'com.snc.itsm.foundation.license_control'

    1. Log in to an Australia instance with com.snc.itsm.foundation .license_control installed.
    2. Install any other family plugin after that.

    Notice that the plugin 'com.snc.itsm.foundation.license_control' is no longer able to rollback.

    Database Persistence - Data Access

    PRB2007256

    KB2925734

    The text search doesn't return results in non-English languages

    After downloading language plugins and switching the system language to a non-English language, results aren't returned when the property 'glide.db_query.replace_distinct_with_groupby' is set to 'false.' When the language is set to English, results are returned.

    Refer to the listed KB article for details.

    Instance Scan

    PRB1992382

    KB2901125

    Instance scan jobs get stuck in a sleep loop for days, which causes the subsequent scans to fail Instance Scan findings are written to the database asynchronously and are tracked using a global counter. If any write fails, the counter doesn't decrement properly; it goes up but never comes back down. This causes all future scans to hang indefinitely, waiting for a counter that will never reach zero. There's no timeout or logging to flag this, so scans can get stuck silently.

    Refer to the listed KB article for details.

    Live Archive

    PRB2022367

    In AttachmentMigrationService, copy-then-delete causes silent data loss through cascade delete on sys_attachment_attribute, dp_attachment_protection_history, and sys_attachment_migration_status

    AttachmentMigrationService migrates attachments between the storage backends 'ROWSTORE' and 'COLUMNSTORE' by creating a new sys_attachment row with a new sys_id, and then deleting the old one. Deleting the old sys_attachment triggers reference_cascade_rule='delete' on every child table that references it, which silently destroys records that reference the old sys_id, even though a valid replacement exists. The cascade engine has no knowledge of the new sys_id, so the new sys_attachment ends up with no associated child rows. The following child tables suffer silent data loss on every migrated attachment: sys_attachment_attribute (per-attachment metadata), sys_attachment_migration_status (migration tracking history), and dp_attachment_protection_history (data-privacy / compliance audit trail).

    1. Open an instance with the columnar attachments plugin, 'com.glide.data_management .columnar_attachments,' enabled.
    2. Create a sys_attachment row for any storage type, such as 'ROWSTORE', and note that the sys_id equals 'X'.
    3. Insert child rows referencing 'X' with the following:
      • sys_attachment_attribute: row with the sys_attachment = X sys_attachment_migration_status: row with the attachment = X
      • dp_attachment_protection_history: row with the attachment = X
    4. Trigger the migration via AttachmentMigrationService.migrateAttachments([X], AttachmentStorageType.ROWSTORE, AttachmentStorageType.COLUMNSTORE).
    5. Query each of the three child tables for the original sys_id 'X' after the call returns.

    Expected behavior: All three child tables still contain rows for the migrated attachment, either against the same sys_id, or under copy-then-delete which is re-pointed to the new sys_id.

    Actual behavior: All three child tables contain zero rows for the original sys_id 'X'. The new sys_attachment record, the new sys_id 'Y', exists with the migrated chunk data, but contains no rows in any of these three child tables. The data is silently lost and no error is logged. This occurs in any instance running on a build that includes AttachmentMigrationService for track, datamanagement, and downstream.

    Platform Analytics Dashboard API

    PRB2025067

    The sys_translated record for par_dashboard_tab is overwritten

    This can cause translations to be lost.
    1. In English, create a sys_translated record as follows:
      • Label: あいう
      • Table: par_dashboard_tab
      • Element: name
      • Language: ja
      • Value: TabName
    2. Create a PAE Dashboard.
    3. Add a tab with the same name as the sys_translated value (TabName).
    4. Save the dashboard.
    5. Create another dashboard.
    6. Add a tab with the same name as the sys_translated value again.
    7. Save the dashboard.
    8. Switch the language to Japanese.
    9. Return to one of the dashboards.
    10. Rename the tab あいう to さしす.
    11. Check the other dashboard tab.

    Observe that the translation is lost because the sys_translated record is overwritten.

    Platform Analytics Migration API

    PRB2022823

    Allow users to configure the re-direction of Core UI Performance Analytics widgets to the Analytics Hub instead of to 'KPI details'

    Users that activated Next Experience after migrating or upgrading to Australia will be redirected to 'KPI details' when selecting a Performance Analytics widget, even if they keep using Core UI dashboards. This issue occurs because the unified_analytics property forces the re-direction to 'KPI details'.

    Related Lists

    PRB2025356

    User can't add records in a related list because of the strict ACL check and missing ACLs for required roles Users with missing ACLs are not able to add new records in the related list due to a strict ACL check.
    1. Log in as a user with the catalog_admin, delegated_developer, and ITIL roles.
    2. Navigate to the 'Catalog Task' record page.
    3. Navigate to the Approvers related list.
    4. Select the Edit button.
    5. Add a few members as approvers.
    6. Select Save.

    Notice that no approver is added in the related list. Required field level ACLs are missing for these roles and there's no way to bypass the strict ACL check.

    Upgrade Center

    PRB2023239

    KB3015307

    There is a mismatch in the glide version between the Appnode and the Database following the upgrade A new code path introduced the MariaDBI18NSQLFormatter class. When the sys_properties record of the 'com.glide.db.session _language_collation_feature' property is set to true, it takes a code path upon upgrade or restart where an instance will not come up. When 'com.glide.db.session _language_collation_feature' is false, the code path exits early and doesn't cause this issue.

    Refer to the listed KB article for details.

    Virtual Agent

    PRB2007255

    There's memory pressure on nodes due to high memory for the cache 'com.glide.cs.qlue.module.coma.MessageBatchingSession' Users with 2GB nodes may encounter memory issues that can cause the events process jobs to yield.

    Run a heap dump.

    Observe that MacMessageBatchingSession or MessageBatchingSession uses over 50 MB of memory.

    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.