--- sourceDocument: Australia Release Notes sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/release-notes Release : - australia ft:locale : - en-US ft:publication_title : - Australia Release Notes ft:clusterId : - rn bundleId : - rn --- # Australia Patch 5m # Australia Patch 5m {#ariaid-title1} Release version: Australia Updated September 3, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 328 minutes to read The Australia Patch 5m release contains important problem fixes via Australia Patch 5 and updates to compatible ServiceNow Store applications. Australia Patch 5m was released on September 3, 2026. : * Build date: 09-01-2026_1150 * Build tag: glide-australia-02-11-2026__patch5m-08-07-2026 ## Monthly "m" releases {#ap5m-release-notes__section_kc4_5gk_zjc} Monthly "m" releases are now available for your ServiceNow AI Platform® instances. These releases, which are identified by an "m" in the release name, contain everything from the base family patches, the latest version of all AI applications, and those apps' supporting non-AI application dependencies. Important: This ServiceNow® release is not available for 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 the Australia Patch 5m release, click [here](https://downloads.docs.servicenow.com/enus/australia/rn/patches/PRBs-A05m.00.xlsx). Australia Patch 5m includes 565 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 {#ap5m-release-notes__security-related-fixes} Australia Patch 5m 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 Australia Patch 5m, refer to [KB3150636](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3150636). ## Changes in Australia Patch 5 {#ap5m-release-notes__changes-in-patch} [Adoption Services release notes](https://servicenow-prod.fluidtopics.net/HtnyGPLuk77EzNodmToF2A#adoption-services-rn "The ServiceNow Adoption Services application is a suite of solutions, both products and features, that provide user support and critical information when a user needs it most. Adoption Services was enhanced and updated in the Australia release.") : : [Configure](https://www.servicenow.com/docs/access?context=configure&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US) : When sn_dyn_guidance_user role is assigned, it also includes the genai_admin role. Note: The genai_admin role does not grant administrative privileges. [Integration Hub release notes](https://servicenow-prod.fluidtopics.net/KFvGm_A7tRMHcInGiPcR1A#integration-hub-rn "The ServiceNow Integration Hub application extends the ServiceNow Workflow Studio automation capabilities by enabling you to integrate your instance data with data in external systems. Integration Hub was enhanced and updated in the Australia release.") : : [Integration Hub Usage Dashboard](https://www.servicenow.com/docs/access?context=integrationhub-usage-dashboard&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) : The Integration Hub Usage Dashboard provides reports of usage by protocol. For more information about the service accounts contributing to each protocol, see [Monitor inbound API integration usage](https://www.servicenow.com/docs/access?context=inbound-api-integration-usage-dashboard&version=australia&pubname=australia-api-reference&ft:locale=en-US). [Kafka SSL credentials fields](https://www.servicenow.com/docs/access?context=hla-data-input-kafka-credentials&version=australia&pubname=australia-it-operations-management&ft:locale=en-US) : Updates to OAUTHBEARER, Token endpoint URL, Client ID, Client Secret, Scope, and OAUTH extensions. [Monitor inbound API integration usage](https://www.servicenow.com/docs/access?context=inbound-api-integration-usage-dashboard&version=australia&pubname=australia-api-reference&ft:locale=en-US) : Monitor inbound integration usage requests, data egress, and domain-level usage through the Inbound API Integration Usage dashboard. [Predictive Intelligence release notes](https://servicenow-prod.fluidtopics.net/BNPtGcB0rGEh~9eFl0AzkA#predictive-intelligence-rn "The ServiceNow Predictive Intelligence application enables you to create and train machine learning models to help improve the performance, efficiency, and flexibility of your systems. Predictive Intelligence was enhanced and updated in the Australia release.") : The sys property ML Trainer - Glide communication KAA (glide.platform_ml.kaa_auth_enabled) implements KAA validation when mTLS is enabled. : : [Properties for Identification and Reconciliation](https://www.servicenow.com/docs/access?context=properties-id-reconciliation&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) : glide.identification_engine.batch_update_last_discovered.use_execute_lazy Sets IRE mode for processing batch updates of the discovery timestamp fields first_discovered and last_discovered. For optimized performance, when IRE processes CI records, it updates discovery timestamp fields in batches. This property controls when these batch updates are executed. true : IRE defers database updates and uses batched operations, which improves performance. Usage: * For standard production operations * When performance is critical * When no race conditions are observed {#ap5m-release-notes__ul_u35_tkq_ljc} false : IRE processes updates synchronously without delay, ensuring immediate database consistency. Usage: * When race conditions between discovery and CI deletion exist * A deletion strategy is aggressively removing recently discovered CIs * If immediate timestamp consistency is required {#ap5m-release-notes__ul_sc2_pkq_ljc} General details: * Type: true \| false * Default: true * Learn more: * Location: [Add to System Properties \[sys_properties\]](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US) table. {#ap5m-release-notes__ul_gnh_phq_ljc} [Properties for Identification and Reconciliation](https://www.servicenow.com/docs/access?context=properties-id-reconciliation&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) : glide.identification_engine.batch_update_last_discovered.use_execute_lazy Sets IRE mode for processing batch updates of the discovery timestamp fields first_discovered and last_discovered. For optimized performance, when IRE processes CI records, it updates discovery timestamp fields in batches. This property controls when these batch updates are executed. true : IRE defers database updates and uses batched operations, which improves performance. Usage: * For standard production operations * When performance is critical * When no race conditions are observed {#ap5m-release-notes__d4132e1691} false : IRE processes updates synchronously without delay, ensuring immediate database consistency. Usage: * When race conditions between discovery and CI deletion exist * A deletion strategy is aggressively removing recently discovered CIs * If immediate timestamp consistency is required {#ap5m-release-notes__d4132e1713} General details: * Type: true \| false * Default: true * Learn more: * Location: [Add to System Properties \[sys_properties\]](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US) table. {#ap5m-release-notes__d4132e1730} ServiceNow AI Platform core feature release notes : : [ServiceNow Vault roles](https://www.servicenow.com/docs/access?context=vault-roles&version=australia&pubname=australia-platform-security&ft:locale=en-US) : Learn and set up the roles necessary to use ServiceNow Vault. [Using Dynamic Guidance](https://www.servicenow.com/docs/access?context=using-dynamic-guidance&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US) : Starting with Dynamic Guidance version 28.4.3, the genai_admin role is automatically included when the sn_dyn_guidance_user role is assigned. The genai_admin role does not grant administrative privileges. [View Inbound API Integration Usage dashboard](https://www.servicenow.com/docs/access?context=view-inbound-api-integration-usage-dashboard&version=australia&pubname=australia-api-reference&ft:locale=en-US) : View integration request counts, data egress volume, and domain-level usage. ## Notable fixes {#ap5m-release-notes__section-notable-fixes} The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes. {#ap5m-release-notes__notable-fixes__entry__4} | Problem | Short description | Description | Steps to reproduce | |-|-|-|-| | Database Persistence - WDF PRB2024733 [KB3137449](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137449) | Reports containing reference-type catalog item variables (lookup) fail to render data after upgrading to the Australia release | After upgrading to the Australia release, reports that contain reference-type catalog item variable columns fail to render data correctly. The affected reference-type variables don't resolve their lookup values, and their presence in the report additionally causes all other columns --- including native table fields such as Number, Created, and Closed --- to render as empty across all rows. | Refer to the listed KB article for details. | | Key Management Framework (KMF) for Platform Encryption PRB2058369 [KB3140571](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140571) | MID Server is unable to fetch credentials after upgrading to Zurich or Australia | In certain versions, there's a Unified Secrets Gateway (USG) service for credential management. During the upgrade to those versions, a system trigger script is designed to automatically execute and populate the sys_​secret_​identity _​group_​member table with the MID Server identity group mappings required for USG authentication. However, this trigger fails to complete successfully, leaving the table incompletely populated. As a result, the MID Server can't authenticate with USG and fails to retrieve credentials. | Refer to the listed KB article for details. | | Multi-Instance Framework PRB2040054 [KB3119447](https://hi.service-now.com/kb_view.do?sysparm_article=KB3119447) | There's a flood of 'Unable to find vtable operation for operation id {}' messages that's generating millions of records in an instance for every Flow Designer execution | In a cloned instance, the root cause of the flood of errors messages 'Unable to find vtable operation for operation id {}' in the syslog is sn_mif_vtable_ operation_context.vtable _operation is empty. | Refer to the listed KB article for details. | | Now User Experience PRB2038702 [KB3134148](https://hi.service-now.com/kb_view.do?sysparm_article=KB3134148) | A scoped public UI page isn't accessible without a login unless 'Name' is used vs a scoped endpoint in a sys_public record | It should be accessible without a login, so a user can complete the authentication from Outlook. | Refer to the listed KB article for details. | | System Events PRB1969068 | The 'Events process 0' job yields to memory pressure, causing event processing delays | When node memory pressure is high (live set ≥ \~91%), the JobYieldCheck mechanism triggers a yield on events process 0 despite it being a priority 25 (high priority) job. High-priority jobs should not be subject to automatic yield throttling, as this directly delays critical event processing and can result in P1 incidents. The memory pressure itself may be transient or difficult to diagnose quickly --- heap dumps often show no obvious culprit, and identifying the root cause of elevated memory usage takes time. During that window, events process 0 is repeatedly yielded, stalling event processing pipelines that users depend on for time-sensitive operations. JobYieldCheck WARNING Job=events process 0 yields due to memory pressure logged on affected nodes. Node memory is sustained at 91--93% of max, with live set at \~91.44% (\~1.28GB). glide.memory.watcher logs no active transaction warnings alongside persistent memory pressure status = true. There's only a single job visible in the queue during the yield window, yet throttling still triggers. However, users expect priority 25 jobs (events process 0) should not be yielded under memory pressure conditions. Yield throttling should be restricted to lower-priority workloads. | | | Table Rotation PRB1959672 [KB3071677](https://hi.service-now.com/kb_view.do?sysparm_article=KB3071677) | Shard tables aren't created on an initial plugin install | When a plugin is manually installed, shard tables aren't created automatically. | Refer to the listed KB article for details. | | UX Framework PRB2027095 [KB3102030](https://hi.service-now.com/kb_view.do?sysparm_article=KB3102030) | The latest component asset isn't selected when multiple asset associations exist in sys_​ux_​lib_​ component_​ m2m_​asset,​ which impacts AI summary cards on UI Builder workspaces | When the AI summary card component was upgraded, its asset name changed from now-ai-summary-card/index to uxc-generative-ai/index. The upgrade doesn't clean up the old asset association, so the sys_ux_lib_component_m2m_asset table ends up with two associations for the same component (old and new asset). The component-to-asset selection query in Glide​Ux​Component​ Def​Provider.​ get​Asset​Names ​By​Component​Sys​Ids()​ had no ordering and relied on default DB ordering. When duplicate associations exist, this could return the stale now-ai- summary-card/index asset, which is incompatible with the latest Platform AI Agents and Skills app. As a result the AI summary card fails to load on UI Builder workspaces. Classic UI uses a different rendering path, so it is unaffected. | Refer to the listed KB article for details. | [ ] {#ap5m-release-notes__notable-fixes} ## All other fixes {#ap5m-release-notes__other-fixes} {#ap5m-release-notes__AllOtherFixes__entry__4} | Problem | Short description | Description | Steps to reproduce | |-|-|-|-| | Activity Stream PRB2027954 | An activity filter's field's slushbucket initially has every field selected when the glide.​ui.​{table}​_​activity.​fields property doesn't exist | For non-task tables with an empty 'glide.​ui.​\​_​activity.​fields' property, 'Filter​Field​Repo.​get​Table​Property​Filters(' returned a hardcoded 'DEFAULT_FIELDS' constant. This default set was designed for task tables and didn't reflect the actual fields on the table, causing incorrect or missing fields in the activity stream. | 1. Verify that the record is a non-task table record. 2. Verify that the glide.ui.{table}_activity.field isn't set. 3. On an instance, in UI16, create a interaction record. 4. Select the Filter Activity button, all of the fields should be selected. 5. Select the Configure fields to bring up that the slushbucket now aligns with the fields in the 'Filter Activity'. {#ap5m-release-notes__ol_xqs_czy_ckc} | | Activity Stream PRB2040417 | The Copy button on the VTB view can't access copyJournalContent or GlideUIDefault | The content doesn't get copied to the clipboard API and doesn't show the 'Copied to clipboard' notification. | 1. On any instance, navigate to AllVisual Task Boards. 2. Create a freeform board. 3. Add a card on the newly-created board. 4. Open the card and add a work note or comment. 5. Select the Copy journal content button. {#ap5m-release-notes__ol_qqs_czy_ckc} Expected behavior: The content is copied to the clipboard API and shows a 'Copied to clipboard' toast. Actual behavior: The content doesn't get copied to the clipboard API and doesn't show the 'Copied to clipboard' notification. | | Agent Chat PRB2021594 | An agent chat box isn't enabled when work is offer re-routed post blind queue transfer | In most recent Australia release, ServiceNow CSM Workspace agent isn't able to type messages in the chat input box after they are re-routed an interaction that was rejected by a previous agent. The chat box should be enabled after re-routing acceptance. | | | Agent Chat PRB2031080 | Setting 'Disable agent inactivity check for API' to true makes the presence states disappear from the presence state picker in workspace's inbox | The presence state picker should display all available states, even when 'Disable agent inactivity check for API' is set to true. | 1. Log in to an instance. 2. Navigate to the awa_presence_state table. 3. Select Update Personalized List using the gear icon. 4. Add the 'Disable agent inactivity check for API' column to the list view. 5. Set the value of 'Disable agent inactivity check for API' to true for the 'Available' presence state. 6. Navigate to Service Operations Workspace (SOW). 7. Select the inbox icon. The 'Available' option isn't displayed. 8. Set the value of 'Disable agent inactivity check for API' back to false for the 'Available' presence state. {#ap5m-release-notes__ol_pqs_czy_ckc} See that the 'Available' option is displayed in the SOW presence state picker. | | Agent Chat PRB2033499 | Improve the presence state picker in workspace's inbox based on the new flag 'show_in_workspace' instead of 'Disable agent inactivity check for API' | | | | Agent Chat PRB2051353 | Agent presence indicator should be shown in the 'Transfer to Agent' list for third party | When searchTargetList is set, a list of agents is shown, but there's no presence indicator. | 1. Create and offer a third party messaging interaction to a CSM Agent. 2. Select the Transfer to Agent quick action. {#ap5m-release-notes__ol_dss_czy_ckc} Expected behavior: It shows a list of agents along with presence indicator when searchTargetList is set. Actual behavior: It shows a list of agents with no presence indicator when searchTargetList is set. | | Agent Chat PRB2052028 | Integration users can't read sys_cs_conversation_member for creating wrap up segment | The wrap up segment creation fails with a 400 status and the error message: 'Failed to create wrap-up segment. Segment not found in implementations for extension point: interactionSegment'. | 1. Create a third party messaging interaction. 2. Offer to a CSM Agent. 3. Call REST API to create a wrap up segment for that interaction and agent. {#ap5m-release-notes__ol_xss_czy_ckc} Expected behavior: The wrap up segment is created and the API returns success. Actual behavior: The wrap up segment creation fails with a 400 status and the error message: 'Failed to create wrap-up segment. Segment not found in implementations for extension point: interactionSegment'. | | Agent Chat PRB2055561 | Rename Now Assist, Moveworks and AI experience to ServiceNow Otto | The Sparkle button for CRR should be replaced with the new Otto button. CRR button's tooltip 'Write with Now Assist' should be replaced with 'Write with AI'. Finally, the Sparkle icon and its label in the recommendation modal should be replaced with the Otto icon. | | | Agent Chat PRB2055562 | Rename of Now Assist, Moveworks and AI experience to ServiceNow Otto | | | | Agent Chat PRB2058031 | Add a missing flag on 'Requires ACL authorization' | A fix has ensured that the 'Requires ACL authorization' flag on 'Conversation Server' graphQL schema is set to true. However, due to a discrepancy in syncing branches, only the ACL changes added are live and not the graphQL schema changes. | | | Agent Chat PRB2063949 | Some messages are hidden on the agent's side when hideControl is true and contains searchText | | | | Agile Development PRB2026219 | The Group capacity field is read only in sprint records | | 1. Navigate to an instance. 2. Navigate to the table 'rm_sprint.list'. 3. Open any sprint record. {#ap5m-release-notes__ol_wps_czy_ckc} Note that Group capacity (points) is read-only. | | AI Agents (Glide Family) PRB2034699 | GenAIMetadata M2MDaoImpl createAIAGenAI MetadataM2M doesn't assert that the genAILogId parameter is not NULL | This causes a full table scan of the sys_gen_ai_ log_metadata table. This code is invoked by the AsyncMessageProcessor. | | | AI Agents (Glide Family) PRB2037758 | AI Agents randomly throw a tool execution error: 'Failed to execute async FDIH tool' | At any random tool call, the AI Agent throws: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. In logs, it shows 'FDIH async tool call exception'. | 1. Log in to an instance. 2. Invoke the Quote AI agent. 3. Input a multi-paragraph, conversational prompt. {#ap5m-release-notes__ol_ess_czy_ckc} Observe that, at any random tool call, it throws: 'Sorry, there was a problem on my side trying to complete this request. Try asking again later'. In logs, it shows 'FDIH async tool call exception'. | | AI Agents (Glide Family) PRB2051367 | TTL isn't honored in sys_​og_​conversational _​cache_​configuration in the absence of any other invalidation rule | The persona section doesn't show the new memories immediately, but they're visible after 24 hours. | 1. Set up LTM extraction on Glide (enable sys_prop use_new_ltm). 2. Set up DARE with memory enabled (in pipeline.yaml, set enable_user_persona). 3. Create a conversation with some details that are a candidate for LTM extraction (for example, 'I like cycling'). 4. Verify that memories are extracted (the ltm job runs every hour). 5. After new memories have been extracted, check the persona section. {#ap5m-release-notes__ol_g5s_czy_ckc} Observe that it doesn't show the new memories. However, they will be visible after 24 hours. | | AI Agents (Glide Family) PRB2059351 | Record scope should override the user session scope | For AI Agents, when any record of a user instance is used, the record scope should override the user session scope of the MSP as per the domain separation policy. However, that's not happening. For example, when an AI Agent with a retriever tool is triggered by any record in a user instance (like C1), it fetches KBs/results from all the user instances under that MSP. | | | AI Agents (Glide Family) PRB2059390 | Role masking isn't unset when running a workflow | | | | AI Experience Framework - Glide PRB2034740 | aiux_service/ chat_check_access should work with the default experience name to query the deployment document ID | There should be a way to query by experience name so that there is no need to force pass a sys_id each time. | | | AI Experience Framework - Glide PRB2036766 | Experience cache population only emits the default theme | Multi-theme (user-criteria) themes are missing from the edge cache, so targeted users get the wrong theme. | | | AI Experience Framework - Glide PRB2061584 | True-up the AI UX Builder Store app | | | | AI Gateway - Security PRB2052119 | As part of the name change, update error strings in MCPOAuthConstants.java that reference 'Now Assist' to 'ServiceNow Otto' | The changes will be made in Zurich and Australia. Also, an additional change is needed for the description in glide/glide-ai-security-scan. | | | AI Search (Glide) PRB1859571 | A search retrieval agent returns an incorrect catalog item URL | | | | AI Search (Glide) PRB2052168 | No_answer Genius Result is streamed intermittently | A Genius Result rarely shows, but it should not show at all. | 1. Navigate to /sp. 2. Search for something that gives a no_answer result, like 'baseball world series'. {#ap5m-release-notes__ol_irs_czy_ckc} Observe that a Genius Result rarely shows. It should not show at all. | | AI Search (Glide) PRB2054276 | The fix script shouldn't backfill non-default sources | When the user upgrades to an instance with additional sources in the multi-content feature, the additional sources are marked as 'Included'. | Upgrade an instance without additional sources in the multi-content feature to a version with the feature. Observe that the additional sources are marked as 'Included'. | | AI Search (Glide) PRB2054932 | In Moveworks API V2, support linking ServiceNow Security Center (SSC) to a search profile | This is a product update. | | | AI Search (Glide) PRB2054938 | For the Moveworks API V2, return chunks when passing an additional flag | This is a product update. | | | AI Search (Glide) PRB2058047 | Indexing with multiple semantic indexing configurations with the same name on different models isn't working | When multiple semantic index configurations are created on the same datasource with the same semantic field name but different embedding models, only the first configuration is loaded into the active semantic index field cache. Subsequent configurations are silently ignored, so ingestion and search only use one embedding model for that field. Only one embedding model is used for indexing and search when multiple semantic index configurations share the same semantic field name. Additional configurations with the same semantic field name are not visible in get​Semantic​Index​Field​Mapping()​.​ No error or warning is logged when the duplicate-name configurations are skipped. Thus, multi-embedding model support for a single semantic field is broken. Configurations are silently lost during cache population. This affects ingestion, search, and any callers that rely on get​Semantic​Index​Field​Mapping()​.​ | 1. Create two active ais_semantic_ index_configuration records on the same datasource with the same semantic_field_name but different embedding_models values. 2. Add valid component fields via ais_semantic_ component_field for each record and set a valid semantic_ snippetization_configuration. 3. Flush the datasource object cache (AisConfiguration CacheManager. flushDatasource ObjectCache()). 4. Call AisConfiguration. get().getSemantic IndexFieldMapping('kb_knowledge','kb_knowledge'). {#ap5m-release-notes__ol_wss_czy_ckc} Observe that only one SemanticFieldConfiguration is returned for semantic_search and the other is silently dropped. | | AI Search PRB1875924 [KB3137872](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137872) | AI search ingestion sticks when the 'Size in Bytes' column has an empty value in sys_attachment for an attachment that has a size more than 25MB | | Refer to the listed KB article for details. | | AI Search PRB1902419 | The conversation ID isn't logged to the sys_search_event table | | 1. On an AI Search-enabled instance, start a new chat with Virtual Agent (VA). 2. Enter 'what is spam'. 3. Flush queued signals. 4. Open the sys_search_event table, and if necessary, add the Conversation ID field to the list/form. {#ap5m-release-notes__ol_nrs_czy_ckc} Expected behavior: Since it was from VA, there should be a conversation. Actual behavior: The conversation ID is empty. | | AI Search UX PRB2004411 | Refactor the synthesized Genius Result presence filter from Data Broker into the Java layer | Currently, the logic to conditionally execute the synthesized Genius Result --- specifically, the filter that checks whether a Genius Result is present before execution --- lives in the Data Broker transform layer (UX layer). This means the filter isn't automatically applied across all clients and must be manually maintained per-client in the Data Broker. This logic must be moved into the Java layer so that it is applied universally and automatically for all users, reducing duplication and the risk of inconsistent behavior across different consumers of the Search API. | 1. Review the Data Broker transform at sys_ux_data_ broker_transform_ 0c735fb4530422104 accddeeff7b12dd.xml#L44. 2. Observe that the conditional filter that gates execution of the synthesized Genius Result on its presence. 3. Note that this filter only applies to clients using this specific Data Broker transform; it isn't enforced at the Java/API layer. {#ap5m-release-notes__ol_fts_czy_ckc} A user that bypasses or doesn't use this Data Broker transform doesn't have the filter applied, resulting in potentially inconsistent or unintended behavior around synthesized Genius Result execution. | | AI Search UX PRB2014714 | Ignore Genius Result's limit for citations in sync mode | | 1. On an AI Search enabled instance with synthesized response configured for portal, navigate to a portal and complete a query that yields a synthesized response. 2. Set the system property 'glide.ais.query. disable_async_mode' to true. 3. Do same search in portal. The user should still get a synthesized response. 4. Open the search application (presumably NAVA) and set the Genius Result limit to 1. 5. Do the same search in portal. {#ap5m-release-notes__ol_uss_czy_ckc} Expected behavior: Users still get a synthesized response. Actual behavior: No Genius Result renders because of no citations. | | AI Search UX PRB2038703 | Instance creation failure for com.​glide.​search.​ graphql.​query.​ Suggestions from service portal's typeahead AIS Suggestions API | When something is searched for in the portal's typeahead, no suggestions appear and AIS Suggestions API calls in the network tab return 'Instance creation failure for: com.​glide.​search.​ graphql.​query.​ Suggestions',​ and 'DataFetchException'. | | | AI Search UX PRB2054213 | URLs with special characters like $ break streaming for non-Virtual Agent clients | Streaming starts successfully, but it stops partway through and the full answer is never rendered. | 1. Open an AIS-enabled instance. 2. Make sure 'Synthesized Response' is enabled in portal. 3. Navigate to the portal with Now Assist enabled. 4. Search for 'How can I reset my password?'. {#ap5m-release-notes__ol_l5s_czy_ckc} Expected behavior: The full answer streams successfully. Actual behavior: Streaming starts successfully, but it stops partway through and the full answer is never rendered. | | AI Search UX PRB2054952 | Rename Now Assist to Otto within AI Search components | This is a product update. | | | AI Search UX PRB2056856 | Replace the sparkle icon animation with the Otto animation for synthesized Genius Results (GR) | | 1. Open an instance with multi-content GR configured. 2. Navigate to portal/global search. 3. Search for a query that returns a synthesized GR. 4. Check the loader in the GR component when the loading state is showing. {#ap5m-release-notes__ol_its_czy_ckc} Expected behavior: The loader state shows the Otto animation. Actual behavior: The loader state shows the sparkle icon animation. | | AI Search UX PRB2057349 | Rename Now Assist to Otto for typeahead suggestions | This is a product update. | | | AI Search UX PRB2073716 | For non-admin users, search results and suggestion navigation on portals are redirecting to platform view | After upgrading to Australia Patch 5 or Zurich Patch 12, non‑admin users performing a search on a portal (for example, /esc) experience incorrect navigation. Selecting a regular search result or a suggested search result opens the record in the platform view rather than within the portal. | Scenario 1: 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12. 2. Log in as a non‑admin user. 3. Perform a search on a portal, such as /esc or /sp. 4. Select the regular search result that is returned. {#ap5m-release-notes__ol_qf5_lxj_jkc} Observe that the record opens in platform view instead of the portal. Scenario 2: 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12. 2. Log in as a non‑admin user. 3. Enter a search term on a portal, such as /esc or /sp, without submitting the search. 4. Select a suggested search result in the typeahead drop-down list. {#ap5m-release-notes__ol_jhd_nxj_jkc} Observe that the record opens in platform view instead of the portal. | | Alumni Center PRB2054850 | Add a null check when using getRefRecord() | | | | Analytics Data API PRB1973007 | The Platform Analytics 'pivot table' unit type doesn't persist | When creating a pivot table using two tables as the data sources, the 2nd and 3rd columns swap their values. | 1. Create a pivot table visualization within a dashboard. 2. Add in two tables as data sources. 3. Create four columns on the pivot table, with the first two column being a count of each respective table and the last two columns a sum of all the values with other columns. 4. Save the visualization. 5. Exit editing mode. 6. Refresh the dashboard. {#ap5m-release-notes__ol_zps_czy_ckc} When the order of the columns is the count of table 1, count of table 2, sum of table 1's column, sum of table 2's column, and when users refresh the dashboard, the 2nd and 3rd columns values swap, with the values from column 3 appearing in column 2 and vice versa. | | Analytics Data API PRB2039649 | The Platform Analytics dashboard ignores the data source filter | The 'Is one of' operator doesn't function as expected on the source. The issue is reproducible in Australia with the Data Visualization plugin version 29.1.0 and in Zurich with version 28.5.0. However, the functionality works as expected in Yokohama with version 28.0.29 and in Zurich with version 28.4.5. | 1. Open an instance. 2. Create an indicator scorecard visualization. 3. Select Number of Incidents as the data source. 4. Apply a source condition using the 'Is one of' operator. 5. Select the required priority values. {#ap5m-release-notes__ol_qrs_czy_ckc} Expected behavior: Only the selected priority is reflected. Actual behavior: All priorities are reflected in the indicator scorecard visualization. | | Analytics Data API PRB2050449 | Next Experience Widgets load with an 'Unable to generate chart' error | The error reads: 'Error Unable to generate chart. Cannot invoke 'com.glide. glideobject. GlideDateTime.after (com.​glide.​ glideobject. ​Glide​Date​Time)​' because 'scoresModifiedAt' is null.'. | | | Analytics Data API PRB2053974 | Bubble chart bubbles render horizontally in Platform Analytics Workspace (PAW) instead of distributed across both X and Y axes | After upgrading to Australia, bubble charts in PAW now render bubbles horizontally (all on Y = -1) instead of being distributed diagonally across both X and Y axes as expected. The same configuration in the Classic Reporting module (sys_report.LIST) correctly displays bubbles distributed across both axes. The bubbles are rendering and not stacking, but the axis distribution logic differs between PAW and Classic Reporting. In Classic Reporting, bubbles are positioned diagonally across both X and Y axes. Each rating value (Dissatisfied, N/A, Satisfied, Very Satisfied) appears at a distinct (X, Y) coordinate pair. In PAW, all bubbles are rendered on the same horizontal line (Y = -1), with X-axis variation only. There's no Y-axis differentiation. | 1. Navigate to Platform AnalyticsLibraryData Visualizations. 2. Select Create data visualization. 3. Choose Bubble as the data visualization type. 4. Add the asmt_metric_result table as the data source. 5. Add a custom condition: Metric is 'How likely is it that you would recommend this service to others?'. 6. Select Run and then add this source. 7. In the 'Dimensions' section, set the Group by to 'Metric definition' and apply. 8. Select Run. {#ap5m-release-notes__ol_iss_czy_ckc} Expected behavior: Bubbles should be distributed across both X and Y axes, matching the Classic Reporting output. Each unique combination of Row (Actual Value) and Column (Actual Value) should result in a distinct (X, Y) coordinate pair on the visualization. Actual behavior: All bubbles are aligned horizontally at Y = -1, with X-axis values varying. The chart is unreadable and does not match the intended visualization. | | Analytics Export API PRB2021342 | The email layout in an Platform Analytics scheduled export doesn't match the received email format | Platform Analytics scheduled reports aren't honoring the email body configured when the field omit_if_no_records is true. | | | Application Install Engine PRB2056922 | Install engine reads the dependencies from package.json with a fall back to the previous way when not available | This is a product update. | | | Application Manager PRB2022268 | The application manager sys_app_version displays duplicate records for the same application and version, which is causing the app to be 'Installation blocked' | As part of the AI testing, it's been observed that the app installations are blocked. The sys_app_version displays duplicate records for the same application, which is causing the app installations to be blocked, despite the app versions being available as well as the license checks having successfully completed. | 1. Navigate to an instance. 2. Navigate to App Manager. 3. Open any app (for example, sn_ai_itsm_cont) which is licensed and validated on CI (usageanalytics) prod, but has yet showed 'Not Licensed'. 4. Select Install. 5. It just fails with 'Installation blocked' on that app itself. 6. Open sys_app_version table. 7. Check the app/scope id. {#ap5m-release-notes__ol_sps_czy_ckc} Expected behavior: It should have only one record for that app and a specific app version. Actual behavior: It has multiple records for the same app and app version. | | Application Manager PRB2057729 [KB3140027](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140027) | Users can't publish custom-scoped applications after upgrading to Zurich or Australia | | Refer to the listed KB article for details. | | Asset Management Common PRB2024372 | Related lists aren't rendered in Hardware Asset Workspace despite existing in an configuration | Certain related lists such as 'Hardware', 'Software licenses', 'Bundles', and 'Other' assets aren't displayed in Hardware Asset Workspace even though they are present in the Workspace configuration. Analysis confirmed that the related lists exist in the latest configuration (physical_asset_workspace view) and are conditionally loaded. The issue results in only a subset of related lists being visible in Hardware Asset Workspace while others remain hidden. | | | Asset Management PRB2025075 [KB3052414](https://hi.service-now.com/kb_view.do?sysparm_article=KB3052414) | A catalog task isn't created in Hardware Asset's refresh flow | There's similar issues with the other flows as well, like transfer order, transfer order line, and contract approval. | Refer to the listed KB article for details. | | Asynchronous Message Bus (AMB) PRB2040279 | Add bearer token authentication support to Asynchronous Message Bus (AMB) client library | This is a product update. | | | Authentication Factors PRB2037251 | Update interactions post-identification and authentication | The 'Interactions' table has only 'Guest' resolved. It should have the user reference resolved post-identification and authentication. | | | Authentication Factors PRB2066684 | Match KB identification phone numbers are ignoring special characters | Questions with the category 'phone number' aren't matched against formatted stored phone numbers during voice agent identification flow. | | | Automated Test Framework (ATF) PRB2012913 | Tests fail with an error: 'Timed out waiting for intent feedback \' | When Automated Test Framework (ATF) sends an intent to the UXF framework, the intent is received by UXF but is silently terminated/consumed without any feedback being returned to the caller. There's no success response, failure response, error message, or 'action not available' status sent back. Because of this, ATF can't determine whether the request failed due to unsupported actions, missing configuration, processing errors, or temporary issues. This prevents ATF from performing retries, fallback handling, or proper error recovery. | | | Automated Test Framework (ATF) PRB2017949 | There's stuck execution trackers due to Automated Test Framework (ATF)'s new feature metadata tracing | For invalid metadata table names in sys_traced_metadata records, the generateMissingPayloadHashes throws an error and causes the final payload hash calculation execution trackers to be stuck. | 1. Ensure that metadata tracing is on. 2. Run a test on a table with a long name (such as 'sys_og_conversational _cache_configuration', more than 40 characters). {#ap5m-release-notes__ol_sqs_czy_ckc} Observe that the sys_traced_metadata records truncate the long table name (sys_traced_metadata records save table names up to 40 characters whereas metadata table names can be up to 80 characters in length). Observe at the end of the test, there's stuck sys_execution_trackers while generating payload hashes for the sys_traced_metadata records because the truncated metadata table name is invalid. It thus throws an error. | | Business Calendar Filter Options PRB1977276 | Filter values included with the 'Fiscal Calendar' (com.snc.fiscal_calendar) plugin aren't translated | Filter values included with the 'Fiscal Calendar' (com.snc.fiscal_calendar) plugin aren't translated when users change their language preferences. If a user switches to French (Canada), the filter value 'Next 3 fiscal months' should be translated as 'es 3 prochains mois fiscaux'. However, if a user switches to French (Canada), the filter value 'Next 3 fiscal months' is actually translated as '3 Fiscal Months suivant'. There are multiple other filter values included with the plugin that are affected. | 1. Provision an instance with a language other than English and the 'Fiscal Calendar' (com.snc.fiscal_calendar) plugin installed. 2. In English, open any list that can use 'Fiscal Calendar' list filters for a date range. 3. Set the language to anything other than English. 4. Refresh the page. {#ap5m-release-notes__ol_crs_czy_ckc} Notice that the filter value still displays some of the text in English. | | Canonicalization Data Services (CDS) PRB2053470 | Data uploaded to cds_server_staging table is blocked within instances | This issue occurs in instances where the property 'glide.cmdb.canonical.URL' is set to https:​/​/​\​.​service-​now.​com/​ and ends with '/'. Unfortunately, that is the base instance value, and it affects the upload portion of CDS. | | | Case and Knowledge Management for HR Service Delivery PRB2023216 | Ship the required RCAs per the analysis result | Also, analyze those RCAs for which the analysis result said not to ship. Trigger automation and verify the result if there are any failures. | | | Case and Knowledge Management for HR Service Delivery PRB2023219 | Ship the required RCAs as per the analysis result | | | | Case and Knowledge Management for HR Service Delivery PRB2025681 | Due to 'getRefRecord', a RCA is generated in the Oracle HCM job execution that should be marked as 'Allowed' | Due to the use of 'getRefRecord' in the script include, a RCA record is generated with the source scope as: 'HR Service Delivery integration with Oracle HCM'. the target scope as 'Human Resources: Core', the target as: 'Table: HR Profile', and the operation as 'Read' after running the Oracle HCM job. This RCA should be marked as 'Allowed' and pushed to the repo. | 1. Provision an instance with Oracle HCM related plugins installed. 2. Navigate to the Oracle HCM Cloud Integration Source record. 3. Ensure that on the Integration Service record, Workers is active. 4. Select the Run Job button. {#ap5m-release-notes__ol_pss_czy_ckc} After some time, the RCA record is generated when 'Job Transform Map' starts running. This RCA is created by the source 'Script Include: OracleHCMJob TransformHelperSNC' where 'getRefRecord' is used. | | Case and Knowledge Management for HR Service Delivery PRB2028299 [KB3061412](https://hi.service-now.com/kb_view.do?sysparm_article=KB3061412) | In Platform Analytics, an ACL isn't letting an admin user modify or create data visualizations in dashboards or data visualizations | When editing any visualization in a dashboard with the sn_hr_er_case table as a data source, the visualization can't access its data source. As a result, metrics are turned off and can't be edited, preventing updates or modifications to the visualization. There is error: 'You don't have access to the data source used in this visualization'. | Refer to the listed KB article for details. | | Case and Knowledge Management for HR Service Delivery PRB2055197 | In Alumni Center, update RCAs in HR Core for the getRefRecord() for Australia | | | | Change Management PRB2035555 | The 'All' filter on the 'Create Change' page doesn't display all standard change templates when a template has no category or catalog | When the 'All' filter is selected for standard change templates on the 'Create Change' page, not all templates are displayed. This is because one template has no category. The null category errors the 'can category be read by user' check. | | | Change Management PRB2035924 [KB3093597](https://hi.service-now.com/kb_view.do?sysparm_article=KB3093597) | Standard changes created from a problem aren't linked to the parent task | The issue is reproducible if users untick the 'Two step' checkbox under ChangeAdministrationStandard Change Properties and then perform cache.doClear Cache. A standard change created from a task (incident/problem) aren't linked to a parent task. If users Check Conflicts before saving a child change from a project requested item, it won't attach the change to the parent item. | | | Change Management PRB2052987 | NewChangeRedirectProcessor only checks the system-wide glide.ui.polaris.experience property and ignores per-user glide.ui.polaris.use preference when deciding Next Experience redirect for Create Change | The file app-itsm/glide-service-mgt/ src/main/plugins/ com.snc.change_request/ update/sys_processor_ 0af16f2d53631010 34d1ddeeff7b12b6.xml (NewChangeRedirectProcessor, path new_change_redirect), line 76: var polarisEnabled = 'gs.​get​Property('glide.​ui.​polaris.​experience',​ false) === 'true';' --- only reads instance-wide sys_property, ignores per-user preference glide.ui.polaris.use (sys_user_preference table), the documented mechanism for per-user Next Experience toggle. The user opted out at a user level, but still was redirected into Next Experience's create-change flow when the system property is on. polarisEnabled check should account for both glide.ui.polaris.experience (system) and glide.ui.polaris.use (user preference) --- not the system property alone. | 1. Turn on the system property glide.ui.polaris.experience = true and com.snc.change_ request.next_ create_page = true. 2. Set the sys_user_ preference glide.ui.polaris.use = false for a specific test user (system unchecked, User = test user). 3. Log in as that user. 4. Trigger Create New Change (module or UI action) so the request hits the new_change_redirect processor. 5. Observe the redirect. {#ap5m-release-notes__ol_iqs_czy_ckc} Expected behavior: The redirect respects the user-level opt-out and goes to sn_chg_model _ui_landing.do (UI16). Actual behavior: The redirect goes to now/​change-​management/​create-​change/​ (Next Experience), ignoring the user preference. | | Change Management PRB2053039 | In the 'Change risk assessment' answer generator skill flow, replace the Now Assist terminology with Otto rebranding | The suggestion message should contain 'Check answers generated by AI for accuracy'. | 1. Navigate to SOWChange Request. 2. Select Assess Risk in the 'Overview' tab. 3. Select Generate Answers. 4. Wait until risk assessment completes answer generation. 5. Open risk assessment. {#ap5m-release-notes__ol_vss_czy_ckc} Observe that the suggestion message doesn't contain 'Check answers generated by AI for accuracy'. | | CMDB Identification and Reconciliation PRB2021886 | Null dbquery results must be preserved as null instead of wrapped | | Run a payload for a non-existing table that has a sys_id in the payload. Where encryption wrappers are constructed, dbq.execute() would normally return null when querying this non-existent table. Now, code is wrapping the null. | | Column Level Encryption PRB2005360 | On an encrypted HTML field, getElement(fieldName) returns a GlideElement with a value of 'null' instead of an empty string (''), causing the condition ge == null to evaluate as true | The field value conversion logic checks for encryption before validating whether the value exists. When encryption is enabled on an empty field, the system attempts to process a null value through the encryption path, which returns the literal string 'null' instead of handling it as an empty value. | | | Condition Builder PRB2054935 | Create a sys property to determine the Glide version for condition builder | This is a product update. | | | Configuration Management Database (CMDB) PRB1994587 | A race condition between IRE LazyWriter and Deletion Strategy causes the configuration item (CI) state to flip incorrectly | A CI's state is flipping from installed to stale during Discovery (delete strategy execution). A race condition occurred between IRE's asynchronous batch update of the last_discovered field using 'db.executeLazy()' and the execution of the Deletion Strategy. The LazyWriter delay caused the Deletion Strategy to process stale 'last_discovered' values, marking valid CIs as retired despite their presence in the payload. | | | Configuration Management Database (CMDB) PRB2017559 | The health configuration cache is ineffective due to a shared cache eviction | The getHealthConfiguration() method in HealthConfigManager.java is not getting effective cache hits. The current implementation caches per (metricSysId + className + domainId) key, creating a few hundred cache entries. Since this is a shared cache, entries get evicted before they can be reused, resulting in repeated DB queries for records that never change during processing. | 1. Create health configuration rules and observe the cache entry through cache_inspect.do. 2. Create a pressure on the system to cause cache eviction. {#ap5m-release-notes__ol_xts_czy_ckc} Observe in the code path that the cache is rebuilt every time there is an eviction. The caching path is controlled via sys_property and only applies to the non-domain path. | | Configuration Management Database (CMDB) PRB2020295 | INSERT_NOT_ALLOWED_FOR_SOURCE incorrectly classified as a partial error causes the cmdb_ire_partial_payloads table to bloat and an out of memory (OOM) error | When an IRE data source rule blocks inserts for a class and data source, affected records are incorrectly saved as partial payloads. Since the block is permanent, these partial payloads can never complete --- each retry creates a new entry, causing the cmdb_ire_partial_payloads table to grow unboundedly. If the partial payload contains a large number of related or lookup items, this can also lead to OOM on app nodes. | | | Configuration Management Database (CMDB) PRB2021367 | Implement totals calculation for the group view when applying a class filter qualifier configuration | | | | Configuration Management Database (CMDB) PRB2026628 | getRefRecord() scoping bypass due to directive changes | | | | Configuration Management Database (CMDB) PRB2030304 | OrphanProcessor skips CIs and reprocesses records after batch timeouts due to unordered HashMap iteration | When the CMDB Health orphan metric job times out MID-run on large datasets, it saves an incorrect resume position and silently skips CIs on the next run. As a result, orphan CIs appear healthy in the dashboard even though they are actual orphans, leading to inaccurate health scores. | 1. Set up a class with a large enough population of orphan CIs such that processing exceeds five minutes. 2. Trigger the CMDB Health orphan batch job. 3. Allow the job to run until the five minute batch timeout fires MID-loop. 4. Observe the checkpoint value stored in MetricProcessorStatus for that class --- it's an arbitrary sys_id, not the lexicographically highest one processed. 5. On the next scheduled run, observe that orphan CIs with sys_ids smaller than the stored checkpoint are not evaluated and not reported as failures. {#ap5m-release-notes__ol_cts_czy_ckc} | | Configuration Management Database (CMDB) PRB2037178 | A relationship editor (child) entry incorrectly displays a '\*' suggested marker when only the parent direction is configured in cmdb_rel_type_suggest | After upgrading from Yokohama to Australia, the CI relationship editor's 'Suggested relationship types' list displays both the parent and child directions of a configured suggested relationship with the '\*' suggested marker, even when only one direction was configured in the cmdb_rel_type_suggest table. For example, a cmdb_rel_type_suggest record is created with base_class = Windows Server, dependent_class = Business Service, and direction Connects to (parent). When the relationship editor is opened for a Windows Server CI, the list shows two entries instead of one: \* Connects to::Connected by (Parent) and \* Connects to::Connected by (Child). Both entries appear with the leading \*, suggesting both directions are configured. Only the (parent) direction was actually configured. Users selecting from the suggested list can't distinguish which direction was the configured one. Because the list is sorted alphabetically and the (Child) entry sorts before (Parent), the misleading default selection can result in CI relationships being created in the inverse direction of the customer's intent --- silently introducing incorrect CMDB data. The \* suggested marker should only appear on the direction that is actually configured in cmdb_rel_type_suggest. The (Child) entry for a parent-only suggested relationship should either not appear in the suggested-marker group, or appear without the \* prefix. | 1. Navigate to the 'Suggested Relationships' module. 2. Insert a record using an unused relationship. 3. Open the relationship editor from the relationships formatter on a Windows server CI. {#ap5m-release-notes__ol_bqs_czy_ckc} Expected behavior: Only the added suggested relationship from one direction is expected. Actual behavior: Observe two relationship choices for the relationship. | | Configuration Management Database (CMDB) PRB2052583 | References to 'Now Assist' for the duplicate CI remediator should be renamed to Otto | | | | Connections and Credentials PRB2034770 | A scoped app is unable to update the http_connection record | Scoped applications need to update http_connection records that they themselves created and own. Because the table-level ACL blocks all cross-scope writes, there's currently no supported path for a scoped app to modify its own connection records. The http_connection table is a platform (global) table whose cross-scope access policy grants only read access to all application scopes. In the earlier ServiceNow-managed scoped app flow, Claroty CTD via Service Graph Connector relied on the existing platform-owned Connection and Credential creation path to create http_connection and related credential records. The available scriptable sn_cc.ConnectionBuilder APIs cover create scenarios such as createConnectionAlias and createConnectionAndCredential, so the absence of a scoped update path didn't surface when the use case was limited to creation. | 1. Navigate to Service Graph Connector for Claroty CTD. 2. Create a connection with the provided connection_url. {#ap5m-release-notes__ol_zrs_czy_ckc} Expected behavior: It should be able to update the connection record for the child sys_alias's http_connection record. Actual behavior: Updating on http_connection isn't allowed from any scoped app due to tables's cross-scope access policy. | | Content Experiences PRB2036902 | A change in HRApprovalAccessUtilsSNC causes schedule content approvals to fail without a new RCA | | 1. Provision an instance with HR Core installed. 2. Create a schedule with approvers such that one rejection rejects the whole schedule. 3. Approve any number of the requests, saving at least one (0:X-1). 4. Reject one. {#ap5m-release-notes__ol_vrs_czy_ckc} Expected behavior: The schedule is rejected as normal. Actual behavior: An RCA error occurs. | | Content Experiences PRB2054955 | RCA for app-ex-ai-agents in Content Publishing for the getRefRecord directive | | | | Contract Management PRB2040201 [KB3140742](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140742) | Assets covered on a contract aren't added through an Multiple Record Associator (MRA) pop-up | In the 'add action' over MRA pop-up, there's a slight change by the platform. It is now performing a GlideRecordSecure insert instead of GlideRecord. It is validating for create and write ACLs on clm_m2m_contract_asset.asset and clm_​m2m_​contract_​asset.​contract fields. There's ACLs where it allows the respective operations only if they are blank. This is clearing out the Contract and Asset field values during creation. So, records which are created don't have these fields and aren't displaying in the related list. | | | Contracts Core PRB2036700 | Add the needed RCA as part of the getRefRecord() scoping bypass directive changes | | | | Conversational Appointment Booking PRB2054247 | True-up Conversation Appointment Booking for GetRefRecord directive changes | After making the required changes as part of the directive, all the three flows (schedule an appointment, reschedule an appointment and cancel an appointment) should work when the caller scope access is restricted. | | | Customer Operations for Customer Service Management PRB2035611 | Fix GetRefRecord scoping bypass | On CSManagementUtils, guard the getRefRecord() result before calling getLabel() to prevent an error when a reference field has no associated record. Also, on CSQueryBRUtil, add a null check on entityGR before calling isValid() to prevent an error during dot-walked field validation. | | | Customer Service Case Action Status PRB2011771 | Keep the 'Major Case' related list consistent in app-csm-action-status and app-major-issue-management | If users reinstall or upgrade app-csm-action-status again after Major Case is installed, the related list on Major Case is different. The newly added-in app-major-issue-management is gone. | | | Customer Service Management PRB2002976 [KB3141009](https://hi.service-now.com/kb_view.do?sysparm_article=KB3141009) | An advanced qualifier reference that uses 'current' isn't functioning as expected in CSM Workspace | Advanced reference qualifiers that rely on the 'current' object fail when templates are applied in Workspace. However, the same functionality works as expected in 'Classic UI (UI16)'. During template application in Workspace, the platform passes corrupted or incomplete serialized data to 'GlideRecordEncoder.decode()'. As a result, the current GlideRecord is returned without field values. | Refer to the listed KB article for details. | | Database Persistence - Data Access PRB2013282 | Columns are created with a 'u_' prefix | After Table​Schema​Manager .​alter()​.​execute()​ adds a column, TableDescriptor returns the new column but the column name is different from what was supplied. The new column was created with a 'u_' prefix in the column name. This behavior is different from table creation, where columns are created with exactly the same name supplied for column_name. | 1. Alter a table using the 'Table Management' API. 2. Add a column. {#ap5m-release-notes__ol_mss_czy_ckc} Expected behavior: Create a column exactly as specified. Actual behavior: It adds a 'u_' prefix to the column. | | Database Persistence - Data Dictionaries PRB2050936 | Let the 'Table Management' Java API create a table/column in a scope without a scope prefix | MetricBase must create tables in the DEX scope without applying the scope prefix, as it applies the mb_ prefix to metricbase table. The API should be changed and require a scope object by default. | Use the TableManagement Java API to create a table in any custom scope. Observe that a scope prefix is added to the table. | | Database Persistence - Data Scale PRB1942731 | If sequences exist to reduce redundant queries, SequenceAtomicCounter.get could cache | | | | Database Persistence - Graph PRB2026586 | toLower() and toUpper() functions aren't supported in WHERE and RETURN | After creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. Cypher's toLower() and toUpper() functions aren't supported anywhere in the builder --- neither in WHERE predicates nor in RETURN projections. | | | Database Persistence - Graph PRB2026589 | COUNT(DISTINCT x) can't be represented with GraphQueryBuilder API | After creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. Aggregate('COUNT', x) only ever emits COUNT(x). There's no way to express COUNT(DISTINCT x), which is the only correct answer when multiple paths can reach the same node. | | | Database Persistence - Graph PRB2026590 | ORDER BY isn't stored in Encoded QueryModel | After creating a query with GraphQueryBuilder, users of GraphQueryBuilder API should be able to get the encoded query representation as a transferrable serialization of the query. RETURN alias --- the AS clause is dropped when using buildEncodedQuery(), so any consumer of the encoded query has no way to know what column name the user asked for. ORDER BY / LIMIT / SKIP --- these have no representation in QueryModel at all, so they're dropped whole on round-trip. | | | Database Persistence - Graph PRB2040734 | Sys_class_name doesn't come as property from getForTables | | | | Database Persistence - Graph PRB2051205 | Inline node properties in the cypher are dropped in the encoded query when using with useCypher() | If there are inline properties in the cypher passed to useCypher, the returned encoded query doesn't contain that query. | | | Database Persistence - Graph PRB2052676 | Cache flushes are triggered, even when the cache is not used/populated | The number of cache flush messages for the table 'cmdb_rel_ci' is in the 80 million+ range every hour. In a way, it's making 80 million inserts into the sys_cache_flush table. 'cmdb_rel_ci' is paired with 'graph_cmdb_rel_type_cache'. The cache graph_cmdb_rel_type_cache isn't enabled, but the cache pairing is still in a static block and is active. | | | Database Persistence - Graph PRB2053774 | Support initializing GraphQueryBuilder with a cypher query string via the JavaScript API | This is a product update. | | | Database Persistence PRB2075293 [KB3150595](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3150595) | After the upgrade to Australia Patch 5, auto-increment columns are failing inserts with the duplicate_key error | Australia Patch 5 (AP5) introduced a change to how certain database auto-increment sequences are managed. Under specific conditions, this change can cause the sequence used to generate new record identifiers to become invalid or out of sync with the database. When this occurs, attempts to create new records may fail. As a result, transient state records may not be created as expected in tables with the auto-increment field. This impacts many functional areas relying on the sequence record to track orders of states, logs or messages. This defect fix is included in the weekly patch due to its severe impact on multiple major functionalities across the platform. | Refer to the listed KB article for details. | | Database Persistence - WDF PRB1931544 | Users should be warned/blocked from setting up a reference field that is ineligible | As of Australia, it currently enforces the reference key assignment only in the WDF Hub mapping page and not on sys_dictionary or sys_db_object. When creating/editing the remote table through the hub, there's a method called 'com.glide.datafabric. schemamapping. Remote​Table​Def#validate​Reference'.​ This method verifies that the reference table and the reference key are valid. If the reference table table doesn't exist/cannot be accessed, or if the reference key's data type is not in the list of allowed types, it blocks the table from being created/updated and throws an error message to the user in the UI. Following this approach, it can add the null value check in this method and throw the appropriate error message to the user. | | | Database Persistence - WDF PRB2038399 | There's a pagination issue | | 1. Open the 'List' view of a data interface. 2. Order by one column. 3. Navigate to the next page. 4. Check the data. The same page is displayed. {#ap5m-release-notes__ol_e5s_czy_ckc} See that the limit isn't applied to the query. | | Database Persistence - WDF PRB2040034 | In Australia, all database columns that start with a number have 'yy_' added to the start of the name, causing a syntax error | When querying a table in the Australia release and the DB column starts with a number, it adds a 'yy_' to the SQL query, breaking the collection of data and making a list view show nothing. Error: 'Syntax Error or Access Rule Violation detected by database (ERROR: column x_​snc_​potatofarm _​0_​farmers0.​yy _​1stname does not exist. Hint: Perhaps you meant to reference the column 'x_​snc_​potatofarm _​0_​farmers0.​1stname'.​ Position: 259)'. | 1. Create a scoped app. 2. Create a table. 3. Create some data on that table. 4. Add a column that name starts with a number. 5. Navigate back to the list view. {#ap5m-release-notes__ol_ers_czy_ckc} See that its blank, but the count displays that there's records. | | Database Persistence - WDF PRB2050923 | Provide unified server-side API's fetch primary key details for Data Fabric and standard ServiceNow tables | | | | Database Persistence - WDF PRB2052538 | Data interface tables are unable to fetch data with remote table as the implementation | Current remote table support requires that the vtable is provider backed. | 1. Open a remote table. 2. Create a data interface table with the fields matching with the remote table. 3. Navigate to 'Interface M2M'. 4. Configure the m2m mappings. 5. Navigate to the \_list.do. {#ap5m-release-notes__ol_nss_czy_ckc} Expected behavior: The table displays the data. Actual behavior: No data is displayed. | | Database Persistence - WDF PRB2080099 | LeadingDigitLegacyColumnIT fails on Australia | On an Australia patch, running against Oracle, any column rename involving a column whose logical name begins with a digit fails with: 'ORA-00957: duplicate column name'. This is because the generated statement collapses the source and target names into the same identifier. | | | Data Fabric Table Glide Services PRB2018015 | The Zero Copy Connector (ZCC) Hub UI becomes unresponsive/times out if a large number of schemas and tables are retrieved | When large amounts of schemas and tables (\~20k) are retrieved in an API call, the function 'refreshSchemasAndTables()' takes a long time to execute compared to the underlying persistence API 'GlideDataFabric EngineService. getInstance(). getAllTablesForCatalo'. This is on the magnitude of 2.25 seconds vs 40 seconds. | 1. Navigate to ZCC Hub on an instance. 2. Create a connection with large number of schemas and tables (\~20k schemas and tables). {#ap5m-release-notes__ol_d5s_czy_ckc} Expected behavior: The 'Data Assets' page loads schemas and table and is responsive. Actual behavior: The 'Data Assets' page times out during loading. | | Data Privacy (Classic) PRB2031050 | The 'Run Once Data Privacy' job takes days to complete after segment creation on large tables (300M+ records) | | 1. Provision an instance with the Data Privacy plugin installed on a large clone. 2. Set up a privacy configuration on a table with a large number of records (300M+). 3. Configure a 'Run Once' dp_job and trigger it. {#ap5m-release-notes__ol_uts_czy_ckc} Expected behavior: The job should complete within a few hours after segment creation (dp_work_item). Actual behavior: The job takes days to complete. | | Data Privacy (Classic) PRB2031271 | Rollback of a scheduled anonymization job doesn't refresh the activity stream UI for Journal fields (work_notes, comments) | When a scheduled Data Privacy anonymization job is rolled back, the Journal field values (work_notes and comments) are correctly restored in the sys_journal_field table. However, the activity stream UI continues to display the anonymized values because sys_activity table (used by Service Operations Workspace) and sys_​history_​set/​sys_​history_​line (used by UI16 List and Form views) aren't refreshed upon rollback. The Description field doesn't exhibit this issue. This is inconsistent behavior introduced when journal type anonymization support was added. | 1. Open an instance with Data Privacy enabled. 2. Configure a scheduled anonymization job targeting Journal fields (work_notes, comments) on the Incident table. 3. Run the anonymization job. 4. Confirm the fields are masked in both the database and the UI. 5. Execute a rollback of the anonymization job. 6. Verify in sys_journal_field that the original values have been restored. 7. Navigate to the affected Incident record in both UI16 and Service Operations Workspace. {#ap5m-release-notes__ol_lrs_czy_ckc} Observe that the activity stream still displays the anonymized values even though the database was reverted. | | Data Privacy (Classic) PRB2032551 [KB3140437](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140437) | LLM prompt creation takes \~800 ms, though it used to be 200-300 ms | The root cause was determined as the introduction of 'Sensitive Data Trail system processors', which had a large default timeout (20 seconds). The processors were scanning all 32 data patterns on an prompt of \~130K characters, taking an additional \~400 ms in latency. | Refer to the listed KB article for details. | | Data Privacy (Classic) PRB2039058 | Real time anonymization (RTA) for child tables separate from parent tables | This is a product update. | | | Data Privacy (Classic) PRB2039332 | Increase the maximum size limit of the incoming request to Data Privacy APIs from 1M to 10M | The Data Privacy API only supports up to 1M character long prompts. However, a simple prompt on Virtual Agent may result in prompts larger than 1M characters, which causes the prompt's response to get stuck. Prompts of extra large size should be processed by the Data Privacy API. | | | Data Privacy (Classic) PRB2040595 | Post-clone anonymization of child workers is incorrectly cancelled due to parent job type mismatch | The post-clone data privacy anonymization job uses a parent-child architecture; one parent job distributes work to multiple child worker jobs that process tables in parallel. The issue is in how the child workers look up their parent job record. In the post-clone flow, the parent job is stored in a different table type than the child workers' lookup code expects. Because the lookup fails with 'data protection job is not valid,' each child worker is cancelled immediately. | | | Data Product Backend Services PRB2027724 | Users are unable to edit reference type details on DTT when editing a data interface | There's no error, but it doesn't work. | | | Data Snapshots PRB1995292 | A data snapshot indicator timeseries API returns empty data instead of the expected single-span score when the request startTime and endTime are the same date | | 1. Configure a data snapshot indicator (pa_datasnapshot_indicator) with a boolean condition. 2. Send a POST request to /api/now/analytics/data with a timeseries data configuration where: 1. The startTime and endTime are set to the same date/time 2. A business calendar is used 3. The date falls within a valid span for that calendar period {#ap5m-release-notes__ol_xrs_czy_ckc} 3. Observe the API response data array. {#ap5m-release-notes__ol_wrs_czy_ckc} Expected behavior: The API returns the single-span score for the calendar period that covers the requested date. Actual behavior: The API returns an empty data array --- the single span covering the requested date is silently truncated/ignored. | | Date Picker PRB2029576 [KB3061444](https://hi.service-now.com/kb_view.do?sysparm_article=KB3061444) | There's a regression on GlideDateTime.setDisplayValue | Any script that calls setDisplayValue() with an ISO-format string (yyyy-MM-dd HH:mm:ss) on an instance where glide.sys.date_format is set to anything not in FORMAT_LIST (for example, dd-MM-yyyy, MM/dd/yyyy, etc.) produces incorrect dates in Zurich. | Refer to the listed KB article for details. | | Decision Graph for Context Engine (Family) PRB2056900 | Glide changes for machine learning integration needed for Distinguished Encoding Rules (DER) mining | This is a product update. | | | Decision Graph for Context Engine (Family) PRB2056902 | Instrument 'Ask For' approval action Instance Observer (IO) during flow execution for context graph tracing | This is a product update. | | | Decision Graph for Context Engine (Family) PRB2056905 | Rate-limited flow trace eligibility evaluation | This is a product update. | | | Decision Graph for Context Engine (Family) PRB2056908 | Scaffolding for the decision-graph module | This is a product update. | | | Decision Graph for Context Engine (Family) PRB2056910 | Cache decision weightage for a low-latency runtime lookup | This is a product update. | | | Decision Graph for Context Engine (Family) PRB2056912 | Adding or deleting a feature dictionary should make mined patterns inactive | This is a product update. | | | Declarative Actions PRB2055766 | The related list UI actions to update rows are failing on m2m if the field being updated is read-only | The UI action calls AssetAutomationAPI. completeAssetDisposalTask. This has current.update, which fails. If the read-only flag is removed from the Stage field in the sn_hamp_m2m_hw _asset_disposal table, then it works. | 1. Navigate to Hardware Asset WorkspaceInventoryDisposal order. 2. Create a disposal order. 3. Navigate to the related list. 4. Add an asset to the disposal order. 5. Open Verify task from the related list. 6. Select the row. 7. Select Verify. {#ap5m-release-notes__ol_a5s_czy_ckc} Observe that the action fails to update. | | Developer App Shell PRB2052364 | Fix GetRefRecord scoping bypass | | | | Developer Sandboxes PRB2054240 | The scheduler claim mutex (sys_mutex) isn't sandbox-aware and forces DSB nodes to contend for a cluster-wide lock, causing scheduled-job pickup delay | | 1. On a multi-node instance (50+ nodes), turn on Developer Sandboxes. 2. Create at least 20-30 sandboxes. 3. Multiple isolated sys_triggers should exist in the sandboxes. 4. Pull stats.do?include=otel.scheduler\* on the sandbox's node. Observe that claim_lock_time averages above one second (expected \~13ms), jobs_lateness averaging 300+ seconds, and worker capacity used is very low. 5. Compare against a controller node on the same instance. Claim_lock_time is still elevated but jobs_lateness stays within a few seconds, because base nodes don't pin an entire platform triggers on one node. {#ap5m-release-notes__ol_rqs_czy_ckc} | | DevOps Change Velocity PRB2052626 | GetRefRecord scoping bypass for the 6.2.1 release | | | | Discovery PRB2015204 | Update the IP address to retired when the network interface card's (NIC) is updated to 'Retired' | In the IP-Based Discovery plugin, the business rule (BR) 'Discovery - Set IP Address to Absent' only sets the IP address to absent. When the NIC is retired, it doesn't set the IP address to 'Retired', leaving orphaned or outdated IP addresses. The BR should handle the retired scenario as well. | | | Discovery PRB2023232 | Some Sybase processes running on Linux don't meet the classifier conditions to trigger the sybase pattern, resulting in an incomplete Discovery | The Sybase Process classifier has these conditions: Command contains 'dataserver', parameters contains 'sqlsrvr', and parameters matches regex '-\[Dd\]\\s+'. The regex breaks down as follows: -\[Dd\]\\s+ matches a literal hyphen, \[Dd\] matches either uppercase D or lowercase d, and \\s+ matches one or more whitespace characters (space, tab, etc.). It matches a hyphen, followed by D or d, followed by at least one space. If a process running returns a parameters string starting with \['parameters':​'-​d/​data/​master.​dat\]​ this doesn't meet the condition for this regex and the pattern doesn't trigger, despite the process being a valid Sybase process. | | | Discovery PRB2029641 | Update Store app true-up for ITOM Licensing Store app 3.13.0 | | | | Discovery PRB2059465 | Discovery patterns fail to launch for sub-accounts/datacenters when glide.​discovery.​ retire_​stale_​accounts is turned on | In Cloud Discovery, schedules configured to discover all sub-accounts under a master account, with enabling glide.​discovery.​retire_​stale_​accounts and glide.​discovery.​cdu.​ auto_​refresh_​sub_​accounts _​and_​ldcs , Discovery patterns fail to launch for sub-accounts/datacenters (only the service account discovery launches). | | | Document Management PRB2056202 | Replace 'Now Assist' and 'Sparkle' with 'ServiceNow Otto' in screenshots, images, and icon assets | All UI visual elements should be updated across SmartDocs, Doc to Voice, and SmartRedact to reflect the ServiceNow Otto branding changes. This includes both images/screenshots and icon assets. | | | Document Management Services PRB2039067 | Smart redaction with redaction codes and notes for documents | This is a product update. | | | Document Management Services PRB2056919 | SmartDocs enablement in UI16 and ServicePortals | This is a product update. | | | Document Viewer PRB2056915 | Support in document viewer for the doc to voice agent | This is a product update. | | | Dynamic Schema PRB2037531 | There's failing DynamicSchema aggregate ITs | In Australia, in the db-dynamic-schema-test package, the following ITs are failing: DynamicSchemaAggregatesIT and DynSchQueryAggregates\*IT. The expression added to the GROUP BY isn't listed in the SELECT clause. | | | Email Notifications PRB1948259 | SelectAll and Delete buttons aren't working in Email Viewer | | 1. Log in as an admin user. 2. Navigate to CSM Workspace and open a case record. 3. From mini composer, send an email with some documents attached. 4. Update the email status to 'sent' from send-ready in the sys_email.list table. 5. Open the email from the 'Emails' tab in the case record. The email opens in the Email Viewer view {#ap5m-release-notes__ol_mrs_czy_ckc} Expected behavior:SelectAll should select all the attachments. The Delete button should delete the selected attachments. Actual behavior:SelectAll isn't selecting all the attachments. The Delete button isn't functioning properly. | | Email Notifications PRB2001946 | The RemoveAll button shouldn't be present in the email viewer | | 1. Log in as an admin user. 2. Navigate to Customer Service Management workspace. 3. Open a case record. 4. From the mini composer, send a email with some documents attached. 5. Update the email status to 'sent' from send-ready in the sys_email.list table. 6. Open the email from the 'Emails' tab in the case record. 7. Select Select All. 8. Select the 3 dots and verify. {#ap5m-release-notes__ol_tts_czy_ckc} Expected behavior: The RemoveAll button shouldn't be present in the email viewer. Actual behavior: The RemoveAll button is visible in the email viewer. | | Email Notifications PRB2019162 | Introduce batch support for subscriptions in NotificationRecipientBuilder | Notification events are taking a longer time to process (5-7 seconds). | 1. Log in to an instance. 2. Create a subscribable notification record. 3. Create 1800+ subscriptions. 4. Trigger a notification. {#ap5m-release-notes__ol_cqs_czy_ckc} Expected behavior: The notification should be sent to all recipients without much delays. Actual behavior: The notification is generated but its processing consumed a significant amount of time. | | Email Notifications PRB2036855 | Agent workspace case emails display multiple 'To' names if the email recipient has multiple contact records | If a contact has more than one contact record in the system (same email address), the system displays the names of all the contacts when viewing an email sent to that person on a case. | 1. Navigate to customer_contact table. 2. Create multiple contact records with the same name and email address, but a different user ID. 3. Navigate to CSM workspace. 4. Create a case. 5. Add one of the contacts created as the case contact. 6. Send an email to that contact. 7. Open the sent email. {#ap5m-release-notes__ol_fqs_czy_ckc} Expected behavior: Only one contact is displayed in theTo field. Actual behavior: TheTo field lists all the contacts with the same name and email address. | | Email Notifications PRB2050616 | Email client APIs shouldn't be public | | | | Embedded Help PRB2056339 | Replace all occurrences of 'Now Assist' text with 'AI' across the Help Center and embedded help | | 1. Open Help Center or embedded help. 2. Open a document that was created using AI-generated help. {#ap5m-release-notes__ol_hts_czy_ckc} Observe that 'Now Assist' text is displayed for AI-generated help articles. | | Employee Profile PRB2011497 | There's a dot-walking RCA error when moving from the 'Learning' scope to the 'Employee profile' scope | An attempt to dot-walk to table sn_employee_profile present in the 'Employee profile' scope from the 'Learning' scope was blocked. The reference field employee belongs to the sn_lep_challenge table. The operation type was: GET_REF_RECORD. | | | Employee Profile PRB2021875 | getRefRecord() changes for Opportunity Marketplace (OPM) and TD Core in Employee Profile | | | | Event Management PRB2034593 | An event field mapping rule from the type 'Map field' using regex causes an error in event processing | When having an event field mapping rule from type 'Map field' using regex and a matching event is processed, if the Additional info field contains the source field JSON as the value, the event finishes in an error state. | 1. Create some event field mapping rule from the type 'Map field' using regex. 2. Create an event with Additional info containing nested JSON, where one of the keys matches the regex and its value is a JSON object. {#ap5m-release-notes__ol_yqs_czy_ckc} Expected behavior: Event processing should complete successfully without errors and an alert should created. Actual behavior: Event processing fails, and the event is moved to the error state. | | Event Management PRB2052731 | Remove the step in mixed grouping that allows alerts to join existing groups before the grouping definitions are run in order | The mixed grouping engine handles alerts in two steps. First, it checks whether an alert can join a group that already exists---without following the order the definitions are set up in. After, it goes through all the definitions in their proper order, where it's also allowed to create new groups. The first step disregards the configured definitions order; as a result, an alert can end up in a group created by a lower-priority rule instead of a higher-priority definition. The definition order exists specifically to control which definition gets to group an alert first, so skipping it defeats the purpose of the order. In conclusion, the two-step process should be removed. The mixed grouping engine should go through the definitions once, in order. For each definition, it should allow alerts to either join an existing group or create a new one. | 1. Create two grouping definitions, Definition A and Definition B, with Definition A placed ahead of Definition B in the rule order. 2. Send alerts A1 and A2 that fit Definition B. 3. Wait for the grouping job to run. 4. Create Group B. 5. Send alerts A3 and A4 that fit both Definition A and Definition B. 6. Wait for the grouping job to run. 7. Check which group A3 and A4 end up in. {#ap5m-release-notes__ol_gts_czy_ckc} Expected behavior: A3 and A4 form a new group created under Definition A, because Definition A comes first in the rule order. Actual behavior: A3 and A4 are added to the existing Group B. | | Event Management PRB2053524 | Azure monitor for 'Issue' integration, and UI enhancements in Express List and alert record | This is a product update. | | | Field Service Task Bundling PRB2064856 | Dynamic bundling creates unassigned bundles | | 1. Verify that Dynamic Scheduling, Task Bundling, and Task Grouping plugins are active. 2. Enable the sys_property 'com.snc.dynamic. scheduling.bundle_ before_scheduling'. 3. Set the Task Grouping rules (Same Location) and policy. 4. Create two work order tasks (WOT) in the draft. 5. Once the WOTs are moved to the 'Qualified (Pending Dispatch)' state, the tasks should be bundled using Dynamic Bundling and Dynamic Schedule the tasks automatically. {#ap5m-release-notes__ol_qss_czy_ckc} | | Flow Engine PRB1943894 | Looping over records using 'built in iterator' is significantly slower than the normal GlideRecord iteration | Flow engine should take a similar amount of time to iterate over records and script or Java when no quiescing occurs, but run times are 16.8x - 73.6x slower. | | | Flow Engine PRB2001686 | There's multiple queries to fetch a flow plan record | When the plan isn't cached, it takes two queries. When run again with the plan already cached, it takes only one query. | | | Flow Engine PRB2001694 | Reduce multiple sys_flow_context select queries | In GlideRecord, before updating, it queries to get the DB state of the record to populate the 'previous' object for business rules. This can be avoided if 'fPopulatePrevious FromMemory' is set to true. It can be set by calling Glide​Record:​:​ set​Populate​Previous​ From​Memory.​ | 1. Create any simple flow. 2. Execute it in background scripts. {#ap5m-release-notes__ol_ets_czy_ckc} Observe that there is 'select query' before every update. | | Flow Engine PRB2029887 | Flow engine is \~200x slower than the equivalent script on 1000 elements, as eager Val.displayValue dominates input wrapping for large collections | A flow that takes a large ComplexObjectCollection as input executes \~200x slower than the equivalent Rhino background script doing the same work. For a 1000-element ForEach input, per-invocation wall-clock is \~143 ms (vs \~0.7 ms for the equivalent script). The slowdown scales with the input collection size; small inputs are affected less, but flows that pass large lists as input are heavily impacted even on the user-default execution path (reporting off, trace off). There's no functional break as the flow produces correct output, but the per-invocation cost is dominated by work that the engine never reads on the default path. | | | Flow Engine PRB2034134 | 'Require' statements throw a JavaScript exception error in Australia's Flow Designer | | | | Flow Engine PRB2038121 | Restore the Flow Engine FlowObjectDef cache | This removes redundant sys_hub_action _type_definition read per quick-action execution. | | | Flow Engine PRB2054195 | The 'ForEach' iteration on GlideRecord does eager canRead checks on all the records | | 1. Create a subflow. 2. Add a lookuprecords action on the sys_user table with active = true and a max count of 10. 3. Add ForEach flow logic with the input as lookuprecords output. 4. Add a log inside ForEach. {#ap5m-release-notes__ol_pts_czy_ckc} In GRProxy, before starting the loop it internally loops over all the records in GlideRecord and collects sys_ids and skipped counts by doing a canRead check. | | Flow Engine PRB2054201 | Introduce a cache in FlowRecompileChecker | The eviction policy is too broad for execution settings in ProcessPlanCache. Any change to any execution setting evicts all plans but should only effect one. Instead, it should evict a process plan directly when its execution settings change. | | | Flow Engine PRB2062691 | Action Fabric flow complexity is insufficient for pricing estimation exercises | The complexity_bucket attribute contains values grouped into bucket_0_10, bucket_11_50, and likely no other buckets. | 1. Perform MCP requests on an instance with Action Fabric telemetry. 2. View the Action Fabric telemetry via Clickhouse or logged data. {#ap5m-release-notes__ol_ass_czy_ckc} Expected behavior: The exact complexity of the MCP flows are recorded. Actual behavior: The complexity_bucket attribute contains values grouped into bucket_0_10, bucket_11_50, and likely no other buckets. | | Flows (Family Channel) PRB2054449 | Refactor all occurrences of 'Now Assist' in Flow Designer, Action Designer, and Flow Diagram to 'ServiceNow Otto' | | | | Flows (Family Channel) PRB2056022 | Otto directive renaming for the call skill step plugin | The plugin name is being changed from 'Now Assist Skill' to 'AI Skill' (or 'AI Skill Step'). The step name is being changed from 'Call Now Skill Step' to 'Call AI Skill Step'. Also, the plugin and step description should be updated where applicable. | | | Global Ranking PRB2035527 | Users aren't able to delete a scrum task from cross-scope | | 1. Navigate to Collaborative Work Management (CWM) Workspace. 2. Open any board. 3. Turn on the 'Story \& Scrum' task. 4. Add story \& scrum tasks records to the board. 5. Try to delete the scrum task. Observe that the shadow task is deleted but the actual scrum task isn't deleted. 6. Refresh the board. Observe that the deleted scrum task reappears. {#ap5m-release-notes__ol_srs_czy_ckc} | | Hermes (Family) PRB2026691 | TCP connection establishment and SSL handshake occur every minute | TCP connection establishment and SSL handshake occur every minute even when the health check is skipped under the 150-second threshold. The unnecessary overhead should be remediated. | | | Hermes (Family) PRB2026695 | Identify and eliminate duplicate health checks where two Hermes services point to the same Hermes cluster | Normally, it'd be expected that Glide apps would use different bootstraps. Given the special condition, when the Kafka bootstraps are the same, it should avoid the duplicate connections/healthchecks between the 2 services. | | | Hiring Experiences PRB2031986 | The 'Last Month' option under 'My job requests' in the hiring portal displays data of requisitions created in the current month | For the 'Last Month' filter in the hiring portal, the UI displays the current month record because it's using \>= beginningOfLastMonth(), which pulls in June (this month) records too. The platform's native filter uses sys_created_onONLast month, which is properly bounded to just the previous month. | | | Hiring Experiences PRB2057166 | GetRefRecord scoping bypass fix | | | | Horizon Component Library PRB2052114 | Replace the 'Sparkle' icon with the Otto Lottie animation in AI and loader experiences | | | | Horizon Component Library PRB2052172 | Suppress console statements so browser tools aren't flooded | | View the 'Theme behavior' console output. The console output should only be logged when env = development. | | Horizon Empty State Component PRB2050333 | Update ai-general illustration | The sparkle illustration should use the new Otto logo instead. | 1. Open an instance. 2. Create a experience in UI Builder. 3. Add an empty state component to the stage. 4. In the config panel, locate the illustration property. 5. Select AI general from the drop-down list. {#ap5m-release-notes__ol_i5s_czy_ckc} Expected behavior: The empty state shows the Otto logo. Actual behavior: The empty state shows sparkles. | | Horizon Icon Component PRB2032851 | Add the Otto icon to the library | | 1. Navigate to an instance. 2. Create a experience in UI Builder. 3. Add a now-button-iconic component to the stage. 4. In the configuration panel, locate the drop-down list for the icon property . 5. Search for 'sn-sparkmoji-logo'. {#ap5m-release-notes__ol_css_czy_ckc} Expected behavior: See the new Otto logo. Actual behavior: The icon is missing. | | Horizon Icon Component PRB2050318 | Update all 'Sparkle' icons | Icons with the Otto logo should be shown instead. | 1. Open an instance. 2. Create an experience in UI Builder. 3. Add a now-button-iconic component to the stage 4. In the config panel, locate the icon property. 5. Search for an icon. {#ap5m-release-notes__ol_j5s_czy_ckc} Expected behavior: Icons with the Otto logo are shown. Actual behavior: Icons with sparkles are shown. | | HR e-signature PRB2035247 | RCA for Content Experience | Specifically, eesign for getRefRecord directive. | | | HR Service Delivery PRB2014389 | RCAs are generated for 'Populate Manager Reportee Count Using Eligible Users' and 'Employee​Hub​Org​ Chart​Reportee​Util​SNC' | During nightly test case execution, two RCAs are generated for the new scripts: - sys_script_include _a302f8807873 f250f877079523d275e1 and - sysauto_script_ 33a5e72453f7 b210f2ebff c230e5e69d. It is causing test failures. | | | HR Service Delivery PRB2021314 | The Cancel UI action in an HR case checks for 'mandatory' after the case is canceled | The Cancel UI action is invoking hr_CaseAjax.cancelAction(). In this function, state and work notes are updated from the server script. Inside the callback function, there's g_form.save(), which checks the mandatory and saves the form. If the data is already saved from the server script, the system shouldn't check the mandatory. | | | HR Service Delivery PRB2035482 | getRefRecord updates to Australia | | | | HR Service Delivery PRB2052205 | In Australia and Zurich, RCAs generated in HR Core and HR Employee Relations must be added back to track/HR | | | | HR Service Delivery PRB2052632 | The header_config_\* fields are missing from the sn_hr_core_service table in Zurich and Australia | header_config_\* fields missing from sn_hr_core_service table in Zurich and Australia. | Open a Zurich or Australia instance with the sn_hr_core and EC Core plugins installed. Observe that the header_config_\* fields are missing from the sn_hr_core_service table. | | Identification and Reconciliation API PRB2028002 | Fix three dynamic IRE UI messaging and wording issues and the system properties in the update folder | | | | Identification and Reconciliation API PRB2034883 | Users can add or edit identification rules for hardware's child classes while dynamic IRE is enabled | If dynamic IRE is enabled, users shouldn't be able to see or edit identification rules on the hardware hierarchy. | 1. Enable dynamic IRE. 2. Navigate to hardware or any of the child classes. {#ap5m-release-notes__ol_m5s_czy_ckc} Observe that static rules are displayed and editable, even though dynamic IRE is enabled. | | Identity PRB1964703 | A federated ID isn't generated for all the users in the instance | There's also instances where a federated ID isn't generated for some users even when they have a unique user_name and email. | | | Inbound API Integration Usage Framework PRB1988771 [KB3082116](https://hi.service-now.com/kb_view.do?sysparm_article=KB3082116) | IPAccessListFilter handling for malformed IP addresses | Inbound REST API calls coming through proxy servers (x-forwarded-for header with multiple IP's) or malformed IP address can sometimes fail in Zurich and Australia instances. | Refer to the listed KB article for details. | | Inbound API Integration Usage Framework PRB2034837 | Record data egress usage for integration requests | This is a product update. | | | Inbound API Integration Usage Framework PRB2034838 | Domain separation support for Inbound API Integration Framework | This is a product update. | | | Innovation Management PRB2055588 | GetRefRecord scoping bypass for app-ppm | | | | Innovation Management PRB2055611 | GetRefRecord scoping bypass for app-common | | | | Install Base Management Store PRB2059577 | Install base items and sold products should support RAC fallback mechanism | The functions _skipFetchEntities and getQRfallbackRoles should be overridden in CSMRelationshipServiceSNC in CSMRelationshipService _InstallBaseRelatedParty to allow this fallback mechanism. | | | Instance Clone (Family) PRB2032595 | Deactivate the 'Target Instance Validate' business rule (BR) on an instance table to support OAuth-based authentication of clone targets from the Clone Admin Console | | On any Australia instance, add a target instance through the Clone Admin Console. The instance is inserted into the table post-successful authentication, but there's an unnecessary BR that runs the authentication again to validate it. This BR was used in the legacy version of the clone and isn't required with the Store app. | | Instance Clone (Family) PRB2051479 | Clone cleanup script fixes | | | | Instance Clone (Family) PRB2051483 | In Clone Admin Console, declare v.2.2.4 to ensure that OAuth is used | | | | Instance Data Replication (IDR) PRB1940978 | There's many IDR-DCTComparisonJobs on an instance | This is likely only a cosmetic issue and not hurting performance. Instances have at least one IDRDCTComparisonJob per node, which seems excessive. For instances with many nodes, this ends up being the majority of IDR jobs. There's only a few consumer jobs per instance (not per node). | 1. On an instance running a version lower than Australia and configured with multiple nodes, open the sys_trigger table. 2. See if there's multiple IDRDCTComparisonJob records present. {#ap5m-release-notes__ol_f5s_czy_ckc} | | Integrated Email Client PRB2051938 | A Now Assist reference in Email Client must be changed to Otto | This is a product update. | | | Integration Hub PRB2056938 | Rename the 'Now Assist for Spoke Generation API Support' Glide plugin | | | | Integration Hub Spokes PRB2053392 | Users can recover box webhook HMAC signing keys via timing oracle on JavaScript == comparison and forge events to trigger arbitrary subflows | This is a product update. | | | Knowledge Center PRB2076447 | The Auto-fix plugin update blocks the Australia Patch 5m upgrade in loadsim release testing | The plugin upgrade thread handling becomes stuck in an error loop triggered by a null pointer. It never exits or advances, leaving the upgrade 'hung'. This happens when the upgrade plugin loader reaches the knowledge center update that adds in the auto-fix and auto-fix enable property. | | | JVM at Scale PRB2032235 [KB3078521](https://hi.service-now.com/kb_view.do?sysparm_article=KB3078521) | Memory watcher isn't logging active transactions in the Australia release | | Refer to the listed KB article for details. | | Knowledge Graph (Family) PRB2016914 | Update the structure to keep the Knowledge Graph configuration file in the same folder as the released description version and dynamic configuration for the Install Server URL | | | | Knowledge Graph (Family) PRB2052948 | Implement batch insert logic for affinity jobs to improve insert latency | This is a product update. | | | Knowledge Management PRB2022138 | getRefRecord() scoping bypass update | It must ship an RCA for HR tables for the knowledge scope sn_km_gen_ai. | | | Knowledge Management PRB2031464 | The Knowledge Base Article (KBA) is text not visible in the workspace | This issue occurs with custom templates that contain fields of mixed data types like HTML, string, date. | 1. Create such a template with mixed data types. 2. Create an article fill, and fill non-HTML field as well. 3. Insert a block in one of the fields. 4. Save this article. 5. Attempt to searching this article on 'SOW/CSM/KC'. 6. Select the article {#ap5m-release-notes__ol_eqs_czy_ckc} Notice that it will open the kb_view page of the article, and renders the article content as empty. | | Knowledge Management PRB2033473 [KB3144003](https://hi.service-now.com/kb_view.do?sysparm_article=KB3144003) | An article title isn't displayed in the Knowledge Article print view (sysparm_media=print) from Service Portal on the Australia release | An article title isn't displayed in the Knowledge Article print view (sysparm_media=print) from Service Portal on the Australia release due to a JavaScript error in KBViewArticle.jsdbx, while it works as expected in Zurich. | | | Knowledge Management PRB2054012 | Rename app-common 'Now Assist' to Otto | | | | Knowledge Management PRB2054937 | True up Store apps NAKM, KC, KCInWorkspaces and ECE | This is a product update. | | | Knowledge Management PRB2058947 | Update versions for the base instance Knowledge Management apps to include Australia and Zurich fixes | | | | Knowledge Management PRB2060905 | Updating versions for the base instance Knowledge Management apps to include Australia and Zurich fixes | There are fixes in app-knowledge-center, app-knowledge-gen-ai, app-kb-uib, and sn-enhanced-content-editor. | | | Legal Digital Forensics PRB2036701 | Add the needed RCA as part of the getRefRecord() scoping bypass directive changes | | | | Legal Hold Notification PRB2055600 | Add the needed RCA as part of the getRefRecord() scoping bypass directive changes | | | | Legal Matter Management PRB2036702 | Add the needed RCA as part of the getRefRecord() scoping bypass directive changes | | | | Legal Request Management PRB2036703 | Add the needed RCA as part of the getRefRecord() scoping bypass directive changes | | | | List Administration PRB2009991 | 'Workflow'-type fields are displaying as 'Pending - has not started' for all values | This requires a single-line change that adds a defensive .clone() call to deep-copy the choice list before WorkflowIcons.process() mutates it. This prevents the shared cache from being poisoned by in-place label overwrites. | 1. Navigate to the table schema for the 'Incident' table. 2. Create a custom field named 'Test column' with the field type set to 'Workflow'. 3. Configure 2-3 choice options for the newly created custom field. 4. Select 2-3 incident records and set values for the 'Test column' field using any of the available options. 5. Open UI Builder. 6. Create an experience and page by using the 'List Page' template. 7. Once the page is created, navigate to it on the instance. 8. From the sidebar navigation, navigate to IncidentsAll. 9. Select the Personalize fields button on the list page. 10. Add the Test column custom field to the visible columns.Observe that the workflow stages for the custom workflow type field appear empty. 11. Open any incident record that has a value set for this field (can be opened in classic view as well). 12. If the field is not visible, add it to the 'Form' view.Observe that the field displays 'Pending - has not started'. Note that even when the field value is changed via background script, it continues to display 'Pending - has not started'. {#ap5m-release-notes__ol_bp1_fnx_gkc} Expected behavior: The display value should be as per available choices. Actual behavior: It displays 'Pending - has not started' even after changing value. 'Pending - has not started' is not even available as a choice option for a field. | | List Administration PRB2030898 | The 'Selected stage' icon isn't applied when WorkflowIcons has already assigned a default icon | | 1. Open the latest Australia instance. 2. Open an articles list in Knowledge Center. {#ap5m-release-notes__ol_rps_czy_ckc} See that workflow states are displaying as 'No workflow stages available'. | | List Administration PRB2044745 | Now-record-list-connected sends encodedRecord as {} instead of '' | The variables contain 'encodedRecord': {} (empty object). It's treated as a non-empty, non-nil value, so the advanced qual is evaluated against an empty 'current' and wrong/empty results are returned. This is reproducible across base instances, but works correctly in Classic UI16. | 1. In a workspace (for example, CSM/incident), open an incident record. 2. From the right sidebar, select Create Template. 3. Select + to add a field. 4. Add a reference field that uses an advanced/dynamic reference qualifier referencing the 'current' object. 5. Open the picker ('Search for Record'). 6. Inspect the getReferenceListLayout / nowRecordListConnectedReference GraphQL call. {#ap5m-release-notes__ol_ats_czy_ckc} Expected behavior: EncodedRecord is '', so the advanced/dynamic qualifier is correctly skipped when no 'current' is available. This matches the UI16 template behavior. Actual behavior: The variables contain 'encodedRecord': {} (empty object). It's treated as a non-empty, non-nil value, so the advanced qual is evaluated against an empty 'current' and wrong/empty results are returned. | | List Administration PRB2053781 | The new AI list badge in UI16 breaks list cell content wrapping | | | | List AI Indicators PRB2051786 | The horizontal scroll for AI-tagged items in the groupedBy list is broken | When the user scroll to the right, the field isn't visible. | | | List AI Indicators PRB2055051 | Update the Otto indicators in seismic workspace lists | This is a product update. | | | List AI Indicators PRB2055052 | Update the Otto indicators in UI16 lists | This is a product update. | | | Manager Hub PRB2054008 | In Manager Hub, add a null check when using getRefRecord() | | | | Mentoring PRB2056277 | getRefRecord() scoping bypass for mentoring | | | | MID Server PRB2063491 | 'LinkedHashMap$Entry' objects connected to the LRU take a couple MB | These objects are from 'ecc_​queue_​authorization_​policy'.​ | 1. Open a local instance. 2. Connect to the MID Server. 3. Create a heap dump. {#ap5m-release-notes__ol_jqs_czy_ckc} Notice that entries of 'LinkedHashMap$Entry' for ecc_queue_authorization_policy have over 3MB for each entry. | | Mobile Experience for Field Service Management PRB2053984 | Backport getRef changes to Field Service Management (FSM) Mobile | | | | Mobile Platform PRB2033559 | Add a null check for using getRefRecord() in the script include | Enforce cross scope access restrictions when using Glide​Element​Reference.​ js​Function_​get​Ref​Record()​.​ | 1. Create two scoped apps: App A and App B. 2. In App B, create Table B with caller restriction turned on. 3. In App A, create Table A with a reference field pointing to Table B. 4. Don't grant RCA access from App A to Table B. 5. Insert a record in Table A referencing a record in Table B. 6. From the App A script, call current.ref_to_b.getRefRecord(). {#ap5m-release-notes__ol_bss_czy_ckc} Expected behavior: Access is denied, null is returned, and a violation is logged. Actual behavior: The call returns a valid record instead of null. | | Mobile Platform PRB2039101 | A device pin on mobile devices can't be turned off for Government Community Cloud (GCC) users | | 1. Log in to a mobile device for a GCC instance. 2. Note that the device pin is turned on. {#ap5m-release-notes__ol_yrs_czy_ckc} See that changing the device encryption enabled property doesn't turn off the pin. | | Mobile Studio PRB2034896 [KB3085639](https://hi.service-now.com/kb_view.do?sysparm_article=KB3085639) | sn_maib app fails to auto-upgrade when installed | This is due to an incorrect app_id declaration in the oob-app properties file. | Refer to the listed KB article for details. | | Multi-Instance Framework - Core PRB2063884 | MIF Hermes doesn't refresh the cluster configuration when the local hermes_cluster_config has no primary or after a datacenter-rule change, causing stale/failed cluster resolution for remote owners | When instance A sends a MIF async message to instance B, it needs B's Hermes cluster details (datacenter + Kafka bootstrap servers). A keeps a saved copy in the hermes_cluster_config table and reads it in Hermes​Producer​Client.​get​Cluster​Info​Set.​ Today that method only calls B's live endpoint (/api/now/hermes _cluster_info, tier-2) when A has no saved rows for B. Two gaps result: 1. Saved rows but no primary --- if A has rows for B where no one is is_primary_for_service=true (scenario like only a single non-primary cluster row), the method does not refresh. And method ensure​Topic​Location​For​Instance(String owningInstance) then finds primaryCluster == null and the send fails with 'No primary cluster found'. 2. Stale rows after a datacenter change --- if a MIMIR rule change moves B's cluster to a new DC, A's saved rows are outdated but still look complete (they have a primary), so tier-1 returns them and A never re-discovers → messages Navigate to the old cluster. | 1. Verify that Instance A has a saved Hermes cluster rows for instance B (service MIF-Hermes) pointing to B's old datacenter, or a single row that isn't marked primary. 2. Send a MIF async message from A to B. {#ap5m-release-notes__ol_zss_czy_ckc} Expected behavior: A resolves B's current cluster details and sends to the correct datacenter. Actual behavior: A uses the old/incomplete saved config and sends to the wrong datacenter, or fails with 'No primary cluster found'. | | Multimodal Service (Family Channel) PRB2051440 | On-demand MMS submission fails | The issue occurs on instances where the multimodal service URL is configured via sys_service_endpoint instead of the system property. | 1. Open an instance with the MMS plugin active. 2. Leave glide.platform_mm_service.service_url empty. 3. Configure the Multimodal service endpoint via an active sys_service_endpoint record. 4. Confirm that the batch/scheduled MMS job reaches the service. Observe that it resolves the URL from sys_service_endpoint. 5. Call new MultimodalServiceUtil() .submitOnDemand(attachmentSysId, query). {#ap5m-release-notes__ol_bts_czy_ckc} Observe that the on-demand MMS submission fails. | | Next Experience Unified Navigation PRB2019091 | If beyond the 5MB limit, a localStorage limit blocks headerMenuItems from being cached | | 1. Open an instance with thousands of apps and tens of thousands of modules, enough to make the menu payload be over 5MB. 2. Clear the caches and refresh the page. {#ap5m-release-notes__ol_tss_czy_ckc} Notice that the menu request is made on each load because the object isn't cached due to being too large. | | Next Experience Unified Navigation PRB2053821 | Update to Otto branding in Next Experience | This is a product update. | | | Now Assist in Virtual Agent PRB2056609 | Change the Knowledge Graph (KG) defaults in NAVA and Now Assist Portal | Today, the KG default is User NLQ graph. That should be changed so the defaults are: In Now Assist Virtual Agent for natural language query, change the graph to Enterprise Graph (Small) and select the tag as 'VIRTUAL AGENT DEFAULT TAG'. In Now Assist Panel for natuaral language query, change the graph to Enterprise Graph (Small) and select the tag as 'NOW ASSIST PANEL DEFAULT TAG'. | | | Now Assist Nextwave Experience PRB2059502 | Add sys_props for caching in sys_og_conversational _cache_configuration | If props are enabled on the instance, that should be reflected via cache service instantly. | | | Now Assist Nextwave Experience PRB2061245 | SessionController shouldn't try to refresh AuthorizationInfoBundle, as this is done in the Glide handshake process | When a topic execution is initiated, the conversation ID isn't available in certain Glide log entries' context maps, which complicates troubleshooting across different trace IDs instead of a unified conversation ID. The conversation ID should be available in the cache and topic execution context map in the syslog table. | | | OAuth PRB2018183 | The unallowed system property glide.oauth. jwt.token_request .honor_claim_keys is included in an upgrade payload, resulting in a misleading 'skipped' upgrade log entry | During a Zurich upgrade, the system property glide.oauth. jwt.token_request .honor_claim_keys (from com.​snc.​platform.​security.​oauth)​ appears as a skipped entry. This property is not allowed by design and therefore never loaded into sys_properties on user instances. | 1. Navigate to AllUpgrade CenterUpgrade History. 2. Open the record of upgrading in Zurich. 3. Select the Skipped Changes to Review tab. 4. Select the skipped record for sys_properties_ 107762282f223210 3698319c003f9b2f.xml. {#ap5m-release-notes__ol_yps_czy_ckc} | | OAuth PRB2052671 | Support to create an OAuth entity record within the caller scope | This is a product update. | | | On-Call Scheduling PRB1975559 | On-call contact information isn't visible for some users for some attempts | This issue only occurs when logged in as a user. | | | On-Call Scheduling PRB2034496 | In a SMS action in a the subflow 'On-Call', the 'Check Assignment Response' doesn't use Notify | The 'On‑Call: Check Assignment Response' flow uses the legacy SMS send action instead of the Notify‑based SMS action. | | | On-Call Scheduling PRB2039960 | The NotifyUtils check for notification devices should return empty when the ACL check is successful | | | | OneExtend PRB2041342 | AI Summary card stays in perpetual loading state | This issue occurs for some Business Application records using the Record Summarization capability. There are no LLM calls and no errors. | 1. Navigate to APM Workspace. 2. Open a Business Application record. Observe that the AI Summary card stays in perpetual loading. 3. Check sys_generative_ai_log. Observe that there's no LLM call logged for this request. 4. Check syslog. Observe that there's no errors; the full pipeline completes with cache HIT. 5. To compare with a working BA record, navigate to service-now.com/now/apm/application-rationalization. 6. Select the Now Asisst icon on business apps. {#ap5m-release-notes__ol_fss_czy_ckc} Observe that the summary is generated. It generates LLM calls and renders correctly. | | OneExtend PRB2056745 | Guardian preprocess flow resolves getGeoRoutingDetails() multiple times per request in NowLLMIntegration GuardianProvider | NowLLMIntegration GuardianProvider. shouldUseGatewayService() and addLLMGatewayRoutingHeader() each independently call through to GeoRoutingServiceImpl .getGeoRoutingDetails() \> resolveGeoRoutingDetails(). ShouldUseGatewayService() itself is invoked from multiple call sites across a single request's lifecycle (transformRequest, generateTrustBuilderInputs, tryLogTrustBuilderResults, and twice within getUrl()). None of these calls are memoized, so resolveGeoRoutingDetails() re-executes its full resolution logic (potentially including the licensing entitlement API call) on every invocation within the same request, even though the underlying geo-routing state can't change MID-request. | 1. Trigger a Guardian moderation request that routes through NowLLMIntegration GuardianProvider (LLM_GENERIC_ SMALL_MODERATIONS model). 2. Trace/log calls into GeoRoutingServiceImpl .resolveGeoRoutingDetails() (or set a breakpoint) during a single request's transformRequest()/getUrl() lifecycle. {#ap5m-release-notes__ol_sss_czy_ckc} Observe that resolveGeoRoutingDetails() executes repeatedly (up to six times found via code trace) instead of once per request. When the 0$ SKU entitlement isn't active, each of these calls re-invokes the expensive isEntitlementActive WithLicensingAPI() licensing call, since resolveGeoRoutingDetails() has no per-request memoization. Only the underlying getGeoRoutings() /getGeoRoutingConfigs() cache calls are cached via ADomainAwareCache. | | OneExtend PRB2056991 | Log reasoning tokens for 3P providers and Now LLM | A new field, reasoning_token_count, naming is aligned to existing token fields. The field is added to the GenAI log table. The field is populated for reasoning-capable models across all supported providers. For non-reasoning models, or when a provider returns no reasoning count, the field defaults to zero (documented) rather than null-ambiguous. A single, documented convention is applied to stored token values: store the provider's raw output_tokens and reasoning_tokens separately such that reasoning_tokens ≤ output_tokens, allowing it to derive answer-only tokens as output − reasoning. Existing consumers of the log are unaffected, and total-token reconciliation still holds. | | | OneExtend PRB2057127 | Multiple GenAI logs are created in skill chaining execution | OneExtend Execute and ExecuteSecure are missing the offGlideChainingEnabled flag. | Execute a skill chaining. Observe that the Generative AI logs are created two times. | | OneExtend PRB2059503 [KB3142021](https://hi.service-now.com/kb_view.do?sysparm_article=KB3142021) | Summarization records aren't displaying a proper response | Incident, Change, Case summarizations are failing with errors when users select the Summarize button: 'Summarization could not be completed because access to the base table Case was unsuccessful'. Error logs: 'Error sending to unified_short_url_active_1...Status 500 - \[Internal Server Error\] \[{'success':​false,​'status​Code':​429,​'message':​'Too many concurrent data insert operations in progress - additional rebuild request being ignored',​'timestamp':​'2026-​07-​17​T07:​00:​17.​752637494​Z',​'results':​{}​}​\]​'.​ | Refer to the listed KB article for details. | | Operational Technology Visibility PRB2031853 | getRefRecord() scoping bypass for Operational Technology (OT) core and OT Service Management | | | | Performance Analytics PRB1802682 | The score for average duration of a DB view is incorrect when compared with the list view for both data snapshots and classic Platform Analytics (PA) | A Glide record sets a default value of '0' for null values. Classic PA uses the Glide record. | 1. Turn on data snapshots for the indicator in incident SLA DB view. 2. Ensure to remove any scripted breakdowns. 3. Add 'AVG of Business Duration' with units as 'Time'. 4. Run data collection for both data snapshots and classic PA. 5. Compare scores. {#ap5m-release-notes__ol_b5s_czy_ckc} See that classic PA shows 11 hours 28 minutes, data snapshots shows 8 hours 35 minutes, and list view shows 20 hours 40 minutes. | | Performance Analytics PRB1949829 | Breakdown elements aren't displaying consistently on the 'workbench' widget | On the 'workbench' widget, all the elements are displaying for a breakdown when the Timeseries field has a value and the value of the property 'com.snc.pa. scorecard.breakdown. chart.max_rows' hasn't been changed. | | | Performance Analytics PRB2032037 | The Platform Analytics dashboard filters ignore Element Security Lists and display 'Nothing is available' | If the user sets up an Element Security List for a breakdown source that's used as a filter in a Platform Analytics dashboard, the filter shows 'Nothing is available'. This happens even though the user has valid access to the dashboard and the underlying data. | | | Performance Analytics PRB2035061 | Core UI widgets render blank data for fiscal and business calendar indicators | Highcharts has been upgraded from version 10.3.3 to 12.3.0. As part of this upgrade, some legacy Highcharts utility methods used by the Core UI dashboards (legacy pa_dashbaord) and widgets have been deprecated or replaced in the newer version. Any usage of older Highcharts APIs or utility methods should be reviewed and updated to use the latest supported alternatives available in Highcharts 12.3.0. | 1. On any instance in (or after) Australia's build, create any indicator source with: Standard calendarfiscal quarter or fiscal year 2. Create the indicators with these sources and run data collection jobs to populate scores. 3. Navigate to KPI Details/Analytics Hub with these indicators and make sure that the charts are visible. 4. Create core UI widgets and link the with the newly created indicators. 5. Create a core UI Dashboard and add the widgets. {#ap5m-release-notes__ol_ars_czy_ckc} Expected behavior: The same data as shown in the Analytics Hub is to be rendered. Actual behavior: All the business calendar or fiscal calendar indicator widgets render blank data. | | Performance Analytics PRB2050693 | injectWidgetContent re-executes already-loaded scripts via document.body.appendChild, causing a widget regression | injectWidgetContent in canvasUtils.js strips all \