{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":42946,"path":"release-notes/australia-security-notables.md","title":"Australia security and notable fixes","bundle":null,"doc_type":null,"release":"australia","body":"\n# Australia security and notable fixes\n\nThe Australia release contains important problem fixes.\n\n- **Australia was released on March 12, 2026.**\n - 03-04-2026\\_1355\n - glide-australia-02-11-2026\\_\\_patch0-02-24-2026\n\n**Important:** For more information about how to upgrade an instance, see [ServiceNow upgrades](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/upgrade.md).\n\nFor more information about the release cycle, see the [ServiceNow Release Cycle](https://support.servicenow.com/kb_view.do?sysparm_article=KB0547244).\n\n**Note:** This ServiceNow AI Platform® major family release is now available in ServiceNow's Regulated Market environments. For more information about services available in isolated environments, see [KB0743854](https://support.servicenow.com/kb_view.do?sysparm_article=KB0743854).\n\nFor a downloadable, sortable version of the fixed problems in this release, click [here](https://downloads.docs.servicenow.com/enus/australia/rn/patches/PRBs-A00.00.xlsx).\n\n## Security-related fixes\n\nAustralia 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, refer to [KB2770681](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2770681).\n\n## Notable fixes\n\nThe following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.\n\n\n
\n\nProblem\n\n\n\nShort description\n\n\n\nDescription\n\n\n\nSteps to reproduce\n\n
\n\nAccess Analysis Instrumentation API\n\n PRB1904862\n\n\n\nMySQL has an out of memory issue due to a complex SQL query\n\n\n\nIn the RecordInspector class, the fGlideRecord variable is defined as a class-level variable, causing the same query to be reused across all operations. In certain scenarios, this leads to the query reaching the exhaustion limit.\n\n\n\n \n\n
\n\nAccess Control List \\(ACL\\) Rules\n\n PRB1910482\n\n\n\nEnsures the QueryRangeACLAuditor doesn't generate a security attribute with a blank script\n\n\n\n \n\n\n\n \n\n
\n\nAccess Control\n\n PRB1836275\n\n\n\nScriptClassifier .isScriptUsingCurrent\\(\\) returns true despite the 'passed in' string not being current\n\n\n\n \n\n\n\n \n\n
\n\nAccess Control\n\n PRB1893366\n\n [KB2476029](https://hi.service-now.com/kb_view.do?sysparm_article=KB2476029)\n\n\n\nQuery range ACL executes for dynamic filter conditions\n\n\n\nWhen a list is querying for dynamic filter, the query\\_range ACL's are executed, resulting in unexpected behavior.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAccess Control\n\n PRB1893600\n\n [KB2178333](https://hi.service-now.com/kb_view.do?sysparm_article=KB2178333)\n\n\n\nRecordFamilyResolver. archiveTable HasACLTerms needs more optimization\n\n\n\nThere's performance issues with reports on instances with a large number of archive tables.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAccess Control\n\n PRB1900620\n\n\n\nAn ACL isn't working as expected\n\n\n\nA data condition is impacting the list\\_edit ACL, but can't be seen or updated due to an introduction to a UI Policy.\n\n\n\n \n\n
\n\nAccess Control\n\n PRB1902529\n\n\n\nThe auto-assignment feature isn't working as expected\n\n\n\nThe auto-provisioning status displayed in the UI doesn't accurately reflect the current values defined in the sys\\_properties \\(glide.security. scripting\\_role. auto\\_provisioning\\) table. Changes made to the relevant sys\\_properties aren't propagated or updated in the UI as expected.\n\n\n\n \n\n
\n\nAccess Control\n\n PRB1907444\n\n\n\nAn error message occurs randomly on pages related to the AI agent security attribute\n\n\n\nThis issue occurs in both a global and non-global scope, such as sn\\_kb\\_social\\_qa.\n\n\n\n1. Create an ACL using AI agent security attributes.\n2. Navigate to the ACL form.\n3. Attempt to update the AI agent security attribute.\n\n Expected behavior: No error message appears on the security attribute pop up window.\n\n Actual behavior: An error message appears.\n\n
\n\nAccess Control\n\n PRB1910493\n\n [KB2321524](https://hi.service-now.com/kb_view.do?sysparm_article=KB2321524)\n\n\n\nThere is slowness when loading forms with **Table Choice** fields, even after applying a 2000 record limit\n\n\n\nThe size of CACHE\\_ARCHIVE\\_TABLE\\_HAS\\_TERMS cache needs to be higher than 2000 since many instances have > 1000 archive tables.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAccess Control\n\n PRB1915184\n\n [KB2400619](https://hi.service-now.com/kb_view.do?sysparm_article=KB2400619)\n\n\n\nSecurity constraints prevent access to a requested page when visiting task.list\n\n\n\nFailing a Deny ACL from anywhere in the hierarchy prevents table access to the list of a parent table.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAccess Control\n\n PRB1939961\n\n\n\nAn incorrect class is passed as context to an ACL\n\n\n\nThe record expansion for DB view changes between X and Y, resulting in the incorrect class being passed as context to an ACL.\n\n\n\n \n\n
\n\nAccess Control\n\n PRB1943406\n\n\n\nThe **Article Body** \\('text'\\) field is read-only for new users that inherit the 'knowledge' role from a group.\n\n\n\nThis issue is only observed in the Zurich family release.\n\n\n\n \n\n
\n\nAccess Control\n\n PRB1960642\n\n\n\nRemove Datatype ACLs created for HTML and translated\\_html datatypes\n\n\n\nAfter upgrading to the Zurich release or later, users without the scripting role \\(snc\\_required\\_script\\_writer\\_permission\\) may be unable to edit HTML and translated HTML fields. Also, non-admin fulfillers can't move problem records from the 'Root cause analysis' state to the next state because they can't input values in specific mandatory fields. Finally, users experience difficulty when updating knowledge base articles following an upgrade, as the article body becomes read-only when attempting to edit.\n\n\n\n \n\n
\n\nAccess Control\n\n PRB1981898\n\n\n\nNeed properties for better control of the scope where a security attribute script gets evaluated\n\n\n\n \n\n\n\n \n\n
\n\nActivity Stream\n\n PRB1914953\n\n [KB2481528](https://hi.service-now.com/kb_view.do?sysparm_article=KB2481528)\n\n\n\nThe user is unable to enter more than 4000 characters in length on the **Journal** field after upgrading\n\n\n\nUsers are unable to copy or paste the text with more than 4000 characters on the **Journal** field after upgrading from Washington DC to Yokohama.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nActivity Stream\n\n PRB1928872\n\n [KB2709314](https://hi.service-now.com/kb_view.do?sysparm_article=KB2709314)\n\n\n\nThe CanReadRepo class encounters a ConcurrentModificationException\n\n\n\nThis concurrency issue arises because the class uses a HashMap, which is not thread-safe. The HashMap should be replaced with a ConcurrentHashMap to ensure thread-safe operations and prevent the exception.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nActivity Stream\n\n PRB1942003\n\n\n\nWork notes/Comments are unexpectedly cleared when saving a form with an empty mandatory field and the work is lost\n\n\n\nWhen there are any unfilled mandatory fields on the form, the text in the comments/work notes is getting cleared on selecting the **Save** button. It's impacting the user experience. Verified that it works fine in Xanadu and Yokohoma and on other workspaces like CSM/FSM Configurable Workspace.\n\n\n\n \n\n
\n\nAdvanced Work Assignment\n\n PRB1946412\n\n [KB2555553](https://hi.service-now.com/kb_view.do?sysparm_article=KB2555553)\n\n\n\nDefault AWA chat capacity isn't honored after a Zurich upgrade\n\n\n\nAfter upgrading to a Zurich instance, the default AWA chat capacity isn't honored. Agents are assigned more chats than the defined maximum limit.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAgent Assist\n\n PRB1910542\n\n\n\nThe window pane doesn't resize when composing an email in a configurable workspace\n\n\n\nWhen the user composes an email in a configurable workspace, the window pane doesn't resize for the email body. The 'Email Templates' frame is expanded and not scrollable, and the **Send email** button isn't visible.\n\n\n\n1. In Yokohama, navigate to an instance.\n2. Open any workspace \\(SOW/CSM/FSM\\).\n3. Open any incident in the workspace.\n4. Compose an email.\n\nNotice a new tab opens.\n\n5. Verify that the 'Email Templates' frame is opened.\n\n Expected behavior: The 'Email Templates' frame is collapsed and scrollable. The Email Client Body is the same size as the window, and the **Send email** button is visible.\n\n Actual behavior: The 'Email Templates' frame is expanded and not scrollable. The Email Client Body is the same height as the 'Email Templates' frame, and the **Send email** button only appears after scrolling down.\n\n
\n\nAgile Development\n\n PRB1924500\n\n\n\nNo access to portal sections in 'Agile 2.0 Epic Dashboard' for users with the scrum master role\n\n\n\nThe user with a scrum\\_master role should be able to see the Agile 2.0 Epic Dashboard, however they receive a query\\_match error on sys\\_portal\\_ preferences. portal\\_section.\n\n\n\n1. Open an instance.\n2. Impersonate the user abel.tuter \\(scrum\\_user\\).\n3. Navigate to **Agile Development** > **Dashboards** > **Agile 2.0 Epic Dashboard**.\n\n Observe the error message, 'Part of the query on sys\\_portal\\_preferences has been ignored because of insufficient access for 'query\\_match' operation on sys\\_portal\\_preferences.portal\\_section.'\n\n
\n\nAI Search \\(Glide\\)\n\n PRB1927798\n\n [KB2426374](https://hi.service-now.com/kb_view.do?sysparm_article=KB2426374)\n\n\n\nMissing compound index on sys\\_translated causes slowness in AI Search indexing\n\n\n\ngetTranslation in CatalogVariablesUtil can be as slow as 500ms, causing a performance issue when indexing sc\\_cat\\_item.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAI Search \\(Glide\\)\n\n PRB1932287\n\n\n\nA null pointer exception \\(NPE\\) occurs during catalog variable indexing when the choice text is empty\n\n\n\n \n\n\n\n1. Create or edit a catalog variable with choice options.\n2. Leave the **Choice Text** field empty for one or more options.\n3. Trigger the indexing process for the catalog variable.\n\n Observe that a NPE occurs during indexing.\n\n
\n\nAI Search \\(Glide\\)\n\n PRB1935842\n\n\n\nA citation can be dropped when the Genius Results limit is set to 1\n\n\n\nWhen performing AI search on NAVA, the user occasionally doesn't get any response back on NAVA. It shows a blank response.\n\n\n\n \n\n
\n\nAI Search \\(Glide\\)\n\n PRB1937244\n\n\n\njava.lang.SecurityException: AisDisableSearchSignalEvent is undefined and may be missing a global qualifier\n\n\n\n \n\n\n\n \n\n
\n\nAI Search for Service Portal\n\n PRB1942272\n\n [KB2608116](https://hi.service-now.com/kb_view.do?sysparm_article=KB2608116)\n\n\n\nUsers are unable to select multiple facets even when 'multi-select or' is selected in the facet settings\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAI Search\n\n PRB1765391\n\n\n\nA comma-separated list in the **dot\\_walk\\_fields** field setting causes validation to fail on a facet form\n\n\n\n \n\n\n\n \n\n
\n\nAI Search\n\n PRB1823355\n\n\n\nWhen there is no scope or global for a scoped admin scoped app, an invalidate query is sent\n\n\n\nAI Search doesn't work as expected and returns no results when searched with any query. On search preview, the message 'An error occurred. Check the logs for more details and contact Support if this issues continues' pops up before the query can even be triggered.\n\n\n\n \n\n
\n\nAI Search\n\n PRB1841579\n\n\n\nsn-search-combobox-desktop's use of createGraphQLEffect dispatches errorActionType due to a 401 error for public GraphQL endpoints\n\n\n\nThe batch request fails due to 401 even though the GraphQL request in the batch was actually successful.\n\n\n\n1. Set the Service Portal home page to public.\n2. Set the Typeahead Search widget to public.\n3. Open Service Portal without logging in.\n4. Open Developer Tools.\n5. Select the 'Search' box.\n\n Observe in Seismic Dev Tools that the batch request failed due to 401. Then, observe in the Network tab that the GraphQL request in the batch was actually successful.\n\n
\n\nAI Search\n\n PRB1888352\n\n [KB2399571](https://hi.service-now.com/kb_view.do?sysparm_article=KB2399571)\n\n\n\nAISearch Conversational CatalogHelpers adds extra overhead on a cs.worker thread, causing performance degradation\n\n\n\nThe AISearchConversationalCatalogHelpers script include adds additional overhead on cs.worker thread causing performance degradation up to 600ms. The degradation varies based on the number of catalogs for a given search.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAI Search\n\n PRB1893450\n\n\n\nWhen there's a search application without a name, the drop-down list appears empty\n\n\n\nWhen the user creates a search application without a name, the drop-down list for selecting search applications appears empty and displays the message 'null'.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1910311\n\n\n\nNLQ Genius Results \\(GR\\) doesn't work in portal in ynowassist and znowassist tracks\n\n\n\n \n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1912867\n\n\n\nUnable to style search result title highlighting\n\n\n\nThe title \\(now-text-link\\) highlighting isn't altered.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1913656\n\n\n\nDot-walked **Genius Result** fields are returned with dots instead of underscores\n\n\n\n \n\n\n\n1. Search for Company Policies in /esc portal.\n2. Select the **Company Policies** genius result.\n\n Observe that the navigated page has no sys\\_id.\n\n
\n\nAI Search UX\n\n PRB1917739\n\n\n\nAdd a mechanism to resend recent Asynchronous Message Bus \\(AMB\\) messages on a created subscription\n\n\n\nUnder certain circumstances, it's possible that the component establishes the AMB connection after the Genius results are sent through the channel, since both the connection subscription and the Genius results being sent are asynchronous.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1918092\n\n\n\nNow Assist synthesized response cards should not show a price for a non-billable catalog item\n\n\n\nWhen the LLM generates answers containing a catalog item, the tool tip for this item shows a price of $0.00 for non-billable item instead of showing nothing.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1952630\n\n\n\nMalformed URLs in the streaming chunks for a synthesized response cause the UI to hang\n\n\n\nThe URL renders stand-alone and sometimes isn't selectable.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1966920\n\n\n\nThe 'Now Assist detected and ...' alert is shown on the top results card when sensitivityFilter.hasMatch is false\n\n\n\nSometimes, the payload of final MESSAGE\\_RECEIVED event has the sensitivityFilter.hasMatch value as a string false. In such cases, the Genius card is hidden and an alert is shown.\n\n\n\n \n\n
\n\nAI Search UX\n\n PRB1972080\n\n\n\nConsole errors on Service Portal \\(SP\\) for non-synthesized Genius Results \\(GR\\) \\(although functionally everything works as expected\\)\n\n\n\n \n\n\n\n1. On a Yokohama or Zurich instance, disable Synthesized GRs for SP.\n2. Search for a term with which there is more than 1 GR.\n\n Observe errors in the console such as 'Failed to load @devsnc/sn-search-genius-card-assist'.\n\n
\n\nAnalytics Data API\n\n PRB1920837\n\n\n\nA Platform Analytics dashboard displays 'No data available' when 'Enable Data Cache' is enabled for Indicator Scorecard visualizations\n\n\n\nAfter an upgrade, dashboards widgets of type 'Indicator Scorecard' aren't loading as expected. The error message says 'No Data Available. No content available for the selected criteria'. This issue occurs for both new visualizations and saved visualizations.\n\n\n\n \n\n
\n\nAnalytics Data API\n\n PRB1926918\n\n\n\nThe 'Process analytics cache prefetch queue' job leads to OutOfMemoryError and the node restarts\n\n\n\nWhen the user runs the 'Process analytics cache prefetch queue' job, it loops in ChangeCheckConflictsSNC script include.\n\n\n\n1. Create a 'test\\_breakdown' table.\n2. Add a field:\n 1. Name: Name.\n 2. Type: String.\n 3. Length: 50.\n3. Populate two million records in the table with names such as Name1, Name2, etc.\n4. Create a breakdown source on test\\_breakdown without any condition.\n5. Create a breakdown of the above breakdown source.\n6. Create a 'test\\_indicator' table.\n7. Add a field:\n 1. Name: ref\\_breakdown.\n 2. Type: Reference.\n 3. Reference: test\\_breakdown.\n8. Populate two million records in test\\_indicator with reference to all the records in test\\_breakdown, respectively.\n9. Create an indicator source based on test\\_indicator, without any condition.\n10. Create an indicator based on the above indicator source.\n11. Navigate to the breakdown created in step five.\n12. Add a breakdown mapping on the **test\\_incident** and **ref\\_breakdown** field.\n13. Navigate back to the indicator.\n14. Add the breakdown.\n15. Change the system properties:\n 1. com.snc.pa.dc.hsql.max\\_row\\_count\\_indicator\\_source => 10000000.\n 2. com.snc.pa.dc.max\\_breakdown\\_elements\\_limit => 10000000.\n16. Collect 1-day score for the indicator.\n17. Create a new dashboard.\n18. Add a visualization:\n 1. Type: Single score.\n 2. Source: Indicator created in step 10.\n19. Add a filter:\n 1. Type: Single select.\n 2. Source: Breakdown created in step five.\n20. Open any memory inspection tool and check the current memory footprint.\n21. Open the filter and select a value.\n\n Notice that the memory footprint steadily increases by about 800 million until the score is displayed.\n\n
\n\nAnalytics Data API\n\n PRB1945218\n\n [KB2611116](https://hi.service-now.com/kb_view.do?sysparm_article=KB2611116)\n\n\n\nThere's a memory leak of JSON serializer in the Multivis API\n\n\n\nEach time a data request is processed, a new serializer is created and not released unless a GC is performed, which causes a memory leak.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAnalytics Data API\n\n PRB1952604\n\n\n\nThe data label indicators show the same unit in Platform Analytics Data Visualization\n\n\n\nAfter creating a data visualization that uses two indicators as data sources with different units, the data labels reflect the same unit.\n\n\n\n1. Create a data visualization \\(line\\).\n2. Add to the data sources with different units \\(\\# and % for example\\).\n3. Show the data label.\n\n Expected behavior: The data label unit in each indicator reflects the unit of the indicator.\n\n Actual behavior: The data label units in both indicators are the same, and not respecting the configured unit of the indicators used as a base.\n\n
\n\nAnalytics Export API\n\n PRB1977069\n\n [KB2732975](https://hi.service-now.com/kb_view.do?sysparm_article=KB2732975)\n\n\n\nUsers are unable to schedule data visualizations\n\n\n\nThis issue occurs when the user is attempting to schedule and send data visualizations as a PPT or PDF file. The mail is not generated after entering the reoccurrence, recipients, and subject and selecting **Save** and **Send Now**. An error is observed in the syslog.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nApplication Install Engine\n\n PRB1903785\n\n\n\nCheck if a package exists in the store\\_package directory of node before downloading it\n\n\n\nAn error appears that includes the text 'Exception reading zip stream, falling back to old cipher' and 'java.io.FileNotFoundException'.\n\n\n\n1. Install any app from the store.\n2. Check that the temp directory is created for the first time.\n3. Delete the temp directory that was created.\n4. Let the system continue installation process, during which it downloads a package again and creates a temp directory.\n\n Observe the error that appears, which includes the text 'Exception reading zip stream, falling back to old cipher' and 'java.io.FileNotFoundException'.\n\n
\n\nApplication Install Engine\n\n PRB1911704\n\n\n\nAn error appears while selecting optional spokes and installing SaaS int app\n\n\n\nDuring the preprocessing operation, the user receives an error while selecting optional spokes and installing the SaaS int app. After a second attempt, the locate remote offering plugin record for com.sn\\_sam\\_saas\\_int can't be located.\n\n\n\n1. Provision an instance with com.sam.saas.int installed on a multi node environment and optional plugins installed on another node.\n2. Try to repair the app.\n\n Observe that an error appears.\n\n
\n\nApplication Manager\n\n PRB1889269\n\n\n\nProgress worker state isn't set to complete after worker is finished\n\n\n\nInstalling plugins shows an error even when successfully completed. In the logs, it looks like the error comes from a script include. Previously, the code block was a part of a larger function that had appVersion and appID as parameters. The code was refactored into the forceSyncWithStore function, which doesn't have appVersion and appID as parameters. If the gs.info line is reached, it throws an error because those two fields were not passed into the function.\n\n\n\n1. Install the custom scoped app \\(e.g., x\\_conym\\_atf\\_sc\\_req, x\\_conym\\_hrp\\).\n2. Check 'sys\\_upgrade\\_history' to confirm the installation is marked as 'complete'.\n3. Check 'sys\\_progress\\_worker' list for the message 'Progress worker state is not set to complete after worker is finished.'\n4. Check 'syslog' for the error 'com.glide.script.RhinoEcmaError: 'appVersion' is not defined.'\n\n
\n\nApplication Manager\n\n PRB1907408\n\n\n\nA rollback is blocking the install/upgrade for non-global scope users in a domain-separated instance\n\n\n\nNon-global domain users have been blocked from being able to install/upgrade on domain-separated instances. There is now a fix to allow this behavior and hence this code change made on App Manager can now be rolled back.\n\n\n\n \n\n
\n\nApplication Manager\n\n PRB1981044\n\n [KB2719949](https://hi.service-now.com/kb_view.do?sysparm_article=KB2719949)\n\n\n\nThe latest version in the sys\\_store\\_app table is updated to the installed version after an install, thereby causing the **Upgrade** button to be unavailable in App Manager\n\n\n\nTwo functions \\(\\_fixLatestVersion ForWithdrawn InstalledApps, \\_fixLatestVersion ForWithdrawn InstalledCustomizations\\) in Application Manager's UpdateChecker. checkAvailableUpdates API \\(aka Sync in the UI\\) were missing a required GlideRecord.addQuery constraint when the 'sn\\_appclient. enable\\_app\\_ manager\\_checksums \\_cache' sys\\_property was set to true \\(default\\). This issue led to the latest\\_version being set to the incorrect values on Install/Sync.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nApplication Manager\n\n PRB1986694\n\n [KB2753355](https://hi.service-now.com/kb_view.do?sysparm_article=KB2753355)\n\n\n\nApp Manager and My Company Applications incorrectly shows available updates after update checker\n\n\n\nWhen publishing a new version of the app, it doesn't appear in 'My Company Application'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAppointment Booking\n\n PRB1940645\n\n\n\nA datepicker isn't selectable until the page is refreshed\n\n\n\nIf the user loads an appointment booking on a portal home page and then uses the Service Portal \\(SP\\) date picker on a different portal page, the datepicker won't be selectable until the page is refreshed.\n\n\n\n \n\n
\n\nAsset Management\n\n PRB1894759\n\n [KB2609881](https://hi.service-now.com/kb_view.do?sysparm_article=KB2609881)\n\n\n\nThe **Currency** field on the 'Contract' form multiplies with 100 for some currencies\n\n\n\nIn the user's instance, the user profile has the country code set to one that uses a comma as the decimal separator, specifically Europe/Sweden \\(SE\\). Because of this, each time the form is loaded, the value gets multiplied by 100 due to the logic in the onLoad client script.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAsset Management\n\n PRB1947295\n\n [KB2570280](https://hi.service-now.com/kb_view.do?sysparm_article=KB2570280)\n\n\n\nThere's an error when creating an asset when populating a serial number\n\n\n\nNotice the error message: 'onChange script error: TypeError: Cannot read properties of undefined'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAsset Management\n\n PRB1963341\n\n\n\nThe 'sn\\_itam\\_common.CommonMobileUtils' script include doesn't exist in the system\n\n\n\nAsset Management Common plugins aren't activated as a dependency of IT Asset Management mobile. Even when activated, the script include used in the mobile action item is missing.\n\n\n\n \n\n
\n\nAsynchronous Message Bus \\(AMB\\)\n\n PRB1909861\n\n\n\nA lazy load of Asynchronous Message Bus \\(AMB\\) messages cause an additional query for every message published\n\n\n\nA performance improvement implemented in Yokohoma was designed to optimize database operations by loading the actual AMB message column from the database only when subscribers for that message exist. However, this optimization has been compromised by a request that updates the redelivery cache, which inadvertently causes the new query to be triggered for every published message, regardless of subscriber status. The intended performance benefit of selective database querying is being negated, as the system is now querying the database for all messages instead of only those with subscribers.\n\n\n\n \n\n
\n\nAsynchronous Message Bus \\(AMB\\)\n\n PRB1910946\n\n\n\nThe Record Watcher \\(RW\\) Asynchronous Message Bus \\(AMB\\) message censor doesn't work when AMB lazy load is turned off\n\n\n\nWhen glide.amb.messages.lazy.load.data is set to 'false', having a record open in two browsers and updating it in one doesn't update it in the other browser.\n\n\n\n1. Set glide.amb.messages.lazy.load.data to 'false'.\n2. Open a record in two different browsers.\n3. Update the record in one browser.\n\n Notice that the **Record** field in the other browser window isn't updated.\n\n
\n\nAttachments to Records\n\n PRB1889947\n\n\n\nInstance nodes do not appear and this error appears: javax.crypto.AEADBadTagException: Error finalising cipher data: mac check in GCM failed\n\n\n\nInstance JVMs won't start after the error, ' java.io.IOException: javax.crypto.AEADBadTagException: Error finalising cipher data: mac check in GCM failed'.\n\n\n\n \n\n
\n\nAttachments to Records\n\n PRB1950689\n\n [KB2612680](https://hi.service-now.com/kb_view.do?sysparm_article=KB2612680)\n\n\n\nAfter upgrading to Zurich, the attachment variable within the record producer isn't incorporated into the activity stream\n\n\n\nThis issue was verified by modifying the 'Ask a question' record producer in a base instance. An attachment variable is added and the attachment appears in the activity stream. However, performing the same test in the Zurich release did not result in the attachment being shown in the activity stream.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAudit History\n\n PRB1938364\n\n [KB2531096](https://hi.service-now.com/kb_view.do?sysparm_article=KB2531096)\n\n\n\nA large amount of history \\(audit\\) data can lead to node memory contention on a node when loading a form\n\n\n\nWhen loading a form for the first time, the node may run out of memory and crash. This happens if the history set has to be built to load the activity stream and if there's a lot of data to be loaded.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAuthentication\n\n PRB1927594\n\n [KB2423799](https://hi.service-now.com/kb_view.do?sysparm_article=KB2423799)\n\n\n\nOauth token calls fail from an API authenticated sessions\n\n\n\nAs part of multi-factor authentication enforcement for local internal user logins, adaptive authentication is enabled and configured the MFA context policy. Once an API authenticated session is established, it's expected to make only API integration \\(or non-interactive\\) related calls, and the '/oauth\\_token.do' call falls outside of integration calls.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAuthentication\n\n PRB1947882\n\n\n\nAfter upgrading within Yokohama, the email MFA option is missing and only TOTP is shown\n\n\n\nAfter upgrading, users are no longer able to see the email multi-factor authentication \\(MFA\\) option during login. Only the Authenticator App \\(TOTP\\) is displayed, even after selecting **Try another way to verify**.\n\n\n\n \n\n
\n\nAuthentication\n\n PRB1960277\n\n\n\nAn Supplier Lifecycle Operations \\(SLO\\) error displays when the SLO URL is empty in Identity Provider \\(IdP\\) configuration\n\n\n\nWhen the **SLO \\(single logout\\) URL** field is left empty in the IdP configuration, the system redirects to external\\_logout\\_complete with an error code slo\\_error. However, this behavior is incorrect. Since SLO is optional, the absence of an SLO URL shouldn't trigger an error. This issue also appears in mobile.\n\n\n\n1. Navigate to the 'IdP Configuration' page.\n2. Ensure that the SLO URL is left empty.\n3. Log in using the configured IdP.\n4. Log out.\n\n Expected behavior: The system should successfully log out and redirect to the external\\_logout\\_complete page without any error code, since SLO is optional.\n\n Actual behavior: The system redirects to external\\_logout\\_complete with error code slo\\_error, implying a failure even though SLO wasn't configured.\n\n
\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1900486\n\n\n\n'Run Server Side Validation Script' is not supported by reusable tests\n\n\n\nThe main test fails with the message, 'Unable to find step configuration 'Execute Test: reusable \\(multi steps\\)' with sys\\_id '' for step with order 1.'\n\n\n\n \n\n
\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1924154\n\n\n\nAttempting to run a non-UI test in Cloud Runner results in the individual tests being 'Pending' forever\n\n\n\nThis also occurs if running through the CICD Run ATF Suites API and setting 'run in cloud' to true.\n\n\n\n \n\n
\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1951016\n\n [KB2579637](https://hi.service-now.com/kb_view.do?sysparm_article=KB2579637)\n\n\n\nAll steps in Automated Test Framework \\(ATF\\) pass a test, but UI tests with many console logs fail\n\n\n\nThis issue specifically occurs when any single UI batch in an ATF test produces more than 1 megabyte worth of console logs \\(approximately 500,000 characters worth of data\\).\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nAutomated Test Framework \\(ATF\\)\n\n PRB1959359\n\n\n\nThere's an issue with the clean-up job for metadata tracing out of memory: sysauto\\_script.do? sys\\_id=26c1592 cff442210940 effffffffff0b\n\n\n\n \n\n\n\n \n\n
\n\nCache\n\n PRB1955869\n\n [KB2595527](https://hi.service-now.com/kb_view.do?sysparm_article=KB2595527)\n\n\n\nThe ScriptEnginesTables cache is undersized in the Zurich release, causing increased processing time\n\n\n\nIf an instance has more than 50 script engines installed \\(via plugins and applications\\), setting the current size to 50 for the ScriptEnginesTables cache may lead to an increase in processing times. This could lead to semaphore contention and/or exhaustion, resulting in a significant increase in total transaction time and processing time and script time.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1880009\n\n\n\nAttachments aren't uploaded in the 'Agent Chat' window from HR Agent Workspace\n\n\n\nThis is happening for HR Core.\n\n\n\n \n\n
\n\nCase and Knowledge Management for HR Service Delivery\n\n PRB1905312\n\n [KB2415334](https://hi.service-now.com/kb_view.do?sysparm_article=KB2415334)\n\n\n\nThe 'Feedback definition' table doesn't display any feedback records\n\n\n\nFeedback definitions aren't visible. Also, users can't create a feedback definition.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCI Lifecycle Management API\n\n PRB1772623\n\n [KB2518604](https://hi.service-now.com/kb_view.do?sysparm_article=KB2518604)\n\n\n\nList view does not translate non-English languages for Lifecycle Stage and Lifecycle Stage status\n\n\n\nThis issue occurs when the user's language preference is set to a non-English language.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCMDB Data Manager\n\n PRB1892066\n\n [KB2217546](https://hi.service-now.com/kb_view.do?sysparm_article=KB2217546)\n\n\n\nA policy form doesn't honor retirement definitions correctly in enforced conditions when multiple retirement definitions are enabled\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCMDB Data Manager\n\n PRB1943938\n\n\n\nThe Data Manager policy jobs experience increasing slowness creating tasks when processing large data sets\n\n\n\nThe CMDB Data Manager policy for running jobs keep running for a long time because the underlying SQL query has pattern of LIMIT and OFFSET on the CMDB table. The table has a lot of data, and thus those SQL queries start showing increased execution time, effectively slowing the job running them.\n\n\n\n \n\n
\n\nCMDB Data Manager\n\n PRB1964689\n\n\n\nCMDBRetirementScriptableAPI doesn't handle policies targeting tables that don't begin with 'CMDB'\n\n\n\nData Manager policies that target only tables without 'CMDB' in the start of the table name can't be published or run due to the API not correctly handling the search for those tables' defined retirement state.\n\n\n\n \n\n
\n\nCMDB Identification and Reconciliation\n\n PRB1955881\n\n\n\nsn\\_cmdb.\\_\\_rel\\_type\\_cache holds a lot of memory\n\n\n\n \n\n\n\n \n\n
\n\nCMDB Identification and Reconciliation\n\n PRB1957741\n\n\n\nOn the CMDB Health Dashboard, a parent metric, like completeness, displays a total count of less than one of the sub-metric \\(required or recommended\\)\n\n\n\nThis causes totals to be incorrect.\n\n\n\n \n\n
\n\nCMDB Query Builder\n\n PRB1952766\n\n [KB2634786](https://hi.service-now.com/kb_view.do?sysparm_article=KB2634786)\n\n\n\nCalls to QueryBuilder from ServiceMapping return no results when executing in the new V2 mode\n\n\n\nIn Zurich, processes that call into Query Builder can have no results returned. There are two scenarios where this occurs. Firstly, a service CI populated via CMDB Group containing a saved query \\(as constructed in Query Builder\\) can have no 'svc\\_ci\\_assoc' records, even when rerunning the service population. However, the expected CIs will appear when viewing the CMDB Group or the saved query directly. Secondly, instances configured to use 'Zing' for Global Search don't return any CI records in the findings. These different methods both rely on the 'CMDBGroup' API, which may not return results of query execution when using the 'v2' execution mode introduced in Zurich. Instances are at risk if they use dynamic CI groups which are built using Query Builder, they're on an impacted Zurich Version, and the system property glide.cmdb.query.execution\\_mode = 'v2'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCMDB Query Builder\n\n PRB1977703\n\n [KB2727703](https://hi.service-now.com/kb_view.do?sysparm_article=KB2727703)\n\n\n\nQuery Builder in V2 mode can cause memory issues due to a static variable\n\n\n\nAn internal variable which is declared as static keeps being appended and thus creates a large memory footprint. This would happen if one or more queries are executed enough times to bloat this variable.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nColumn Level Encryption Enterprise\n\n PRB1957091\n\n\n\nSys attachments zip data and Column Level Encryption jobs aren't completed\n\n\n\nSys attachments zip data and Column Level Encryption jobs aren't completed even when the CLE Migration Dashboard correctly reads this property and displays 'migration success' and com.glide.cle.allow\\_ec\\_key\\_deletion is set to 'true'.\n\n\n\n1. Navigate to the filter navigator.\n2. Remove triple DES usage.\n\n Observe that column level encryption data migration isn't completed. Notice that the sys\\_property 'com.glide.cle.allow\\_ec\\_key\\_deletion' is set to true. The CLE Migration Dashboard correctly reads this property and displays 'migration success'.\n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1909893\n\n [KB2250398](https://hi.service-now.com/kb_view.do?sysparm_article=KB2250398)\n\n\n\nThe 'Run' filter can apply an old condition and not pick up the newly applied filter conditions\n\n\n\nIn the CMDB Relationship editor, the filter can apply old conditions and not pick up the newly applied filter conditions. This issue isn't consistently reproducible but there's a problematic API call made.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1924215\n\n\n\nThe 'Owned By' \\(search\\) reference dialog doesn't close, and nothing happens after selecting the selected user\n\n\n\nThis occurs in the CSDM Application Service form view.\n\n\n\n \n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1930654\n\n\n\nThe legacy health dashboard doesn't tell the user that the dashboard is deprecated/no longer supported\n\n\n\nUsers have bookmarked, saved, or edited links to the legacy health dashboard, meaning they can still access it. There's a lot of confusion on why the dashboard is no longer working as intended. There should be a message to tell the user this dashboard has been migrated to CMDB Workspace.\n\n\n\n1. Check out a Washington DC instance.\n2. Make a favorite for Health Dashboard - CMDB view.\n3. Upgrade your instance to X+.\n4. Select the bookmark for the CMDB view.\n\n Expected behavior: When users navigate to the legacy dashboard, they should be able to see a message telling them to use the new health dashboard and that the legacy dashboard is no longer supported.\n\n Actual behavior: Observe that the legacy health dashboard has some broken widgets, no colors, etc. But there is no indication that this dashboard is retired or has been migrated.\n\n
\n\nConfiguration Management Database \\(CMDB\\)\n\n PRB1949356\n\n\n\nThe exact count match check results in an incorrect duplicate task creation\n\n\n\nAfter upgrading to Zurich, de-duplication \\(dedupe\\) tasks are created incorrectly under certain scenarios. As a result, a large number of records are created in the duplicate\\_audit\\_result table, causing significant database growth. Instead of updating existing entries, new records are inserted during each subsequent run. In one scenario, the de-duplication tasks are created when they were previously working. In another scenario, users with many hosts that contain cmdb\\_serial\\_number records with the same serial\\_number and serial\\_number\\_type notice that the number of duplicate\\_audit\\_result can grow to be tens of millions daily.\n\n\n\n \n\n
\n\nConnections and Credentials\n\n PRB1974412\n\n [KB2730719](https://hi.service-now.com/kb_view.do?sysparm_article=KB2730719)\n\n\n\nCertain outbound HTTP requests fail randomly with '401 unauthorized' even though valid tokens exist\n\n\n\nWhile executing outbound HTTP request using REST step, the request misses the authorization header even though the valid OAuth token exists.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nContract Management\n\n PRB1913448\n\n\n\nThe payment amount and total amount are incorrectly displayed in the local currency value under USD currency\n\n\n\nWhen the user sets a payment amount using a local currency \\(for example, NOK\\) when selecting **Adjust** on the contract, the payment amount gets saved on the XML. When re-opening the record in the 'Form' view, it defaults to USD, but shows the amount that originally belonged to NOK. This behavior applies to both **payment\\_amount** and **total\\_cost** fields.\n\n\n\n1. Open a contract from the ast\\_contract table.\n2. Select **Adjust**.\n3. Enter a new payment amount and currency, for example, NOK 966.00.\n4. Search and view the same Contract on List view.\n5. Notice that payment amount and total amount are both reflected as \\(NOK\\)966.00 and \\(USD\\)96.7669 when selecting **Toggle currencies**.\n6. Open the record in the 'Form' view.\n\n Notice that the payment amount is USD 966.\n\n
\n\nCore Platform\n\n PRB1593473\n\n\n\nPerformance Dashboard requests time out for instances with a large number of MID servers\n\n\n\nIt requests a time out when they call new Diagnostics\\(\\) on the widgets in the Diagnostics dashboard because that script include accumulates all the data from each node's **node\\_stats** field. When there are many MID servers and nodes, parsing XML files can take longer than timing out. The mid-server portion is coming from the 'instance' XML stats include, which is part of the list of includes that is stored in the referenced node\\_stats record and one of the includes in the 'glide.cluster.xmlstats' property. XMLStatsInstance.java is the class for this.\n\n\n\n \n\n
\n\nCore Platform\n\n PRB1644827\n\n [KB1648914](https://hi.service-now.com/kb_view.do?sysparm_article=KB1648914)\n\n\n\nThere's errors when committing an update set that creates a child table with a **Function** field\n\n\n\nVersion loading is stopped by DictionaryUpdateLoader for sys\\_dictionary\\_table\\_name\\_null. Committing an update set that creates a child table with a **Function** field fails. The update set log produces errors.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nCurrency Administration\n\n PRB1930077\n\n [KB2481239](https://hi.service-now.com/kb_view.do?sysparm_article=KB2481239)\n\n\n\nThe 'Exchange Rate Schedule' job has been replaced by the 'Update Currency Conversion Rates' job in Yokohama\n\n\n\nUpdating the steps to use currency conversion rates.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Compaction\n\n PRB1816028\n\n\n\nThe 'Unexpected Compactor' job runs on the sys\\_attachment\\_doc table, causing an outage\n\n\n\n \n\n\n\n \n\n
\n\nDatabase Indexes\n\n PRB1901971\n\n [KB2206973](https://hi.service-now.com/kb_view.do?sysparm_article=KB2206973)\n\n\n\nA missing index on the 'sys\\_id' column of the 'cmdb\\_qb\\_result\\_base' table causes a replication lag when the table size is large\n\n\n\nThe index on the 'sys\\_id' column of the 'cmdb\\_qb\\_result\\_base' table is missing on 14000+ instances. Due to this missing index, when the 'Table Cleanup on Query Status' \\(qb\\_query\\_status\\) table is triggered on such instances, it can lead to replication lag issues, especially when large volumes of records need to be deleted from the qb\\_query\\_status table. This can lead to memory exhaustion, and records are not properly cleaned up.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Access\n\n PRB1829096\n\n\n\nThere's an incorrect timeref display value for ISO week 53\n\n\n\nIt's cosmetic as only the axis labels are affected and the real values are preserved.\n\n\n\n \n\n
\n\nDatabase Persistence - Data Access\n\n PRB1834259\n\n\n\nA syntax error or access rule violation is detected by a database\n\n\n\nThe following error is displayed when a glidefunction column is used as a sort in a list view with a filter on a denormalized glidelist: '\\(ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list Position: 2328\\)'.\n\n\n\n \n\n
\n\nDatabase Persistence - Data Access\n\n PRB1864866\n\n\n\nThe CMDB table record on sys\\_db\\_object is not loading, and the transaction is cancelled due to the large number of CMBD columns and indexes on the CMBD table\n\n\n\nThe slowness is observed on MariaDB hosted instances as well.\n\n\n\n1. Log in to an instance as a user with elevated privileges.\n2. Open sys\\_db\\_object table.\n3. Search for the name 'cmdb'.\n\n Notice that the transaction keeps loading for 5 minutes and eventually cancels out. A similar call stack is observed when loading the 'v\\_index\\_creator\\_list' with the filters as 'reference table' is 'Base Configuration Item'.\n\n
\n\nDatabase Persistence - Data Access\n\n PRB1922171\n\n [KB2617119](https://hi.service-now.com/kb_view.do?sysparm_article=KB2617119)\n\n\n\nThe CONTAINS query interferes with the RLQUERY in a hybrid table\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Access\n\n PRB1924708\n\n\n\n'Show Matching' a list and 'order by' **ref\\_** fields throws a null pointer exception\n\n\n\nAfter the user orders the list, the records disappear.\n\n\n\n1. Navigate to task.list.\n2. Open **Configure** > **List Layout**.\n3. Add the planned start date \\[change request\\] to the list of columns.\n4. Save.\n5. Add watch list to the view.\n6. Populate the watch list of some records.\n7. Show Match watch list.\n8. Order by the planned start date \\[change request\\].\n\n Expected behavior: The records show.\n\n Actual behavior: The records disappear.\n\n
\n\nDatabase Persistence - Data Access\n\n PRB1925389\n\n\n\nGlide queries that use a search term query in conjunction with an order-by on a **Date-time** field return a null pointer exception\n\n\n\nFor instances running on RaptorDB, Glide queries that use a search term query in conjunction with an order-by on a **Date-time** field return a null pointer exception for matching records that have a null order field value.\n\n\n\n \n\n
\n\nDatabase Persistence - Data Access\n\n PRB1944805\n\n [KB2552260](https://hi.service-now.com/kb_view.do?sysparm_article=KB2552260)\n\n\n\ngetDisplayValue\\(\\) throws a null pointer exception on many types of catalog variables\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Access\n\n PRB603878\n\n [KB0621061](https://hi.service-now.com/kb_view.do?sysparm_article=KB0621061)\n\n\n\nCondition Builder causes an exception when using a 'matches regex' condition\n\n\n\nWhen the user tries to use a 'matches regex' condition, the following error appears: 'Syntax Error or Access Rule Violation detected by database \\(You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MATCH\\_RGX 'pmon'' at line 1\\)'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Management\n\n PRB1868796\n\n [KB2071053](https://hi.service-now.com/kb_view.do?sysparm_article=KB2071053)\n\n\n\nUpdating a record in the sn\\_vul\\_vulnerability table via 'Data Management Update' jobs \\(sys\\_dm\\_update\\) throws an error\n\n\n\nThe user can open a record in the sn\\_vul\\_vulnerability table and update it, but when the same user tries to update it via the sys\\_dm\\_update job, it throws an error. Error: 'The user does not have the necessary permissions to update records in table sn\\_vul\\_vulnerability'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Management\n\n PRB1891527\n\n\n\nWorkflows aren't properly evaluating conditions to determine if tasks should fire\n\n\n\nFilter conditions work differently between Xanadu and Yokohama instances.\n\n\n\n \n\n
\n\nDatabase Persistence - Data Management\n\n PRB1904961\n\n [KB2328103](https://hi.service-now.com/kb_view.do?sysparm_article=KB2328103)\n\n\n\nDB compaction fails when there's a table with more than the MAX\\_INT number of rows\n\n\n\nA user has a sys\\_audit table that has almost 8 billion rows. The query that fetches the size of tables parses out the number of rows as integer, which causes this error. There isn't a way to prevent it from reading the results for certain tables: '...worker.2 worker.2 txid=9f2eff89c30a CompactionQualificationJob SEVERE \\*\\*\\* ERROR \\*\\*\\* Compaction qualification failed java.sql.SQLException: Out of range value for column 'table\\_rows' : value 7854795901 is not in class java.lang.Integer range...'.\n\n\n\n1. Insert more than the largest value of a Java integer number of rows into a table.\n2. Run the 'DB compaction' job.\n3. Check that the job completes.\n\n
\n\nDatabase Persistence - Data Management\n\n PRB1908446\n\n [KB2256996](https://hi.service-now.com/kb_view.do?sysparm_article=KB2256996)\n\n\n\nTurn off the 'Collect Reliability Metrics for Data Management' job\n\n\n\n'Collect Reliability Metrics for Data Management' leads to long running queries when the TableStatsService API / Reliability metrics API is called on large tables with conditions. It causes performance issues.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Management\n\n PRB1949832\n\n\n\nThe 'Physical Table Stats Gatherer' job runs long due to an influx of query with hash 943940198\n\n\n\nThis occurs after the user upgrades to Zurich. Due to the slow query, the job ran more than two days.\n\n\n\n \n\n
\n\nDatabase Persistence - Data Management\n\n PRB1988503\n\n [KB2764725](https://hi.service-now.com/kb_view.do?sysparm_article=KB2764725)\n\n\n\nActive subflow executions with clean parent flow executions are listed as 'Unreferenced Records' and are deleted by DMUnreferencedRecordCleaner\n\n\n\nThis issue was observed in Zurich. If a parent flow completes while an associated asynchronous subflow continues running, the completed parent flow context is cleaned up by the retention policy by routine system cleanup. As a result, the running subflow becomes unreferenced, and may be removed during routine system cleanup.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Scale\n\n PRB1860663\n\n\n\nAn index is created without a size limit for some unbounded fields, which leads to errors while creating an index or adding data\n\n\n\nThe 'AWS Service Catalog Connector' \\( x\\_126749\\_aws\\_sc\\) installation is left with an invalid index in the 'Task' table in RaptorDB. There's an error: 'SEVERE \\*\\*\\* ERROR \\*\\*\\* Exception executing deferred indexes for class: task...'\n\n\n\n \n\n
\n\nDatabase Persistence - Data Scale\n\n PRB1906463\n\n\n\nExcessive DBConnectionPools messages in logs results in multiple default semaphores\n\n\n\nBoth UI and worker nodes are impacted.\n\n\n\n1. Make DB connection open requests slow \\(10+ seconds wait\\).\n2. Generate some load to exceed connection pool size/UI transaction semaphore count.\n\n Observe that UI threads are getting stuck on a connection pool while it's blocked waiting for a connection to be created.\n\n
\n\nDatabase Persistence - Data Scale\n\n PRB1928008\n\n [KB2428930](https://hi.service-now.com/kb_view.do?sysparm_article=KB2428930)\n\n\n\nAn upgrade to Yokohama hangs\n\n\n\nUpgrades to Yokohama releases may hang for certain instances because of contention on the query registrar.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Persistence - Data Scale\n\n PRB1959979\n\n\n\n'Get connections from secondary pool' doesn't retry more than once\n\n\n\nThe retry count is capped because failImmediate is always set to true for secondary pools. This causes some issues with read replica routing.\n\n\n\n \n\n
\n\nDatabase Persistence\n\n PRB1848049\n\n\n\nAdd support for a new RaptorDB feature to prevent DDL locking\n\n\n\nDDL locking occurs when a long running query is executed.\n\n\n\n1. Execute a long running query against Postgres.\n2. Attempt to alter a table using an instant operation.\n\n Notice that DDL blocks all traffic until the long running query finishes.\n\n
\n\nDatabase Persistence\n\n PRB1937018\n\n\n\ndbi.truncateTable\\(table\\_name\\) is truncating a table name when the table name is >29 characters and the 'Daily schedule' job isn't able to drop that table\n\n\n\nIn recent releases, DBTruncateUtil.truncateTable\\(\\) calls for tables with long names leave orphaned tables behind in the DB and causes backups to fail.\n\n\n\n \n\n
\n\nDatabase Persistence\n\n PRB1971863\n\n\n\nTransaction canceled: 'Failed to get database connection due to exhaustion of connection pool on the node'\n\n\n\nA spike in requests can produce a demand exceeding pool max capacity. Some connections are created, but the process is slow, causing various race conditions and delays and eventually causing a timeout in one operation.\n\n\n\n \n\n
\n\nDatabase Views\n\n PRB1826155\n\n [KB2243925](https://hi.service-now.com/kb_view.do?sysparm_article=KB2243925)\n\n\n\nBoolean string literals in a view table produce an error or cause the wrong results to be returned\n\n\n\nThe fix for PRB1764595 does not address the issues caused by boolean string literals in a view table that produce an error or cause the wrong results to be returned.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDatabase Views\n\n PRB1900333\n\n\n\nQuerying a database view using an IN query on the view's sys\\_id uses a list of encoded sys\\_id values, resulting in an invalid query in Yokohama\n\n\n\nWhen a database view is queried a sys\\_id, a unique value is generated by encoding the sys\\_ids from the matching joined records from each view table, which results in the row being returned.\n\n\n\n \n\n
\n\nData Fabric Table Glide Services\n\n PRB1937036\n\n\n\nData Fabric memory usage of GlideTableInfo\n\n\n\nPerformance testing on an instance experiences out of memory issues and node restarts when a long running transaction or a high number of transactions are executed. About 6.1% of the total memory is used by the JVM in a heap dump using GlideTableInfo.\n\n\n\n \n\n
\n\nData Privacy \\(Classic\\)\n\n PRB1881041\n\n\n\nThe **New** button displays on related lists where it isn't configured\n\n\n\n \n\n\n\n1. Provision an instance with the GRC: Advanced Risk and GRC: Risk Management Workspace plugins installed.\n2. Open the 'Lists' page in the Risk Workspace.\n3. Navigate to 'Risk assessment project' section.\n4. Select the **New** button visible at the top right on the list page.\n5. Fill all of the required fields.\n6. Make sure the impersonating user is set as the owner.\n7. Move the project to the 'Risk scoping stage'.\n\n Observe the **New** button that's visible on the 'Risks' related list.\n\n
\n\nDecision Table \\(Family\\)\n\n PRB1930728\n\n\n\nAdding a new choice to a choice type results in a decision table\n\n\n\nThe user should be able to create a choice type result with a new choice result, or add a new choice to the choice type result in a decision table. However, there's an error.\n\n\n\n1. Create a decision table and add at least one input and one condition.\n2. Create a choice type result with a new choice list.\n\n Notice that the user can create a result type choice, but it gives an error whenever they try to add new choice in choice list.\n\n
\n\nDecision Table \\(Family\\)\n\n PRB1971318\n\n\n\nUsers are unable to publish decision tables\n\n\n\nThe decision table isn't published and a 'Could not update the decision table' message is displayed.\n\n\n\n1. Create a decision table with a result column of type choice and capture it in update set.\n2. Create new choice and add a couple of choices.\n3. Import the decision table into another instance.\n4. Publish the decision table to move it from draft to publish.\n5. Then move it draft state and publish again.\n\n Expected behavior: The decision table should be published.\n\n Actual behavior: The decision table isn't published and the 'Could not update the decision table' message is displayed.\n\n
\n\nDeclarative Actions\n\n PRB1975231\n\n\n\nField decorators for variable fields are cached in a way that causes issues, causing them to not show up sometimes\n\n\n\n \n\n\n\n1. Create a variable set.\n2. Create a catalog item for specific catalogs only.\n3. Add the catalog item to the included in list for the variable set.\n4. Navigate to the catalog item.\n5. Select **Try it**.\n6. Order the item.\n7. Navigate to the request record.\n8. Navigate to the related list.\n9. Navigate to the request item record.\n10. Note the sys id and visit the record in workspace.\n11. Add a reference variable to the variable set created above.\n12. Navigate to the catalog item.\n13. Try it again.\n\n Following the same steps above, users end with the variable fields in workspace without field decorators.\n\n
\n\nDiscovery\n\n PRB1509705\n\n [KB0967278](https://hi.service-now.com/kb_view.do?sysparm_article=KB0967278)\n\n\n\nThe Simple Network Management Protocol \\(SNMP\\) object identifier \\(OID\\) 1.3.6.1.4.1.1602.4.7 is discovered as 'Network Multi-PDL Printer Board-D1/H1' and is used by many different families and models of Canon multi-function printers\n\n\n\nThe SNMP Classification OID record 1.3.6.1.4.1.1602.4.7 is used by whole families of Canon multi-function printers. This OID record causes them all to be model 'Network Multi-PDL Printer Board-D1/H1' regardless of the true family/model.\n\n\n\nDiscover a Canon printer with the OID 1.3.6.1.4.1.1602.4.7.Expected behavior: Either the make/model needs to be extracted from the other OID data, such as sysDesc, or no model name entered in this OID.\n\nActual behavior: The Printer CI will be created with Model 'Network Multi-PDL Printer Board-D1/H1', which is incorrect.\n\n
\n\nDiscovery\n\n PRB1636956\n\n [KB1224543](https://hi.service-now.com/kb_view.do?sysparm_article=KB1224543)\n\n\n\nPerform Refresh Member accounts' Discovery is stuck in active state because of service\\_account\\_reload system commands in ECC queue\n\n\n\nThis is not related to the **Refresh Member Accounts** UI action. 'Perform Refresh Member accounts' is triggered by Cloud Schedule when glide.discovery.cdu.auto\\_ refresh\\_sub\\_accounts\\_and\\_ldcs is set to 'true'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1681006\n\n [KB1641144](https://hi.service-now.com/kb_view.do?sysparm_article=KB1641144)\n\n\n\nObject identifier \\(OID\\) records for Cisco ASA-55xx Firewalls are not consistently using the Next-Generation Cisco Firewall Discovery pattern and Cisco Firewall Device \\[cmdb\\_ci\\_firewall\\_device\\_cisco\\] CI class\n\n\n\nThere are 111 OID records included out-of-box for Cisco ASA 5500 series Firewalls. Only 7 of these are set for the correct classifier/table and Next-Generation Cisco Firewall Discovery pattern. Of the remaining, 26 are set to the generic IP Firewall \\(cmdb\\_ci\\_ip\\_firewall\\) class and probe, which is acceptable, but doesn't fully discover the device. However, 27 are set as routers, and 51 as switches, which is incorrect.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1752501\n\n [KB1639128](https://hi.service-now.com/kb_view.do?sysparm_article=KB1639128)\n\n\n\nDifferent certificate checks between VMWareVCenterVMTagsProbe and VMWarevCenterVMsProbec / cVMWarevCenterDatastoresProbe\n\n\n\nWhen doing VMWare Discovery currently, there are different certificate checks between VMWareVCenterVMTagsProbe and VMWarevCenterVMsProbe/ VMWarevCenterDatastoresProbe. Certificate checks are only being done when one wants to discover VMWareVCenterVM tags.\n\n\n\n1. Run VMWare Discovery.\n2. Discover tags.\n\n Expected behavior: The MID Server platform's MID Security policy should be left to define whether certificate checks are needed or wanted for the vCenter endpoint.\n\n Actual behavior: VMWareVCenterVMTagsProbe does a certificate check itself, which isn't needed.\n\n
\n\nDiscovery\n\n PRB1833795\n\n [KB1825538](https://hi.service-now.com/kb_view.do?sysparm_article=KB1825538)\n\n\n\nThe credential alias doesn't work for applicative credentials\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1862106\n\n [KB2436326](https://hi.service-now.com/kb_view.do?sysparm_article=KB2436326)\n\n\n\nGlobal IP exclusion isn't working for a cloud VM schedule\n\n\n\nNot all the global exclusions are working for a Cloud Discovery.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1898321\n\n [KB2260681](https://hi.service-now.com/kb_view.do?sysparm_article=KB2260681)\n\n\n\nLogs for patterns execution on Discovery logs need to be less alarming\n\n\n\nDiscovery logs for patterns indicate a pattern failure 'Failed Exploring CI Pattern', even though the pattern brought data back.\n\n\n\n1. Run lab and cloud discoveries.\n\nNotice that this should give a variety of errors or use attached update set, which has dummy patterns that fail in different use cases.\n\n2. Look at the Discovery log.\n\n Notice that 'Failed Exploring CI Pattern' occurs for discoveries that actually brought data.\n\n
\n\nDiscovery\n\n PRB1919668\n\n [KB2588245](https://hi.service-now.com/kb_view.do?sysparm_article=KB2588245)\n\n\n\nThere's an error during a new certificate request creation for letsencrypt\n\n\n\nDiscovery's 'Discovery - Update status started count' business rule runs for ecc\\_queue ouput inserts that aren't actually from Discovery. This causes an error.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1925275\n\n\n\nInconsistent behavior in Discovery's status **Started** and **Completed** counts and **State** fields\n\n\n\nWhen the user runs quick Discovery, the Discovery status' **State** is either stuck in 'Active' or 'Starting' states. The **Started** or **Completed** counters stay on count 0 and there is no progress despite successful Discovery.\n\n\n\n \n\n
\n\nDiscovery\n\n PRB1927941\n\n [KB2434137](https://hi.service-now.com/kb_view.do?sysparm_article=KB2434137)\n\n\n\nDiscovery patterns failed prematurely, causing Discovery failure\n\n\n\nAn example is during 'Windows OS - Server' pattern Discovery running the Cluster pattern library throws consecutive errors, which should be expected, but the pattern engine failed the pattern instead.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1930200\n\n [KB2474013](https://hi.service-now.com/kb_view.do?sysparm_article=KB2474013)\n\n\n\nThe 'Protected Tables' plugin blocks DiscoverySensorJob logging and causes warnings about syslog inserts from ProtectedTableAccessHandler instead\n\n\n\nWhen the 'Protected Tables' Plugin is active, which is recommended, the source= DiscoverySensorJob GlideRecord inserts made directly to the syslog table by Discovery's 'DiscoverySensorJob' script include are blocked, and flood the syslog table with logs from source=ProtectedTableAccessHandler instead.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery\n\n PRB1933785\n\n\n\nA Cloud Discovery schedule incorrectly maps all related service accounts even when the 'Discover all Related accounts' toggle is unchecked\n\n\n\nWhen creating a Cloud Discovery schedule for a project and unchecking the 'Discover all Related accounts listed below' toggle, the schedule still maps to all service accounts under that folder level. This behavior is intermittent and has been reproduced on multiple environments. The UI script logic doesn't correctly handle timing between setAllSubAccSelected and getSubAccountsOfMasterAccount. As a result, subAccountsList is reset incorrectly, leading to unintended account mappings.\n\n\n\n \n\n
\n\nDiscovery\n\n PRB1953520\n\n [KB2718488](https://hi.service-now.com/kb_view.do?sysparm_article=KB2718488)\n\n\n\necc\\_queue input records are stuck in IP jail, causing status cancellation\n\n\n\nIPs are placed in a jail if it is suspected that multiple IPs on a schedule belong to the same device. IPs are supposed to be released from jail when the Discovery of the device is complete. When this occurs, the IPs are never released from jail.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDiscovery Probes and Sensors\n\n PRB1960340\n\n [KB2611107](https://hi.service-now.com/kb_view.do?sysparm_article=KB2611107)\n\n\n\nDiscovery's MID Server script files for Application Dependency Mapping are deleted during clones\n\n\n\nThe MID Server script file \\(ecc\\_agent\\_script\\_file\\) records have attachments. These attachments may go missing after the instance is cloned, breaking Discovery probes. To retain the attachments of base instance code-related records in clones, the table\\_name in the sys\\_attachment table must be prefixed with ZZ\\_YY. Discovery's names don't have that prefix, so the attachments may not be copied depending on the preserver/exclude settings for the clone.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nDocument Intelligence Unified Backend\n\n PRB1876011\n\n\n\nA conversation hangs after a topic is selected\n\n\n\nIn the syslogs related to DocIntel, scheduled job errors occur.\n\n\n\n1. Navigate to the Employee Service Center.\n2. Enter the prompt, 'I need to borrow a loaner laptop for work by tomorrow'.\n\n Notice that the topic will be selected, and 'Starting 'Loaner Laptop'...' is displayed, but then gets stuck.\n\n
\n\nDocument Management Services\n\n PRB1920126\n\n\n\n'Export to PDF' for a scheduled report doesn't export in the proper alignment\n\n\n\n \n\n\n\n \n\n
\n\nDocument Viewer\n\n PRB1947203\n\n\n\nAfter upgrading to Yokohama, there's an issue during the generation of a PDF file for a custom audit process using the PDFGenerationAPI library\n\n\n\nThe URL of an image or some function of the style of the HTML text used as the basis for the PDF file isn't converted or supported.\n\n\n\n1. Take the **Corporate FSQ Audit engagement** field \\(engagement\\_type\\) with the status \\(state\\) as 'Follow Up' \\(5\\).\n2. Verify that the **Report** field \\(kb\\_article\\) is populated.\n3. Verify that the **Audit Report State** field \\(u\\_audit\\_report\\_state\\) is 'Final Report Delivery' \\(final\\_review\\).\n4. Select the **Preview Audit Report** UI action that appears.\n\n An attachment should automatically be generated and be attached to the engagement in question, but nothing happens.\n\n
\n\nDynamic Translation for Agent Chat\n\n PRB1942231\n\n\n\nThe 'agent\\_translated\\_msg' column is overwritten with an empty value when the agent is in English and the chat requester is non-English\n\n\n\nAn issue has been identified and introduced in Yokohama that impacts Dynamic Translation for Agent Chat \\(DTAC\\). When an agent is using English and the chat requester is using a non-English language, the 'agent\\_translated\\_msg' column in the database is overwritten with an empty value.\n\n\n\n \n\n
\n\nEmail Notifications\n\n PRB1898761\n\n\n\nEmail Client has a rendering issue in Next Experience due to '--now-accordion \\_divider--color'\n\n\n\nThe issue doesn't happen in UI 16 or in Next Experience without Frame. The issue only happens in Next Experience with Frame.\n\n\n\n1. Provision an instance with sn\\_csm\\_gen\\_ai installed.\n2. Set the email recommendation skill to active.\n3. Set the system property 'glide.ui.load\\_ seismic\\_email\\_client' == true1.\n4. Navigate to an instance.\n5. Switch to Next Experience via personal settings.\n6. Navigate to any incident record.\n7. Select the 3 dots menu on the form header menu.\n8. Select **Email**.\n\n Expected behavior: The pop-up Email Client window should be rendered correctly.\n\n Actual behavior: The pop-up Email Client window is missing some CSS resources.\n\n
\n\nEmail Notifications\n\n PRB1930940\n\n [KB2465116](https://hi.service-now.com/kb_view.do?sysparm_article=KB2465116)\n\n\n\nEmail parts are deleted when moving to a draft in workspace\n\n\n\nEmail issues are observed in the workspace. After copying and pasting the information, it's deleted.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nEmail Notifications\n\n PRB1942395\n\n\n\nThe cursor moves to the end of an input field when the CPU throttling is 4\\* slower and 6\\* slower\n\n\n\n \n\n\n\n1. Log in as an admin user.\n2. Navigate to CSM Workspace.\n3. Open a case record.\n4. Navigate to **Compose email**.\n5. Change CPU throttling in the 'Network' tab to 4\\*slower/6\\*slower.\n6. Type continuously.\n\n Expected behavior: Drafting an email shouldn't encounter unexpected cursor placement to the end.\n\n Actual behavior: The cursor jumps to the end while typing.\n\n
\n\nEmail Notifications\n\n PRB1950667\n\n [KB2572580](https://hi.service-now.com/kb_view.do?sysparm_article=KB2572580)\n\n\n\nThe **Apply** button isn't found in the **Apply Email Templates** icon in CSM Workspace\n\n\n\nWhen the compose email is used and the 'Apply Email Template' icon is selected in a case record, the **Apply** button isn't visible for email templates that contain a large body.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nEmail Notifications\n\n PRB1951516\n\n\n\nWhen using email client, drag and drop functionality isn't including an attachment on sending\n\n\n\nIn the current UI16 email client, users can add attachments using the **paper-clip** icon or by dragging and dropping files into the email body. However, drag-and-drop doesn't work outside the email body because a background field was not properly defined, which causes this limitation.\n\n\n\n1. Log in to a Zurich instance.\n2. Navigate to the incident.list.\n3. Open Email Client.\n4. Drag and drop an attachment.\n\n When an email is sent, notice that the attachment isn't included. When users manually add the attachment, it's being added in to the email and is being sent.\n\n
\n\nEmail Notifications\n\n PRB1952527\n\n [KB2743221](https://hi.service-now.com/kb_view.do?sysparm_article=KB2743221)\n\n\n\nAn email template isn't applied when users select **Apply template** in the mini/full composer\n\n\n\nThe template isn't applied.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nEmail Notifications\n\n PRB1964152\n\n\n\nEmail Client template behavior changed after upgrading to Zurich\n\n\n\nAfter upgrading to Zurich, the behavior of Email Client template selection has changed. In Xanadu and Yokohama, the system always reverted to the default template when showing the 'Email' tab again. However, in Zurich, the system keeps the last used template \\(template2\\) instead of returning to the default.\n\n\n\n1. Log in to an instance.\n2. Open Service Operations Workspace.\n3. Open an incident record from the list.\n4. Select the **Detail** tab.\n5. Select the **More** menu on the right of 'Work notes', then select **Email** \\(template1 is applied\\).\n6. Confirm that template1 is currently applied.\n7. Select the **Email Template** icon on the right-side menu.\n8. Select **template2**, then select **Apply Template**.\n9. After template2 is applied, enter an email address in the **To** field and select **Send Email**.\n10. Repeat Step 5.\n\n Expected behavior: Template1 is applied again \\(returns to the initial status\\).\n\n Actual behavior: Template2 remains applied \\(the last used template is applied\\).\n\n
\n\nEmployee Taxonomy Framework\n\n PRB1894626\n\n [KB2547515](https://hi.service-now.com/kb_view.do?sysparm_article=KB2547515)\n\n\n\nRepetitive subtopics display in a subtopic widget\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nEmployee Taxonomy Framework\n\n PRB1930747\n\n\n\nEVAM view config records are skipped in Yokohama\n\n\n\nFour EVAM view config records are skipped when upgrading to Yokohama: sys\\_ux\\_composite\\_data\\_ template\\_predicate\\_ 28f0a2ffc30320102ec1a589a840ddea, sys\\_ux\\_composite\\_data\\_ template\\_predicate\\_ 44b0a2ffc30320102ec1a589a840dd8d, sys\\_ux\\_composite\\_data\\_ template\\_predicate\\_ 5de0a2ffc30320102ec1a589a840dde5, and sys\\_ux\\_composite\\_data\\_ template\\_predicate\\_ d5a062ffc30320102ec1a589a840ddd3. This happens because the view template is changed to xxxx v2 and 'child\\_docs' is missing from custom fields.\n\n\n\nCheck the skipped records in an upgraded Yokohama base instance.\n\n
\n\nEncryption\n\n PRB1931988\n\n [KB2481838](https://hi.service-now.com/kb_view.do?sysparm_article=KB2481838)\n\n\n\nA 'Data migration' job fails when there are no context keys and EFC's in the migration\\_pending state\n\n\n\nThe job state changes to 'Error', with the following summary: 'Error creating job handler for type all\\_data\\_to\\_kmf: \\[The KMF cryptographic module to encryption context relationship table is empty. The 'Migrate Key Context to Module' job might not have been run or has failed.\\].'\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nEvent Management\n\n PRB1955277\n\n\n\nConnectedBSGraphHandler needs additional guardrails, as this is leading to out of memory errors and node restarts\n\n\n\nThe issue is happening as part of the 'Event Management - Impact Calculator for BS\\_3' job.\n\n\n\n \n\n
\n\nFlow Engine\n\n PRB1864438\n\n\n\nThe flow action 'Submit Catalog Item Request' is not working when populating the HTML type variable\n\n\n\nThe HTML variable is populated as a data pill, when it should be populated as a variable data.\n\n\n\n1. Log in to an instance.\n2. Open the catalog item '3M Privacy Filter - Lenovo X1 Carbon'.\n3. Submit it with the HTML data.\n4. Check the flow execution 'Test Html Variable Flow'.\n\nNotice that two new RITMs are created.\n\n\n Expected behavior: The variable 'HTML Variable' populates as Variable Data.\n\n Actual behavior: The variable 'HTML Variable' populates as a Data Pill.\n\n
\n\nFlow Engine\n\n PRB1879472\n\n\n\nSub flow context can't be opened after an upgrade to Yokohama\n\n\n\nThere's a deserialize error when viewing a flow context that has a static value assigned to the subflow output. The error stack can be located in the logs.\n\n\n\n \n\n
\n\nFlow Engine\n\n PRB1896563\n\n [KB2250326](https://hi.service-now.com/kb_view.do?sysparm_article=KB2250326)\n\n\n\nA stage\\_state orphan record is created after a flow is cancelled\n\n\n\nNumbers of stage\\_state records with 'column\\_renderer'=Legacy and empty **field**, **id**, **source** and **table** fields exist in the stage\\_state table.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlow Engine\n\n PRB1923566\n\n\n\nYielding to the high priority flows feature causes several issues\n\n\n\nPausing should only occur before a flow element has started executing. If a pause occurs during the execution of a flow element, then it will cause an error for the cursor location and reporting.\n\n\n\n \n\n
\n\nFlow Engine\n\n PRB1932618\n\n\n\nDuplicate updates of a field in an update record action after updating the same record in a custom action using a script\n\n\n\n \n\n\n\n \n\n
\n\nFlow Engine\n\n PRB1941990\n\n [KB2605563](https://hi.service-now.com/kb_view.do?sysparm_article=KB2605563)\n\n\n\nTrigger inputs aren't accessible after a do-until loop execution\n\n\n\nThis issue is caused by the changes to GlideFlowStages Updater.java \\(older name GlideStage UpdateListener.java\\). It's observed that, in this specific flow structure, the 'in.request\\_item' flow input isn't passed to the 'Create Catalog Task' action. Querying the sys\\_flow\\_value table, there are 2 entries for 'in.request\\_item' one for the flow input and another with the parent loop associated. As the same key 'in.request\\_item' is now associated with parent loops, it can only be accessed in the loop body \\(and for the specific iteration\\), and all other references to it out side the loop aren't available.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlow Engine\n\n PRB1958181\n\n [KB2606177](https://hi.service-now.com/kb_view.do?sysparm_article=KB2606177)\n\n\n\nFlows are intermittently not triggered after upgrading in a domain separation enabled instance\n\n\n\nAfter upgrading a domain separated instance, some flows are no longer triggered. This is because some of the flow's records are in the domain that the flow was defined in, and other records in a different domain.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlow Engine\n\n PRB1984516\n\n [KB2741852](https://hi.service-now.com/kb_view.do?sysparm_article=KB2741852)\n\n\n\nFlows with record triggers intermittently aren't triggering after a Zurich upgrade\n\n\n\nThe root cause of the issue lies in the record trigger cache preparation, which isn't thread safe. This may result in returning incomplete triggers that cause flows/playbooks not to trigger.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1821536\n\n [KB2144795](https://hi.service-now.com/kb_view.do?sysparm_article=KB2144795)\n\n\n\nInline script dot-walk doesn't work as expected\n\n\n\nThe issue happens when there are three or more dot-walks, the engine major version is two, and com.glide. hub.flow.inline\\_ script.dotwalk. enabled is set to true.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1921408\n\n [KB2659810](https://hi.service-now.com/kb_view.do?sysparm_article=KB2659810)\n\n\n\nThe sys\\_hub\\_flow\\_version record of a flow is not captured in the update set when updating the flow\n\n\n\nThe user must manually capture the sys\\_hub\\_flow\\_version record in update set to avoid a preview error.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1923234\n\n\n\nAdd the FDCollection complex object after all applications are installed\n\n\n\n \n\n\n\n \n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1931588\n\n\n\nOpening a flow and closing it without editing updates the **Updated** and **Updated by** fields\n\n\n\n \n\n\n\n \n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1938123\n\n\n\nFlows using base instance actions related to the plugin 'Customer Service Spoke' fail after upgrading to Yokohama\n\n\n\nThe flows in question are base instance actions related to 'Customer Service Spoke': 'Add Work Note to Task' and 'Add Comment To Task'.\n\n\n\n \n\n
\n\nFlows \\(Family Channel\\)\n\n PRB1952639\n\n\n\nThere's an error in the logs: 'com.glide.script.RhinoEcmaError: \"FlowRecommendationsSkillCheck\" is not defined'\n\n\n\nThere are 464 error logs in the last 15 minutes. This makes it difficult to check the debug logs. Nothing is being executed on the instance.\n\n\n\n \n\n
\n\nForm Templates\n\n PRB1968784\n\n\n\nUsers aren't able to update certain fields using templates in Service Operations Workspace \\(SOW\\)\n\n\n\nWhen a field depends on another field, if a user is attempting to clear the dependent field value via a template while the parent field is populated, the system validates if the new value exists within the parent field's reference. The validation fails, preventing the field from being cleared.\n\n\n\n1. Navigate to an instance.\n2. Impersonate any users who have roles to control incident along with SOW and to use a template.\n3. Navigate to **SOW** > **incident record** to apply a template.\n4. Fill out values in an assignment group and 'assigned to' columns.\n5. Select the **template** icon in the far right panel and choose it to update a field for instance 'Assigned to'.\n\n Expected behavior: A warning message shouldn't appear. And the **Assigned to** field should be updated.\n\n Actual behavior: A warning 'unable to update field Assigned to' message appears and users are unable to update the **Assigned to** field.\n\n
\n\nGlideAggregate API\n\n PRB1674129\n\n\n\nPagination for grouped lists in workspaces is not working correctly\n\n\n\nThis pagination issue hides the last rows of the list in Agent Workspace.\n\n\n\n1. Open an instance.\n2. Navigate to Incident.LIST.\n3. GroupBy assignment group.\n\nNotice that there are 23 rows in the list.\n\n4. Navigate to Agent workspace.\n5. Open All incidents.\n6. GroupBy assignment group.\n\n Notice that the pagination shows 6 rows when there are actually more than 6 rows. Additionally, the last 3 rows that are seen in native UI are not present in Agent workspace.\n\n
\n\nGranular Delegation\n\n PRB1914000\n\n\n\nAdhoc Granular Delegation intermittently doesn't work\n\n\n\nThis issue only happens when the delegation rule condition is added on the child table of the **task** field, which is added on the delegation rule.\n\n\n\n1. Activate the Granular Delegation plugin.\n2. Create the delegation rule table on the change\\_request table.\n3. Choose the second step table.\n4. Set the filter to active = true.\n5. Select the **Assignments** and **Approvals** check boxes.\n6. Log in as an admin.\n7. Navigate to **All** > **change\\_request.list**.\n8. Create a new change request \\(Normal\\) with the Assignment group as 'Hardware'.\n9. Assign it to a user.\n10. Change the state of the change request to 'Assess'.\n11. Impersonate the user Abraham Lincoln.\n12. Navigate to **All** > **Employee Center**.\n13. Select **My Tasks**.\n14. In the Open Tasks list, find the newly created change request.\n15. Select **Delegate this task**.\n16. Delegate it to the user Abel Tuter, with the start date as yesterday and the end date as tomorrow.\n\n Expected behavior: The UI shows the task as delegated to Abel Tuter with an option to edit.\n\n Actual behavior: The user sees a 'Success', but the UI still shows the 'Delegate this task' link.\n\n
\n\nHistory Set\n\n PRB1910202\n\n\n\nAdmin overrides are enabled in the ACL, but the admin user was denied access to History > List view\n\n\n\nAfter the Yokohama upgrade, or when upgrading between patches, users with the 'admin' role are no longer able to access History > List view of all the tables/records. Prior to upgrading, the admin user was able to access the 'History List' menu as expected, and should have access to the 'History List' by default. This issue occurs even when the system property 'glide.security. admin.override. accessterm' is set to 'true'. Admin users can verify that they were blocked by the ACL with the 'Analyze Permissions' tool in the test instance. Only users who having the 'sn\\_hr\\_core.admin' role are able to see the History > List menu.\n\n\n\n1. Open a Yokohama instance.\n2. Impersonate System Administrator user.\n3. Open an incident record.\n4. Select the 'form contact' menu.\n\n Expected behavior: The admin user accesses the History List menu by default.\n\n Actual behavior: History > List is not visible to the impersonated admin user.\n\n
\n\nHorizon Alert Component\n\n PRB1912990\n\n\n\nNow-alert doesn't render HTML that is not wrapped in an outer tag\n\n\n\n \n\n\n\n1. Create a now-alert component.\n2. Use the HTML and partial markup.\n\n Notice that the HTML is not rendered.\n\n
\n\nHorizon Component Library\n\n PRB1929229\n\n [KB2515183](https://hi.service-now.com/kb_view.do?sysparm_article=KB2515183)\n\n\n\nA theme changes when opening an HR Case record page\n\n\n\nThe user's theme preference changes automatically when creating/opening an HR Case form from the workspace.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nHR Service Delivery\n\n PRB1920738\n\n [KB2525534](https://hi.service-now.com/kb_view.do?sysparm_article=KB2525534)\n\n\n\nHR Case description \\(rich\\_description\\) doesn't copy over data, and the rich description is left empty\n\n\n\n**Rich Description** appears as null in the 'List' view but displays correctly in the case record. The reverse works as expected— when updating the **rich\\_description** field in the HR case form, the value will appear in the **rich\\_description** field in the list view.\n\n\n\n1. Log in to the instance.\n2. Create an HR case.\n3. Navigate to **sn\\_hr\\_core\\_case.LIST**.\n4. Open the newly created case.\n5. Select the **Hamburger** icon.\n6. Configure the form layout.\n7. Add the **Description** field.\n8. Save the changes.\n9. Return to the HR case form.\n10. Enter a message in the **Description** field, but don't enter anything in the **rich\\_description** field.\n11. Save the changes.\n\nObserve that the same value is automatically updated in the **rich\\_description** field due to a business rule that syncs values between the two fields.\n\n12. Open the list view.\n13. Add the Description and rich\\_description columns.\n\n Notice that the **rich\\_description** field doesn't contain a value.\n\n
\n\nHR Service Delivery\n\n PRB1931448\n\n [KB2503620](https://hi.service-now.com/kb_view.do?sysparm_article=KB2503620)\n\n\n\nThe **Suspend Reason** field isn't present on a form by default\n\n\n\nThis causes a discrepancy in populating the suspend reason in the work notes in an HR case.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nHR Service Delivery\n\n PRB1943958\n\n [KB2570781](https://hi.service-now.com/kb_view.do?sysparm_article=KB2570781)\n\n\n\nThere's a 'You do not have permission to read the created record' error when creating an HR Case\n\n\n\nA race condition in the UI happens when a form is submitted before the GUID is created and an empty sys\\_is is passed. The server-side code was not handling this. It happens intermittently.\n\n\n\n1. Open **Create New** via Agent Workspace.\n2. Select the **Benefits Management** HR service.\n3. Select **Create case**.\n\n Notice the error, but the case gets created in backend with an empty case number.\n\n
\n\nHTML Field Type Editor\n\n PRB1950682\n\n\n\nThe character count in HTML box is half cut in Zurich\n\n\n\nAfter the Zurich upgrade, the character count/words in the HTML editor are cut in half. In Yokohama, the character count/words are seen clearly.\n\n\n\n1. Navigate to kb\\_knowledge.LIST.\n2. Open any record that is in the draft state.\n3. Check the **description** field HTML editor.\n\n Observe that the character count isn't clearly visible.\n\n
\n\nHTML Field Type Editor\n\n PRB1953216\n\n\n\nURL links added in HTML fields no longer change color when the **Toggle Theme** button on the TinyMCE editor is selected\n\n\n\nThe issue is observed in Zurich. It was tested in both light and dark themes, Next Experience, and coral.\n\n\n\n1. In a Zurich instance, navigate to kb\\_knowledge.do.\n2. Copy and paste a URL link into the **Article body** HTML field.\n3. Select the **Toggle theme** button.\n\nObserve no color changes.\n\n4. Repeat the same steps in a Yokohama instance.\n\n Observe the color of the URL link.\n\n
\n\nInstance Data Replication \\(IDR\\)\n\n PRB1897813\n\n [KB2287977](https://hi.service-now.com/kb_view.do?sysparm_article=KB2287977)\n\n\n\nShared key recovery doesn't happen when attempting to seed\n\n\n\nIncorrect symmetric keys are observed in mostly incorrect post clone scenarios. This breaks the entire IDR and no data or metadata can be decrypted successfully.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nIntegration Authentication\n\n PRB1960124\n\n\n\nVerbose JWT logs use opaque tokens when AuthLog is enabled\n\n\n\n \n\n\n\n \n\n
\n\nIntegration Hub\n\n PRB1905216\n\n [KB2601538](https://hi.service-now.com/kb_view.do?sysparm_article=KB2601538)\n\n\n\nBase instance script includes have duplicate names\n\n\n\nThe following script includes have duplicates: RestStepMultipartUtil \\(Package - ServiceNow IntegrationHub Action Step - REST\\), and RestStepFormUrlEncodedUtil \\(\\(Package - ServiceNow IntegrationHub Action Step - REST\\)\\).\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nInternationalization Features\n\n PRB1892286\n\n [KB2277705](https://hi.service-now.com/kb_view.do?sysparm_article=KB2277705)\n\n\n\nA non-admin user can't change a dashboard name by specific steps when the system language is set to Japanese\n\n\n\nThe dashboard name should be updated correctly and reflected in both the primary record and its translated fields, as it is in the Washington and Xanadu versions. In the Yokohama version, the update to the dashboard name fails silently when the Japanese language is enabled and the sys\\_translated record exists.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nInternationalization Features\n\n PRB1911538\n\n [KB2266945](https://hi.service-now.com/kb_view.do?sysparm_article=KB2266945)\n\n\n\nThe 'Translated Text Synchronize' business rule has an infinite loop against v\\_plugin\n\n\n\nThe 'Translated Text Synchronize' business rule goes in an infinite loop. The virtual table v\\_plugin \\(or any virtual table\\) can refresh \\(delete and insert of records\\) the table upon query. Since v\\_plugin has translated fields, glideRecord insert tries to insert into the sys\\_translated\\_text table, which runs the 'Translated Text Synchronize' business rule. This business rule tries to query the owner table i.e., v\\_plugin again, which can trigger the refresh again and this goes on in an infinite loop. This is causing performance impact against many instances.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nInternationalization Features\n\n PRB1912273\n\n\n\nAfter a Yokohama upgrade, catalog admins can't create sys\\_translated records\n\n\n\nSince the upgrade to Yokohama, it's no longer possible for catalog\\_admin users to create new records in table \\[sys\\_translated\\], only update existing ones.\n\n\n\n1. Provision a Yokohama base instance with a language plugin installed.\n2. Create a testuser with the role catalog\\_admin to access the catalog items and their variable sets and variables \\(but not the sys\\_translated table directly\\).\n3. As sys\\_admin, create two variables for any catalog item.\n4. Add a translation for one of the two variables.\n5. Switch to testuser.\n6. Open the catalog item.\n7. Change the preferred language to the one associated with the plugin \\(make sure that the translation exists\\).\n8. Change the English value to a translation for the variable that wasn't translated yet.\n9. As sys\\_admin, check on the sys\\_translated table directly.\n\nObserve that the change is instantly reverted after trying to save it and isn't saved.\n\n10. As testuster, adjust the existing translation of the variable question text for the translation that already exists.\n\n Observe that the adjustment is saved correctly and can be found in the sys\\_translated table, with 'updated' and 'updated by' correctly updated to the testuser.\n\n
\n\nJVM at Scale\n\n PRB1938155\n\n [KB2532115](https://hi.service-now.com/kb_view.do?sysparm_article=KB2532115)\n\n\n\nglide.memory.watcher is too aggressive after a Zurich upgrade\n\n\n\nChange the memory watcher to use old gen usage percentage over the whole heap usage percentage kicks in remediator logic early.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nKey Management Framework \\(KMF\\)\n\n PRB1906571\n\n\n\nPassword2 system properties return an encrypted value after a node restart for on-prem instances\n\n\n\nIn on-premises environments, database \\(DB\\) properties aren't being correctly decrypted and remain encrypted in memory.\n\n\n\n \n\n
\n\nKey Management Framework \\(KMF\\)\n\n PRB1913708\n\n\n\nThe KMF 'Customer Action' page no longer displays the latest certificate vulnerability due to a missing **experience\\_properties** field\n\n\n\nThe KMF has a 'Customer Action' page with a custom script that uses the **experience\\_properties** field. This field is not populated in Zurich, which causes the feature to break.\n\n\n\n \n\n
\n\nKey Management Framework \\(KMF\\)\n\n PRB1944097\n\n [KB2654904](https://hi.service-now.com/kb_view.do?sysparm_article=KB2654904)\n\n\n\nUsers are unable to upload push certificates into the sys\\_certificate table\n\n\n\nAn error is thrown.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nKnowledge Management\n\n PRB1922665\n\n\n\nThe source numbers in Q&A responses should be unique\n\n\n\nIn some situations, the numbers from the Now Assist synthesized answers can display '0' for all the citations, or sometimes use the same number for different references.\n\n\n\n \n\n
\n\nKnowledge Management\n\n PRB1973365\n\n [KB2733684](https://hi.service-now.com/kb_view.do?sysparm_article=KB2733684)\n\n\n\nThe 'Article Template Selector' page is not visible in UI16 in master\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nLDAP integration\n\n PRB1931311\n\n\n\nRemoving demo data removes the LDAP record producer\n\n\n\nRemoving demo data from an instance removes the LDAP Server record producer as well.\n\n\n\n \n\n
\n\nList Administration\n\n PRB1353818\n\n [KB1700738](https://hi.service-now.com/kb_view.do?sysparm_article=KB1700738)\n\n\n\nThe **Dependent Choice** field can display different labels in a list row vs form when two dependent choices have the same value\n\n\n\nOn the list view of a record, a particular field displays one value incorrectly, but another correct value when looking at the records form or 'showXML'. This occurs when the dictionary record of the field uses choices and field dependencies, and when there are two choice records for the field that have the same 'value' \\(not label\\). When they have the same value but different labels, the label shown in the list view defaults to whatever dependent field value is first in alphabetical order with the same value.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nList Administration\n\n PRB1883306\n\n\n\nIn Service Operation Workspace \\(SOW\\), when updating the due date from the list view, the date/time is removed\n\n\n\nWhen the user changes the system property 'glide.sys.date\\_format' from base to 'dd-MM-yyyy', the field is cleared out when they attempt to change the date. This issue was observed in Yokohama.\n\n\n\n1. Access a Yokohama base instance.\n2. Navigate to **SOW**.\n3. Navigate to **List menu** > **Requests** > **Open Items**.\n4. In the list view for the Requested Item, add the column 'Due Date'.\n5. Change the date/time and apply it.\n\nNotice that the date/time should update as expected.\n\n6. Open the system property 'glide.sys.date\\_format'.\n7. Change the value to 'dd-MM-yyyy'.\n8. Save the record.\n9. Return back to the RITM with the updated due date.\n10. Change the date/time to a future date and apply it.\n\n The value for the date/time is removed from the list view and on the form level.\n\n
\n\nList Administration\n\n PRB1917110\n\n\n\nIn Yokohama, the fixed filter condition doesn't calculate the sum in list view\n\n\n\nThe total value calculation doesn't account for the fixed filter condition defined in the module.\n\n\n\n1. Enable the calculated list configuration for a decimal-type field.\n 1. Select and hold \\(or right-click\\) the column header in the list view. For example, Sunday in the time\\_card table.\n 2. Select **Total Value**.\n2. Navigate to the sys\\_app\\_module table.\n3. Create a module with a fixed filter condition using the URL from arguments. For example, time\\_card\\_ list.do? sysparm\\_fixed\\_query =user=javascript: gs.getUserID\\(\\).\n4. Impersonate any user.\n5. Open the time\\_card list view via the module.\n6. Check the sum value displayed for the configured decimal field.\n7. Manually apply the same filter condition using the list filter.\n\n Observe that the total value calculation does not account for the fixed filter condition defined in the module. This behavior works correctly in the Xanadu instance.\n\n
\n\nList Administration\n\n PRB1918529\n\n [KB2669196](https://hi.service-now.com/kb_view.do?sysparm_article=KB2669196)\n\n\n\n**Export** doesn't contain current view data\n\n\n\nThe **export** functionality doesn't apply the fixed filter configured in the list UI Builder's 'Fixed Filter' property. When exporting data, the exported file includes all records instead of reflecting the current view filter. This occurs when the fixed filter is configured in the 'Fixed Filter' property, as the **export** button ignores this configuration and only applies optional filters. The issue is reproducible in workspaces using the record-list-connected component \\(NRLC\\), where the fixed filter is not respected during export.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nList Administration\n\n PRB1932331\n\n\n\nWord wrap doesn't work for NRLC list\n\n\n\nContent in the **Short Description** field does not break into new lines when line breaks are added.\n\n\n\n \n\n
\n\nList Administration\n\n PRB1932703\n\n [KB2543882](https://hi.service-now.com/kb_view.do?sysparm_article=KB2543882)\n\n\n\nDisplay values aren't showing for reference fields within the 'List' component\n\n\n\nWhen including a table on the 'List' component that contains reference fields, it's showing empty. Where as in platform, it shows a value.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nList Administration\n\n PRB1934797\n\n\n\nThere's an issue configuring the Platform Analytics Scheduled Exports Library list\n\n\n\nThe **Time** field isn't working as intended when added to the list view.\n\n\n\n1. On any Zurich instance, navigate to **PA** > **Library** > **Scheduled export**.\n2. Try to add **Time** field.\n\n Observe the error.\n\n
\n\nList Administration\n\n PRB1944139\n\n\n\nUptake allowExtended fields property on the lists side for the sn-field-select component\n\n\n\nTracking the changes for PRB1935534.\n\n\n\n1. Create a system property 'glide.ui.list.allow\\_extended\\_fields'.\n2. Set it to 'true'.\n3. Create a UI Builder page with a list component configured.\n4. Set the table property 'task'.\n5. Open the runtime page.\n6. Select the **Personalize columns** button in the header.\n\n Expected behavior: The fields from all tables extending from the task are displayed.\n\n Actual behavior: Only fields from the task table are displayed.\n\n
\n\nList Administration\n\n PRB1946446\n\n [KB2601161](https://hi.service-now.com/kb_view.do?sysparm_article=KB2601161)\n\n\n\nFiltering issues on a **Date** field in workspace\n\n\n\nAfter selecting a date, the filter options on the **Date** field in workspace are updated to an invalid date.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nList Filters\n\n PRB1967959\n\n\n\nUnable to filter the **Tags** field in the presentation list from CSM/FSM Configurable workspace\n\n\n\nWhen the user selects on the tag that has been added, a modal does not populate and the user is unable to select **View records with this tag**. Instead, the 'tags' column cannot be filtered.\n\n\n\n1. Access the CSM/FSM Configurable Workspace.\n\nNotice that the variable with sys\\_id '0c69dae8cc842210f87799583e1668b2' is loaded to the workspace \\(order = '-10'\\).\n\n2. Access the list of any table.\n3. Use the condition builder to add the **Tags** field as a condition.\n\nNotice that the **Tags** field is not listed for selection.\n\n4. Add the 'tags' column to the list view.\n5. Select on the added tag.\n\n Expected behavior: A modal is populated and the user can select **View records with this tag** to find matching records.\n\n Actual behavior: Nothing happens, and it says the 'tags' column can't be filtered.\n\n
\n\nMemory: Heap Space\n\n PRB1636231\n\n\n\nMemory is exhausted by the archiver job 'Consumer' due to syslog records stored in the memory, and syslog\\_awa isn't configured as a rotated table\n\n\n\nMemory is exhausted by the archiver job 'Consumer' reparenting records from the syslog table due to a problem observed when syslog\\_awa, which is a child table of syslog, is created without table rotation. The archiver job reparents records for the archive rules it triggers for, and reparents a table that's not rotated. When syslog\\_awa isn't configured as a rotated table, the reparenting process executes on it and its parent table syslog. Query to syslog shards are then observed, and memory is consumed as the records on these shards are stored into memory. Due to the size of it, it causes memory to become depleted. When the archiver job is running, the localhost logs have a large query to a syslog shard where the function reparentDocumentIDRecords is running.\n\n\n\n \n\n
\n\nMetricBase\n\n PRB1738054\n\n\n\nThe MetricBase Connectivity helper script for the MB Health Dashboard can construct an incorrect URL for a request for XML stats\n\n\n\nIn this script, it gets the hostname through a Glide property. If the host is null, it defaults to localhost:8080, but not all Glide instances run on 8080. This script runs every 10 minutes, so it can clutter the logs with errors.\n\n\n\n \n\n
\n\nMetricBase\n\n PRB1913485\n\n\n\nClotho system series should be inserted into the v\\_clotho\\_series table using a global scope rather than null scope\n\n\n\nThe 'Application' column for v\\_clotho\\_series metrics should have a global scope.\n\n\n\n1. Navigate to the sys\\_metric table.\n2. Filter for records on tablename v\\_clotho\\_series.\n3. Update the table list view in the UI by selecting the **Gear** icon to show the 'Application' column.\n\n Notice that the 'Application' column for all v\\_clotho\\_series metrics should have a global scope.\n\n
\n\nMID Server\n\n PRB1504483\n\n [KB0964389](https://hi.service-now.com/kb_view.do?sysparm_article=KB0964389)\n\n\n\nFile-based Discovery on a Windows host might fail with 'AuthorizationManager check failed' due to hard coded network path \\\\\\\\127.0.0.1\n\n\n\nWhen running a file-based Discovery on a Windows host, the following error may occur in the Discovery log: ​'Error: & : AuthorizationManager check failed.' When running the PowerShell script, PowerShell believes that the script is coming from the internet since the path to the file is a network path that starts with an ip\\_address, resulting in the 'AuthorizationManager check failed' error.\n\n\n\n1. Activate the 'File Based Discovery' plugin.\n2. Run it on a Windows host with a certain security policy.\n\n Observe the returned error.\n\n
\n\nMID Server\n\n PRB1863551\n\n [KB1972022](https://hi.service-now.com/kb_view.do?sysparm_article=KB1972022)\n\n\n\nMid Web Server/ACC API Key can't be viewed on instances provisioned in 2017 or earlier without creating a Module Access policy\n\n\n\nOlder instances can use a different KMF module to encrypt the **password2** field used to store the API key due to a change of packaging that occurred in 2017 on the base table, discovery\\_credentials. On these instances, the **View API key** UI action on mid\\_webserver\\_api\\_key\\_credentials returns encrypted data unless the customer configures a Module Access policy manually.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nMID Server\n\n PRB1892912\n\n [KB2763600](https://hi.service-now.com/kb_view.do?sysparm_article=KB2763600)\n\n\n\nMID tries to download signatures for synced file attachments when code signing is turned off\n\n\n\nDuring file sync when code signing is off, the MID still attempts to fetch the attachment's signature along with the attachment. When the record signature doesn't exist, an error message beginning with 'Unable to find the signature with the sys id' appears in the Glide system logs.\n\n\n\n1. Ensure code signing isn't enabled on the Glide instance.\n2. Ensure that there is an attachment record that is downloaded by MID file sync but does not have a signature record in the sn\\_kmf\\_record\\_signature table \\(for example, a MIB\\).\n3. Start the MID.\n\n Notice an error message in the Glide system logs.\n\n
\n\nMID Server\n\n PRB1898139\n\n [KB2398708](https://hi.service-now.com/kb_view.do?sysparm_article=KB2398708)\n\n\n\nThe MID Server doesn't start due to a parenthesis in the home folder's path, leaving the MID Server down after upgrades\n\n\n\nIf there's a parenthesis in the MID server path, the upgrade from the Yokohama version fails. This problem is specific to the Set-FolderPermissions.ps1 script.\n\n\n\n1. Create a MID server with a parenthesis in the path.\n2. Run start.bat.\n\n Notice that it fails with this line: '\\\\ was unexpected at this time.' The upgrade log also includes a 'was unexpected at this time' syntax error specific to the Set-FolderPermissions.ps1 path.\n\n
\n\nMID Server\n\n PRB1912171\n\n [KB2266697](https://hi.service-now.com/kb_view.do?sysparm_article=KB2266697)\n\n\n\nYokohama MID Server upgrades do not upgrade all jar files in lib\n\n\n\nYokohama MID Server upgrades don't upgrade all jar files in lib, causing NoClassDefFoundError for various classes, and MID Server to go down.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nMID Server\n\n PRB1916650\n\n [KB2421892](https://hi.service-now.com/kb_view.do?sysparm_article=KB2421892)\n\n\n\nPatterns on agent commands are randomly failing with allow list errors\n\n\n\nCollecting MSSQL DB details using ACC Discovery fails to fetch DB details with an error message. The exception occurred when executing a command on Agent. The error occurs when processing the adhoc check request: 'command failed due to allow list exclusion: check command denied by the agent allow list. Context: Asset allow list empty, using agent config file allow list.'\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nMID Server\n\n PRB1923497\n\n\n\nA deadlock occurred due to two threads\n\n\n\nThe issue is caused by a conflict between two internal processes that manage and refresh OAuth credentials and MID Server connections. The platform periodically checks and refreshes expired OAuth tokens using a scheduled job. When this happens, the system reloads the credentials and resets all related connection data to ensure security and consistency. At the same time, if a Discovery probe or integration is trying to establish a new connection, it might attempt to access the same shared connection resources. This overlap can lead to both processes waiting for each other to finish, resulting in a temporary deadlock where neither process can proceed.\n\n\n\n \n\n
\n\nMID Server\n\n PRB1969766\n\n [KB2664275](https://hi.service-now.com/kb_view.do?sysparm_article=KB2664275)\n\n\n\nMissing MIDLogFileHandler MID Server properties cause MID servers to go into an infinite loop of restarting during start up\n\n\n\nMID Servers repeatedly come up and then go back down for a few seconds before the MID Server comes back up again. This loop repeats continuously if certain MID Server Properties are missing from the ecc\\_agent\\_property table on the instance.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nMobile Platform\n\n PRB1908491\n\n [KB2243641](https://hi.service-now.com/kb_view.do?sysparm_article=KB2243641)\n\n\n\nmobile-client-scripts don't take the user's date/time format into account when parsing data in V2Transform\n\n\n\nIn DateTimeFormatter.ts getUserDateTimeFormatter, it calls globalThis.userDateTimeFormat, but this is never set.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nMobile Platform\n\n PRB1931576\n\n [KB2466952](https://hi.service-now.com/kb_view.do?sysparm_article=KB2466952)\n\n\n\nOffline-mode payload generation has excessive memory retention, causing performance degradation due to an SG offline document job\n\n\n\nThe Yokohama release introduced major changes to the way in which mobile offline payloads are generated, most notably embedded forms are now transformed into redirected forms. This removes the embedded forms from list screen documents and turns them into separate documents. With that change resulted in an increase in the number of documents that are processed during offline payload generation. This number can spike to as large as twice or three times as many documents processed compared to previous releases. As such, this results in an excessive number of GlideRecord instances being retained in memory. This has been seen to cause memory issues, node restarts, and severe performance degradation for users.\n\n\n\n \n\n
\n\nMobile Studio\n\n PRB1974465\n\n\n\nMobile AI Builder \\(id = sn\\_maib\\) plugin oob\\_apps/now-mobile-ai-builder.properties should have mode = optional to ensure it is not an installed base instance\n\n\n\nMobile AI Builder \\(id = sn\\_maib\\) is installed as it is marked as mode = core in oob\\_apps/now-mobile-ai-builder.properties.\n\n\n\n \n\n
\n\nMulti-provider Single Sign-on \\(SSO\\)\n\n PRB1979071\n\n [KB2715489](https://hi.service-now.com/kb_view.do?sysparm_article=KB2715489)\n\n\n\nSAML SP Keystore expiration\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nNext Experience Unified Navigation\n\n PRB1908169\n\n [KB2252998](https://hi.service-now.com/kb_view.do?sysparm_article=KB2252998)\n\n\n\nAn exact match for an experience with an invalid routeConfigId doesn't navigate\n\n\n\nA new issue was found which results in Zing search results aren't opening properly within a workspace.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nNow Assist Panel\n\n PRB1867538\n\n\n\nCopy for synthesized responses \\(auto start\\) on Now Assist panel \\(NAP\\) doesn't work and copies 'undefined'\n\n\n\nWhen using the Now Assist panel \\(NAP\\) and entering 'Summarize a record', the **copy** icon on the auto-started synthesized response doesn't copy the content, and instead, 'undefined' is copied. When 'undefined' is copied instead of the content and the synthesized response isn't auto-started, there is no **copy** icon and a 'Like/dislike' displays instead.\n\n\n\n \n\n
\n\nNow Assist Panel\n\n PRB1909094\n\n\n\nThe **Show more** button isn't visible on NASS for Safari browsers\n\n\n\nWhen using the Now Assist Panel \\(NAP\\), Now Assist for Virtual Agent \\(NAVA\\), or Now Assist for Request \\(NASS\\) on Safari, the **Show more** button isn't visible after truncation, so the user is unable to see the full message. This prevents users from accessing the complete content of responses.\n\n\n\n \n\n
\n\nNow Assist Panel\n\n PRB1965617\n\n [KB2768233](https://hi.service-now.com/kb_view.do?sysparm_article=KB2768233)\n\n\n\nLegacy Now Assist Portal doesn't load upon upgrade\n\n\n\nThe Now Assist panel bubble opens when selected, but the panel doesn't fully load. The interface remains stuck in a loading state, and no content is displayed to the user.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nOAuth\n\n PRB1963296\n\n [KB2624687](https://hi.service-now.com/kb_view.do?sysparm_article=KB2624687)\n\n\n\nUsers aren't displaying in OAuth application user\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nOneExtend\n\n PRB1920515\n\n [KB2493973](https://hi.service-now.com/kb_view.do?sysparm_article=KB2493973)\n\n\n\nLLM usage domain separation application properties aren't installed by default\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nOneExtend\n\n PRB1925002\n\n\n\nAgentic Workflow's trigger sys\\_user is taking precedence over run as 'AI User'\n\n\n\nWhen trigger conditions are met, the workflow should be executed with workflow's 'Run As' user for the new incident. However, the workflow is actually executed with the trigger's sys\\_user and the execution is terminated with the error 'Access Denied'.\n\n\n\n \n\n
\n\nOneExtend\n\n PRB1944861\n\n [KB2566151](https://hi.service-now.com/kb_view.do?sysparm_article=KB2566151)\n\n\n\nAssists consumption for custom skills created in the Now Assist Skill kit\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nOneExtend\n\n PRB1963582\n\n\n\nOpening Flow Designer triggers errors in logs\n\n\n\nOpening Flow Designer triggers flow generation and flow summarization skills. However, since the skills aren't active in the customer instance, they're throwing errors in syslog table, such as 'Failed to get skill config for skillConfigId: 0472be2434131100b7b556ababf25d, capabilityId:'.\n\n\n\n1. Log in to a Zurich base instance.\n2. Open Flow Designer.\n3. Open syslogs.\n\n Observe the 'Failed to get skill\\*' messages.\n\n
\n\nPassword Reset\n\n PRB1932368\n\n\n\nMassive flood of 'sys\\_user\\_grmember.delete' and 'sys\\_user\\_grmember.insert' events cause a huge delay on platform event processing\n\n\n\nMass import or deletion of a user group membership will generate large number of 'sys\\_user\\_grmember.delete' and 'sys\\_user\\_grmember.insert' events, causing a huge delay on platform event processing.\n\n\n\n \n\n
\n\nPDF Generation\n\n PRB1829301\n\n\n\nSystem Trigger-PDFReportExportJob causes nodes to go out of memory\n\n\n\nOne user had slowness in the instance when the trigger on PDFReportExportJobs was executed. This trigger was consuming a lot of memory which forced support to turn off the execution. This was observed multiple times in the instance.\n\n\n\n \n\n
\n\nPerformance Analytics API\n\n PRB1917953\n\n [KB2703941](https://hi.service-now.com/kb_view.do?sysparm_article=KB2703941)\n\n\n\nAnalytics Center doesn't have guardrails in its NLQ Service, causing Java heap space out-of-memory errors\n\n\n\nAn NLQ with the combination of 'AC' and an empty 'table' parameter is fired, leading to excessive scans across the instance and eventually causing an out of memory error.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nPerformance Analytics Dashboards\n\n PRB1906120\n\n\n\nUser preferences \\(com.snc.par.dashboards.ui.preferences\\) are never cleared and causing out of memory errors and node restarts\n\n\n\n'WARNING \\*\\*\\* WARNING \\*\\*\\* error processing rest data broker: Exception while executing request: Java heap space...'.\n\n\n\n1. Navigate to an instance.\n2. Open the dashboard.\n3. Select **Filter** > **Assignment group**.\n4. Wait for a couple of seconds and navigate to **User Preferences**.\n\n Observe that the latest preference has large text and lot of applies to values in JSON.\n\n
\n\nPerformance Analytics\n\n PRB1964068\n\n\n\nEmpty dashboards are repeatedly duplicating from the 'Migrate Homepages' scheduled script\n\n\n\n'com.glideapp.home.deprecate\\_homepages' has been set to false. After upgrading the instance from Xanadu to Zurich, a script called 'Migrate homepages' was introduced which created duplicated empty dashboards every time it runs.\n\n\n\n \n\n
\n\nPlatform Analytics Component API\n\n PRB1907336\n\n\n\nThe 'Created By' column values truncates after 10 characters in the Data Visualization library for Platform Analytics\n\n\n\n \n\n\n\n \n\n
\n\nPlatform Analytics Component API\n\n PRB1934435\n\n\n\n'Dashboard view count' doesn't update for Core UI dashboards\n\n\n\n \n\n\n\n \n\n
\n\nPlatform Analytics Component API\n\n PRB1948336\n\n\n\nOption to turn off the 'Welcome to Platform Analytics' pop-up / modal for migrated dashboards\n\n\n\nWhen a responsive dashboard is migrated to PA dashboard, a pop-up / modal is shown to all users accessing the migrated dashboard: 'Welcome to the Platform Analytics experience'.\n\n\n\n \n\n
\n\nPlatform Analytics Component API\n\n PRB1952208\n\n\n\nThe dashboard list doesn't display and can't filter properly\n\n\n\nThe Dashboard Library on Platform Analytics \\(Zurich\\) generates an invalid query when any of the built-in filters are used and thus generate no queries due to the sys property glide.invalid\\_ query.returns\\_ no\\_rows being set to true.\n\n\n\nNavigate to **Platform Analytics** > **Dashboards**.\n\n Notice that when 'Filter active' is true, no records are displayed even when there are numerous active dashboards. Using any filters removes all records from the list.\n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1843154\n\n\n\nNot able to save a dashboard after editing\n\n\n\n \n\n\n\n \n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1890523\n\n\n\nCommitting update sets with dashboard changes doesn't clear the par\\_dashboard\\_cache\n\n\n\nAfter the user commits the update set, the dashboard changes don't show up in the new instance because the par\\_dashboard\\_cache isn't cleared.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1905382\n\n\n\nDashboard tab names do not have unique keys for translations in a sys\\_translated table\n\n\n\nCore UI dashboard tab names contain the sysId of the pa\\_tab record, and sometimes a BEL character and the string. Performance Analytics Experience dashboard tab names do not have this sysID prefix. In the Core UI dashboard, the sysID prefix enabled gives a different translation to the same string so multiple tabs can have 'New Tab 2,' but each can have different translation because real key is 'd6a290139 368b5107249 b9d86cba 1081New Tab 2'.\n\n\n\n \n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1909232\n\n\n\nPlatform Analytics dashboards can't be saved due to colliding components that have the same positions\n\n\n\nPerformance Analytics Reporting dashboard can't be saved if multiple components are colliding. An error occurs in the logs: 'DEBUG: DASHBOARD\\_SERVICE: Dashboard with sys\\_id is Dirty. Need to update DashboardsService DEBUG: DASHBOARD\\_SERVICE: Dashboard updated true DashboardsService SEVERE \\*\\*\\* ERROR \\*\\*\\* DASHBOARD\\_SERVICE: An error happened editing the layout. DashboardsResource SEVERE \\*\\*\\* ERROR \\*\\*\\* DASHBOARD\\_API: Edit API - Widget Collision WidgetCollisionException - Colliding Widgets are.'\n\n\n\n \n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1909523\n\n [KB2262722](https://hi.service-now.com/kb_view.do?sysparm_article=KB2262722)\n\n\n\nChanges in the dashboard only appear in the session language where they were made\n\n\n\nUsers are experiencing inconsistent behavior in Platform Analytics dashboards depending on the selected user language. When viewed in English, the dashboard reflects the latest updates. When switched to Italian, an outdated version displays, even after clearing the cache using cache.do.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nPlatform Analytics Dashboard API\n\n PRB1964706\n\n\n\nErrors found in a system log caused by daily automated list\n\n\n\nAfter upgrading to Zurich, system log entries show below errors every day at 08:00 related to the automatic migration of List - Simple to Analytics List.\n\n\n\n \n\n
\n\nPlatform Analytics Migration API\n\n PRB1926289\n\n\n\nA reference table isn't migrated for the reference filter\n\n\n\nAfter migration, the target for the filter is missing, and the reference table hasn't been migrated.\n\n\n\n1. Create a dashboard on CoreUI.\n2. Add the base instance interactive filter of type reference: Incident Assignment Group - Multiple.\n3. Verify the filters.\n\nNotice that on the filter record, there's also the reference table available.\n\n4. Migrate the dashboard.\n\n Notice that after migration, the target for the filter is missing, and the reference table hasn't been migrated.\n\n
\n\nPlaybook Experience Core\n\n PRB1929896\n\n\n\nThe playbook lane isn't translated to Italian\n\n\n\nThis is an issue with record generator. It can also be reproduced by going to 'Playbook Preview' and selecting the record generator for the record.\n\n\n\n1. Log in to any instance.\n2. Switch the language to Italian from the menu preference.\n3. Open **Workspaces** > **Risk workspace**.\n4. Select the **List** icon.\n5. Select **Risk assessment planning** > **Scheduled assessment**.\n6. Select **New**.\n\nObserve that the playbook lane is still coming in the English language.\n\n\n Expected behavior: The playbook lane should be translated to Italian.\n\n Actual behavior: The playbook lane isn't translated to Italian.\n\n
\n\nPlaybooks \\(Family Channel\\)\n\n PRB1934746\n\n [KB2592048](https://hi.service-now.com/kb_view.do?sysparm_article=KB2592048)\n\n\n\nPlaybooks archived in Xanadu don't work in newer releases\n\n\n\nNew fields that get added to the deserialiser need to handle the keys not existing, which, as of now, is snapshot\\_id and variant\\_id.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nPortfolio Management\n\n PRB1936553\n\n [KB2503548](https://hi.service-now.com/kb_view.do?sysparm_article=KB2503548)\n\n\n\nThe condition of the business rule 'Update Total Plan Cost In Proj Currency' evaluates to undefined when the com.snc.ppm\\_multicurrency plugin isn't installed\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nPredictive Intelligence\n\n PRB1617925\n\n\n\nAsync NLU request fails with a close connection error\n\n\n\nSome calls within a batch of NLU async calls don't reach the predictor and a connection error is reported by Glide.\n\n\n\n \n\n
\n\nPredictive Intelligence\n\n PRB1954123\n\n [KB2594708](https://hi.service-now.com/kb_view.do?sysparm_article=KB2594708)\n\n\n\nMutual TLS \\(mTLS\\) is enabled on Zurich instances, causing access issues for inbound integrations\n\n\n\nDue to the updates related to the Predictive Intelligence plugin, mutual TLS \\(mTLS\\) is enabled on user instances after a Zurich upgrade. This may result in instance access issues for inbound integrations.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nProcurement\n\n PRB1675022\n\n\n\nThe user can't allocate the rights for an Unlimited Software license through a source request\n\n\n\n \n\n\n\n1. Activate the 'SAMP Master and Procurement' plugin.\n2. Create an entitlement with **Unlimited License** checked.\n3. Create a Service Catalog request.\n4. Add the same software model to cart.\n5. Checkout the cart.\n6. In SCTASK, select **Source Request**.\n\n In the 'Source Request' page, see that 'available rights' is 0 and the **Allocate** button is turned off.\n\n
\n\nRecord Watcher\n\n PRB1894715\n\n [KB2345405](https://hi.service-now.com/kb_view.do?sysparm_article=KB2345405)\n\n\n\nChecklistItemResponder is too slow to effectively scale with normal usage of the platform, leading to the record watcher queue becoming backlogged\n\n\n\nA performance issue has been identified related to checkLitsItem responders and ACL \\(Access Control List\\) checks while creating checkListItems in Visual Task Board's cards. These issues caused delays, especially when tasks had more than 50 checklist items. This is primarily because getItemsByChecklistId\\(\\) is invoked every time a checklist item is added or a card is moved between lanes. It loops through all items under a checklist and performs individual ACL evaluations \\(read/delete access\\). These checks result in: Repeated database lookups, redundant ACL checks for the same parent checklist, and slower response times, especially when checklist items exceed 50.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nReporting\n\n PRB1910065\n\n\n\nReports with multiple datasets throw an error: 'ERROR: Cannot generate the report. JSONObject\\[''original\\_xvalue''\\] not found'\n\n\n\nThis issue was noticed when using the 'Time series' type and Gregorian Calendar per month.\n\n\n\n \n\n
\n\nResource Management\n\n PRB1941447\n\n [KB2552237](https://hi.service-now.com/kb_view.do?sysparm_article=KB2552237)\n\n\n\nThe assignment FTE falls to an incorrect value due to lack of availability adjustment to 24 hours in the monthly view of RMWS\n\n\n\nThe issue is caused by not adjusting availability to 24 hours. It should adjust availability to 24 hours and redistribute hours evenly.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nREST API Framework\n\n PRB1936861\n\n\n\n'Requested URI does not represent any resource' is logged as an error instead of a warning\n\n\n\n'Requested URI does not represent any resource' is logged as an error instead of a warning in the system Logs. Errors in the system logs represent issues that must be fixed; however, the 'Requested URI does not represent any resource' message should be displayed as a warning in the system logs because it is an error that has been handled and the user/platform can recover from.\n\n\n\n \n\n
\n\nRestricted Caller Access \\(RCA\\)\n\n PRB1967269\n\n\n\nUnable to update status of restricted caller access privileges\n\n\n\nMultiple restricted caller access entries are changed from 'Allow' to 'Requested' after the Zurich upgrade. The user has re-allowed what was possible, but some applications are private and can't be manually updated.\n\n\n\n \n\n
\n\nRoles\n\n PRB1888313\n\n\n\nTime-limited role access is assigned if a user has more than one request in the future\n\n\n\nAccess should work as expected for users with multiple time-limited user role records, with assigning and revoking working as expected.\n\n\n\n \n\n
\n\nSeismic Framework\n\n PRB1919027\n\n\n\nDocument requests end up using outstanding child prefetch promise\n\n\n\nIn certain scenarios, the Service Worker incorrectly fulfills a main page request using a pending iframe request. This occurs when the Service Worker matches the main page request to an existing pending iframe request, resulting in the main page loading the iframe's content instead of its own. This leads to incorrect rendering and potential functional issues on the main page.\n\n\n\n1. Open any UI16 page on a Next Experience enabled instance.\n2. Wait for the page to load.\n3. Reload the same page several times \\(5+\\).\n\n Expected behavior: The navigation bar and shell to show up with UI16 content all the time.\n\n Actual behavior: Only UI16 content is shown on the page. The navigation bar and shell are missing.\n\n
\n\nSeismic Framework\n\n PRB1961091\n\n\n\nThe seismic placeholders 'nowPlaceholderHeight' and 'nowPlaceholderWidth' aren't rendering components\n\n\n\nWhen both events in a starting position are visible on the screen, the templates render correctly. When the starting positions of both the events aren't visible on the screen but still they are in view port \\(gets hidden due to the section header\\), only one template renders and the other doesn't.\n\n\n\n \n\n
\n\nServer-side scripts\n\n PRB1825872\n\n\n\nES12 support in global script includes isn't working\n\n\n\n \n\n\n\n \n\n
\n\nServer-side scripts\n\n PRB1972733\n\n\n\nField translations for security integrations are failing and return a null value\n\n\n\nThe field translations aren't working. On changing the field **evaluator.with EnforcedSecurity\\(false\\)**, field translations work as expected.\n\n\n\n \n\n
\n\nService Catalog Portal Widgets\n\n PRB1939681\n\n\n\nThe 'SC Category' page doesn't display catalog items correctly if the portal doesn't have AI Search turned on\n\n\n\nThe portal is associated to many catalogs. The portal is only meant to show the categories/items that are part of the catalogs it is associated to. The URL to show the categories is constructed manually. The URL is using the sc\\_category page. Since the portal doesn't contain the catalog that has the category, it behaves strangely.\n\n\n\n \n\n
\n\nService Catalog\n\n PRB1919964\n\n [KB2532880](https://hi.service-now.com/kb_view.do?sysparm_article=KB2532880)\n\n\n\nThe Record Producer **Submit** UI action should be grayed out after being selected once\n\n\n\nOn a catalog item in service portal, the **Submit** button re-enables after the first selection.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nService Catalog Variables\n\n PRB1855812\n\n\n\nWhile changing the language from English to Norwegian, the user can't see all options under Lifecycle status 'End of life'\n\n\n\nThe getValue method on the GlideRecord that takes the column name behaves differently from the scriptable getValue on the gliderecord when the column is of type translated\\_text. It works fine for the translated\\_field types.\n\n\n\n \n\n
\n\nService Graph Connectors\n\n PRB1972771\n\n\n\nA JDBC connection test times out after a Zurich upgrade\n\n\n\nThe JDBC Connection test times out after a Zurich upgrade. The user modified the script in the client script section of the UI page in the instance, which resolved the issue. The user is also concerned about this page customization.\n\n\n\n \n\n
\n\nService Mapping\n\n PRB1710808\n\n [KB1576904](https://hi.service-now.com/kb_view.do?sysparm_article=KB1576904)\n\n\n\nIn a tag-based service, the sys\\_property svc\\_by\\_tags.install\\_status.blacklist isn't used to filter out CIs brought by traversal rules\n\n\n\nSMServiceByTagsTopologyUtils, in the logic of walking by traversal rules, should apply the filter by the CI install\\_status according to svc\\_by\\_tags.install\\_status.blacklist. There are some issues with the tag-based population invoker. One thing to make sure is to force service recalculation even when the checksum hasn't changed, for cases when the service contains retired CIs.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nService Mapping\n\n PRB1912099\n\n\n\nList CI list view doesn't allow copying the filter\n\n\n\nList CI list view used to have a visible filter of CI sys\\_ids. The list uses fixed\\_query, which doesn't allow changing or copying of the list of CI sys\\_ids.\n\n\n\n \n\n
\n\nService Portal Core Widgets\n\n PRB1953795\n\n\n\nThe **Subscribe to update** button doesn't work for non- admin users after a Zurich upgrade\n\n\n\n \n\n\n\n \n\n
\n\nService Portal\n\n PRB1886667\n\n\n\nKorean consonants and vowels are separately returned when the user types into a variable using a keyboard in a portal page\n\n\n\n \n\n\n\n \n\n
\n\nService Portal\n\n PRB1893333\n\n\n\nAfter the first login with MFA authentication, the user is redirected to the Platform UI page instead of the Portal page\n\n\n\nThe user lands on the platform page instead of the Service Portal page after MFA setup.\n\n\n\n1. Log in as a user with MFA enabled.\n\nNotice that after a successful login, the user will be redirected to setup MFA.\n\n2. Complete the MFA setup.\n\n Expected behavior: The user is expected to land back on the Service Portal page.\n\n Actual behavior: The user lands on to the platform page.\n\n
\n\nService Portal\n\n PRB1893869\n\n [KB2313113](https://hi.service-now.com/kb_view.do?sysparm_article=KB2313113)\n\n\n\nThe EC Search widget doesn't handle the overflow of text when there are more than ten navigation tabs\n\n\n\nWhen there are more than ten navigation tabs \\(sys\\_search\\_filter\\) created for the AI Search Application, the EC Search widget doesn't handle the overflow of text.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nService Portal\n\n PRB1914199\n\n\n\nPortal throws unnecessary success messages when adding an attachment\n\n\n\n \n\n\n\n \n\n
\n\nService Portal\n\n PRB1956154\n\n\n\nExtra unusable scroll bars appear on all user portals when accessed from a touchscreen-enabled laptop\n\n\n\nThis only happens when the .touch\\_scroll class is added to the body element forcefully through developer tools.\n\n\n\n1. Use a Windows laptop with a surface touch screen enabled.\n2. Log in to any instance.\n3. Open any portal.\n\n Observe the redundant scroll bar.\n\n
\n\nService Portal\n\n PRB1970979\n\n [KB2706155](https://hi.service-now.com/kb_view.do?sysparm_article=KB2706155)\n\n\n\nHelp text is misaligned in portal forms after upgrading to Zurich\n\n\n\nAfter upgrading to Zurich, the help text in portal catalog items is not aligned correctly. It is shifted to the right of the label above it.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSidebar \\(Family Release\\)\n\n PRB1928878\n\n\n\nPrivate conversations are visible to users on the sidebar\n\n\n\nThis issue occurs when impersonating a user who is in the discussion ends the impersonation, and then impersonates a user that isn't a participant in the discussion.\n\n\n\n1. Impersonate any user.\n2. Navigate to any workspace.\n3. Open an incident that is in an 'Open' state.\n4. Select **Discuss**.\n5. Enter necessary mandatory info.\n6. Add a user as a participant.\n7. End the impersonation.\n8. Impersonate a different user not participating in the discussion.\n9. Load the same Incident with the discussion.\n\nNotice that there's an entry for the discussion that the user isn't a participant in is visible in the record's Activity Stream.\n\n10. Select **Open Discussion**.\n\n Expected behavior: Only users who are a participant should see the chat conversation\n\n Actual behavior: Users that aren't participants in a private chat are still able to see the chat conversation.\n\n
\n\nSoftware Asset Management\n\n PRB1913658\n\n [KB2290496](https://hi.service-now.com/kb_view.do?sysparm_article=KB2290496)\n\n\n\nOn an upgrade to Yokohama, new entitlements may get created from entitlement import errors\n\n\n\nUsers may observe the issue as duplicate entitlements found after an upgrade to Yokohama, or, after an upgrade to Yokohama, a number of entitlements were added that were created by 'system'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSoftware Asset Management Publisher Pack for Microsoft\n\n PRB1908686\n\n [KB2243700](https://hi.service-now.com/kb_view.do?sysparm_article=KB2243700)\n\n\n\nWindows OS Server Pattern is failing at the extension section 'collect CAL info' with duplicate DUPLICATE\\_RELATED\\_PAYLOAD errors for samp\\_user\\_device\\_license\\_consumption\n\n\n\nWindows OS Server Pattern did not update or populate the IP address for the host. In the payload, duplicate related items for the table 'msft\\_ual\\_user' in 'Collect CAL info' causes IRE issues.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSoftware Asset Normalization\n\n PRB1862904\n\n [KB1968357](https://hi.service-now.com/kb_view.do?sysparm_article=KB1968357)\n\n\n\nThe 'SAM - Find Normalization Suggestions' job fails when there are Discovery models with an empty version\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSoftware Asset Reclamation\n\n PRB1937128\n\n [KB2514421](https://hi.service-now.com/kb_view.do?sysparm_article=KB2514421)\n\n\n\nReturn value issue with SAMPReclamationUtil > getMetricAttributeFromLMR\n\n\n\nThe job 'SAM - Identifying New Reclamation Candidates' job fails with error: 'Cannot read property 'unlimitedLicense' from null.'\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSyntax Editor\n\n PRB1533082\n\n\n\nThe fonts defined on the system property 'glide.ui.html.editor .v4.font.collection' aren't displayed on the font list of the HTML editor on Agent Workspace\n\n\n\nThe list should show only the fonts defined in the value of system property 'glide.ui.html.editor .v4.font.collection', but it shows all the fonts mentioned on the system property 'Description'. On the native UI HTML editor, it's working as expected.\n\n\n\n \n\n
\n\nSystem Events\n\n PRB1933518\n\n [KB2515608](https://hi.service-now.com/kb_view.do?sysparm_article=KB2515608)\n\n\n\nDefault queue provisioning fails during an upgrade\n\n\n\nDefault queue provisioning fails during the upgrade process with the message 'invalid table: sysevent\\_queue\\_provider\\_param, state: failed'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nSystem Export Sets\n\n PRB1926120\n\n\n\nThere are node errors due to messages sent when Hermes/Kafka is unavailable or slow\n\n\n\nWhen Hermes/Kafka clusters are down or running slowly, LES can't check their health before sending messages. As a result, the producer client keeps retrying, and without any pause or queue in place, these repeated attempts can eventually push the node into an error state.\n\n\n\n \n\n
\n\nSystem Update Sets\n\n PRB1909130\n\n [KB2250914](https://hi.service-now.com/kb_view.do?sysparm_article=KB2250914)\n\n\n\nAn installation from an update set overwrites customized records\n\n\n\nTo remediate the update set, the commit should be backed out \\(including a rollback of the app install\\) and a different way of installing the application should be used.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nTable Administration and Data Management\n\n PRB1819751\n\n\n\nThere's a shadow table alter error when deleting a record after changing the string type field size from 50 to 100\n\n\n\nDeleting a record from a form \\(not a list\\) results in the following error: 'Error Message\\(conn=258502\\) ALGORITHM=NOCOPY is not supported. Reason: Cannot change column type. Try ALGORITHM=COPY'.\n\n\n\n \n\n
\n\nTime Card Management\n\n PRB1901454\n\n\n\n'Week starts on' doesn't work in Time Sheet Portal\n\n\n\nThe calender does not open for the **Week start** field on a form in the Time Sheet Portal.\n\n\n\n1. Provision an instance with the 'Time card management' plugin installed.\n2. Impersonate a system admin.\n3. Open time\\_cad\\_list.do.\n4. Create an entry.\n5. Select the **hamburger** icon and configure the form in form design.\n6. Add the field **Week start** in the time sheet portal view.\n7. Open the time sheet portal.\n\nObserve the created record.\n\n8. Select the three dots option.\n9. Select **open** in the 'form' view.\n\n Notice in the form that the **Week start** field is not opening the date picker.\n\n
\n\nTransaction Management\n\n PRB1909722\n\n\n\nForked transactions close the async context immediately on an error\n\n\n\nA few users have reported encountering a blank screen.\n\n\n\n \n\n
\n\nTransaction Management\n\n PRB1923245\n\n\n\nThe IllegalMonitorStateException in WaiterCountManager can prevent locked threads from being unlocked and lead to a deadlock\n\n\n\nThere's a race condition between a new thread pool addition during a specific plugin installation and locking thread-pool queues to claim a transaction for processing. This could cause a potential deadlock.\n\n\n\n \n\n
\n\nUI Field Administration\n\n PRB1157537\n\n [KB0685847](https://hi.service-now.com/kb_view.do?sysparm_article=KB0685847)\n\n\n\nUser presence works only if the browser cache is cleared\n\n\n\nThe user turned on the system property for user presence, but the user presence functionality doesn't work as expected. The user presence works when the user clears the browser cache.\n\n\n\n1. Using Chrome, log in to an instance as an admin user.\n2. Disable the presence.\n3. Using Firefox, log in to the instance as an ITIL user.\n4. In Chrome, as admin, enable the presence.\n\nNotice that the **Presence** icon becomes available.\n\n5. Navigate to the Firefox session.\n\nNotice that the **Presence** icon isn't reflected. If the user logs out and logs back in, the presence still doesn't show.\n\n6. Clear the browser cache in Firefox.\n\n Observe that the **Presence** icon works.\n\n
\n\nUI Field Administration\n\n PRB1774082\n\n\n\nThe glide.phone\\_number\\_e164.strict system property, which is false, doesn't seem to apply in the workspace form\n\n\n\nThe field type Phone Number \\(E164\\) displays an error in HR workspace but not in platform when the **Phone** field has incorrect digits and when the following system properties are set to false: glide.phone\\_number\\_e164.strict : false and glide.phone\\_number\\_e164. display\\_territory\\_selector: false.\n\n\n\n1. Open an HR record with a field type **Phone Number \\(E164\\)**.\n2. Put 11 digits instead of 10 in the platform view.\n3. Save the record.\n4. Open the same record in HR workspace.\n\n Observe that the same field now has an error in the HR workspace.\n\n
\n\nUI Field Administration\n\n PRB1881510\n\n\n\nThe category under 'change request values' on the standard change template isn't reflected in Service Operations Workspace\n\n\n\nThis issue is present in the base instance as well. The **category** field is visible, but the value set for the category isn't visible under 'change template values'.\n\n\n\n1. In the application navigator, navigate to **Change** > **Standard Change** > **My Proposals** > **New**.\n2. Create a template with the change request values filled in.\n3. Request approval.\n4. In Service Operations Workspace, navigate to **List** > **Tasks** > **Assigned to you** \\(remove the filter if required\\).\n5. Open the standard change template.\n\n Observe that the category under 'change request values' isn't reflected.\n\n
\n\nUI Field Administration\n\n PRB1882475\n\n\n\nChange request values on change templates aren't visible on Service Operations Workspace \\(SOW\\)\n\n\n\n \n\n\n\n1. Navigate to the std\\_change\\_producer table.\n2. Open an existing change template or create a new one.\n3. Ensure that the view is SOW.\n4. Ensure that the form layout has the **Change Request values** field present.\n5. Navigate to SOW.\n6. Open the standard change template.\n\n Observe that the change request values aren't visible.\n\n
\n\nUI Field Administration\n\n PRB1894570\n\n\n\nHTML height is read-only with client script changes when a section is changed\n\n\n\n \n\n\n\n1. Navigate to incident.list.\n2. Create an HTML field on the dictionary.\n3. Save a record with random text.\n4. Navigate to client script and create a client script so that the field is read-only.\n5. Navigate to the record.\n\nObserve that HTML read only height is small.\n\n6. Change section and note the HTML height.\n\n Notice that the HTML height is read-only.\n\n
\n\nUI Field Administration\n\n PRB1941078\n\n\n\nrelated\\_list\\_edit\\_helper.processMRARecords doesn't apply contextual ACLs\n\n\n\nThis issue occurs after installing the Enterprise Asset Management plugin.\n\n\n\n1. Install Enterprise Asset Management plugin.\n2. Navigate to **Asset Workspace**.\n3. Create a pallet.\n4. Create asset.\n5. Log in as a technician.\n6. Select **Add assets**.\n7. Select an asset.\n8. Select the **Add on MRA** pop-up.\n\n Observe that the asset didn't get added.\n\n
\n\nUI Field Administration\n\n PRB1945077\n\n\n\nClick-to-call ignores the E.164 country code and defaults to +1\n\n\n\nThe 'Click-to-call' feature incorrectly dials US numbers instead of international numbers like the UK or India, regardless of the country code. Dialing from the contact card works correctly, but using the **Click-to-call** icon always defaults to US numbers.\n\n\n\n1. Navigate to the CSM Workspace.\n2. Open a case record.\n3. Select the **Information** icon of the **Contact** field.\n\nThe user account opens.\n\n4. Select the **phone** icon of the **Business phone** field.\n\n An outbound call is placed, and an interaction record is created.\n\n
\n\nUI Field Administration\n\n PRB1959307\n\n\n\nNotes text area does not auto expand when a new interaction/incident is created in Workspace\n\n\n\nThe **Journal** field work notes do not resize automatically as they did in previous versions.\n\n\n\n1. Open SOW.\n2. Notice the **+** icon in the workspace.\n3. Select a new interaction/incident.\n4. Start typing until the content exceeds the visible area.\n\n Notice that the text area is not resizing and the user is unable to see the text written.\n\n
\n\nUI Form Administration\n\n PRB1894995\n\n [KB2438505](https://hi.service-now.com/kb_view.do?sysparm_article=KB2438505)\n\n\n\nA requested item \\(RITM\\) created from an interaction in Service Operations Workspace \\(SOW\\) with an HTML variable automatically re-attaches images from the variable as the current user\n\n\n\nWhen a user copy-paste text + images from Word, email, etc. to an RITM created from an interaction in a SOW HTML variable, reloading the RITM automatically re-attaches images to the record and gets displayed in the activity stream as a new attachment.\n\n\n\n1. Navigate to an Xanadu instance.\n2. Create a catalog item with one HTML variable.\n3. Open an interaction record from SOW.\n4. Locate and select the **Create Request** button.\n5. Create a request for the catalog item created in the second step.\n6. In the HTML variable, copy-paste text and images from a Word document or email.\n7. Submit the request.\n8. From SOW, open the RITM just created.\n\n Expected behavior: The RITM opens normally and images aren't reattached.\n\n Actual behavior: Images from the variable are reattached every time a user opens the RITM record. Newly re-attached images are show in the activity stream. These images can also be found in the sys\\_attachment table with Table sys ID = RITM sys\\_id.\n\n
\n\nUI Form Administration\n\n PRB1919041\n\n\n\nAn empty and read-only **Template value** input field causes an error when saving a record: 'Cannot read properties of null \\(reading 'hasChildNodes'\\)\\)'\n\n\n\nTo reproduce, users need a record with an input field of type **Template value**, that is empty and also read-only. The error shows when saving the record.\n\n\n\n1. Log in as an admin.\n2. Navigate to **All** > **incident.CONFIG**.\n3. Add a field called **Test Template**.\n4. Make it of the type 'Template Value' and save.\n5. Select the 'Advanced' view and the 'Dependent Field' tab.\n6. Select **Use dependent field** and a field, such as 'Channel'.\n7. Save the changes.\n8. Navigate to **All** > **incident.CONFIG**.\n9. Create a UI Policy that will always make the new template value field read-only.\n10. Pick an existing incident.\n11. Make a change to the **Short description** field and save.\n\n Expected behavior: The record should save without error.\n\n Actual behavior: There's an error: 'Cannot read properties of null \\(reading 'hasChildNodes'\\)'.\n\n
\n\nUI Form Administration\n\n PRB1920717\n\n\n\nHyperlinks in annotations on forms are not opening in a new window\n\n\n\nHyperlinks open in the same tab instead of opening in a new tab.\n\n\n\n1. Open a base instance.\n2. Open an incident table.\n3. Open any incident.\n4. Select and hold \\(or right-click\\) and navigate to **Configure** > **Form builder**.\n5. Create an annotation with the code.\n6. Open the incident in SOW.\n7. Under 'Details,' select the link.\n\n Expected behavior: It opens the link in a new tab.\n\n Actual behavior: It opens the link in the same tab.\n\n
\n\nUI Form Administration\n\n PRB1926448\n\n\n\nAfter upgrading to Yokohama, the 'Before Query' business rule doesn't filter records in the workspace using an encoded query\n\n\n\nAdding an encoded query on a 'Before Query' business rule to a filter record restricts the record on UI16, but fails to filter the record in the workspace. The record doesn't open in UI16, but opens successfully in the workspace. This issue was found in Yokohama and Zurich.\n\n\n\n1. Create a 'Before Query' business rule on the incident table.\n2. Create an incident with a short\\_description.\n3. Set it to 'test'.\n4. Attempt to open the record in UI16 and workspace.\n\n
\n\nUI Form Administration\n\n PRB1938024\n\n\n\nThe 'View' context and tooltip is broken for a sn\\_cmdb\\_admin user\n\n\n\n \n\n\n\n \n\n
\n\nUI Form Administration\n\n PRB1950676\n\n [KB2622641](https://hi.service-now.com/kb_view.do?sysparm_article=KB2622641)\n\n\n\nThe Approval Summarizer formatter isn't displayed after upgrading to Zurich\n\n\n\nAn issue has been identified after upgrading to Zurich with the Approval Summarizer formatter where the approval record doesn't display the summary of the item being approved.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUpgrade Center\n\n PRB1889948\n\n\n\nThe pop-up 'Edit box' UI is mispositioned when trying to edit a field by double-clicking \\(or using the keyboard shortcut\\) on it on a hierarchical list\n\n\n\nThis issue is found in Washington DC, Xanadu, and Yokohama.\n\n\n\n1. Open a base instance.\n2. Navigate to the **change\\_request** table.\n3. Enable the hierarchical list for this table.\n4. Open any change record.\n5. Add at least 20 records to the first related list on that change record.\n6. Return to the change list.\n7. Expand the hierarchical list for the same change record from step 4.\n8. Try to edit the 15th or later cell on that expanded list.\n\n Notice that the **Edit box** UI is mispositioned.\n\n
\n\nUpgrade Center\n\n PRB1933942\n\n\n\nSkipped error after upgrading\n\n\n\nThe user gets a skipped error after upgrading the instance from Xanadu to Yokohama. The reason is 'Skipping unavailable system property glide.db.df\\_engine.enabled. Customers cannot configure this property.' It's included in the plugin 'com.snc.db.df\\_engine'.\n\n\n\n \n\n
\n\nUsage Analytics\n\n PRB1819883\n\n\n\nNull pointer exceptions occur when running 'UACountPersistorMessageEnqueueJob' and 'UsageAnalytics Count Persistor V2'\n\n\n\n \n\n\n\n \n\n
\n\nUsage Analytics\n\n PRB1925359\n\n [KB2423777](https://hi.service-now.com/kb_view.do?sysparm_article=KB2423777)\n\n\n\nMultiple out of memory \\(OOM\\) errors are triggered on the nodes from the 'User Property Change Sync' job\n\n\n\nMultiple OOM errors were triggered on the nodes at different times whenever the 'User Property Change Sync' job was running. As a result, the node restarts.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUsage Analytics\n\n PRB1931446\n\n\n\nGCC/On-Prem/Self-Hosted users get exceptions and errors when using User Property Sync and Usage Tracking - Migration\n\n\n\nFor the first issue, the user property sync is turned on for on-prem/self-hosted instances and is trying to sync the user property like in TrackLongInactiveUserLogin. TrackLongInactiveUserLogin should actually check if instance is self-hosted and job should not run. There's an error. For the second issue, migration jobs aren't respecting on-prem constraints, and are attempting to sync from appsee via host URL. This URL is empty for on prem instances. Jobs like apps/funnel/cohort migration are running regardless of the instance type, leading to errors.\n\n\n\n1. Navigate to any on-prem instance.\n2. Try to run the 'User Property sync' job by navigating to **scheduled jobs**.\n\nThis should not run.\n\n3. Try to run the 'App Migration' job by navigating to **scheduled jobs**.\n\nThis should not run.\n\n4. Check if metric calls are going.\n\nThey should.\n\n5. Try to run the 'Config downloader' job.\n\nThis should not run.\n\n\n
\n\nUsage Analytics\n\n PRB1960875\n\n\n\nThe UXAAppMigrationJob job throws an error\n\n\n\nThe UXAAppMigrationJob job throws an error reading, 'Script: UXAAppMigration : inserting into sys\\_analytics\\_app table failed with error:ReferenceError: \"APIKEY\" is not defined.: no thrown error com.glide.ui.ServletErrorListener'.\n\n\n\n \n\n
\n\nUser Administration\n\n PRB1930929\n\n [KB2468450](https://hi.service-now.com/kb_view.do?sysparm_article=KB2468450)\n\n\n\nUpdates on the sys\\_user table are aborted by business rules, breaking functionality\n\n\n\nThe business rules are too restrictive. The following business rules contain 'Abort action' in the script if an invalid country code or language code is present: 'Prevent invalid country code' and 'Prevent invalid language code'. However, they don't have any conditions to trigger. If the country code or language code was already invalid due to historic imports/updates, then all transactions on the sys\\_user records \\(and extended tables like customer\\_contact\\) is aborted. This breaks functionality such as data import, updating the user profile, password reset application, and administering the sys\\_user record via the UI. There is also insufficient logging presented to the user to indicate why the transaction failed.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUser Authentication\n\n PRB1944133\n\n\n\nThere's a login page \\(login.do\\) presentation issue after a Zurich upgrade\n\n\n\nThere's a login page \\(login.do\\) presentation issue after a Zurich upgrade when changing the language to French.\n\n\n\n \n\n
\n\nUXF Components\n\n PRB1919730\n\n [KB2505771](https://hi.service-now.com/kb_view.do?sysparm_article=KB2505771)\n\n\n\nUXF page components aren't loading properly post-upgrade due to a page fragment not updating during the upgrade\n\n\n\nWhen users upgrade minor patches, if there are no changes to the metadata related to macroponents, page fragment caches won't be flushed. During the upgrade process, if any user accesses pages that have asset bundles, a problem occurs. During the upgrade, asset bundling is turned off, so the macroponent page fragment doesn't have assetsInBundle, but once the upgrade is completed, asset bundling will be turned on. However, the backend is serving the old page fragment without the asset bundle context, and the macroponent asset bundle is not loaded, so components in the page won't load.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUXF Macroponent\n\n PRB1909733\n\n\n\nA thread is stuck because there are multiple threads accessing the same page with the same macroponent\n\n\n\nThere is a stuck semaphore transaction related to the function createCacheable PageFragment FromShell in CacheablePage FragmentFactory.java. This can lead to multiple threads stuck with no other option than to restart the node to provide relief. This may occur when there is no cache entry for the requested macroponent on the server, and multiple users are trying to access the same page with the same macroponent simultaneously.\n\n\n\n \n\n
\n\nUX Framework\n\n PRB1886861\n\n\n\nThere's an Automated Test Framework \\(ATF\\) error\n\n\n\nA syntax error or access rule violation is detected by database: '\\(\\(conn == xxxxx\\) Table 'xxxxx\\_1.sys\\_uxf\\_snapshot' doesn't exist\\)'.\n\n\n\n \n\n
\n\nUX Framework\n\n PRB1887044\n\n [KB2541971](https://hi.service-now.com/kb_view.do?sysparm_article=KB2541971)\n\n\n\nThe latest asset in sys\\_ux\\_lib\\_asset isn't used when multiple asset records exist for the same asset version\n\n\n\nThis impacts Now Assist Panel loading and Dirty State Management in workspaces.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUX Framework\n\n PRB1892094\n\n\n\nAn ATF test UI action fails due to a timeout error\n\n\n\nThe intent library delivers context on generator registration for translators that don't exist on the page.\n\n\n\n \n\n
\n\nUX Framework\n\n PRB1924256\n\n\n\nIn Service Operations Workspace \\(SOW\\), the Change Overview page loads blank on the first normal change creation in a new session\n\n\n\nAfter creating a new normal change and saving the record, the 'Overview' page is displayed as blank.\n\n\n\n1. Log in to an instance.\n2. Impersonate a user.\n3. Open SOW.\n4. Navigate to **Change** in List.\n5. Create a new normal change.\n6. Save the record.\n\n Notice that the 'Overview' page is displayed empty.\n\n
\n\nUX Framework\n\n PRB1925967\n\n\n\nEngagement Messenger isn't loading chats after upgrading\n\n\n\nThe chat box in Engagement Messenger is blank, and loads no content. The errors occurs, 'SecurityError: Failed to read a named property 'uxfIntentLibrary' from 'Window'.\n\n\n\n1. Launch the Engagement Messenger.\n2. Select the chat box.\n3. Observe that the chat box is blank.\n4. Navigate to a Yokohama instance.\n5. Navigate to Agentic Portal in a separate browser tab.\n\nDon't attempt to log in.\n\n6. Open up the dev console.\n7. Execute the script.\n8. Execute the code.\n9. Select the chat bubble that appears after the code finishes executing.\n\n Expected behavior: The chat loads with content.\n\n Actual behavior: The chat load is blank and a security error appears in console.\n\n
\n\nUX Framework\n\n PRB1942276\n\n [KB2661969](https://hi.service-now.com/kb_view.do?sysparm_article=KB2661969)\n\n\n\nWhen hovering over any workspace tabs \\(parent or child/secondary\\), the tooltip stays on screen and doesn't disappear\n\n\n\nThis is an intermittent issue, but when it occurs the user can't read part of the record.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUX Framework\n\n PRB1947987\n\n [KB2649894](https://hi.service-now.com/kb_view.do?sysparm_article=KB2649894)\n\n\n\nCSM/FSM Workspace list filter changes when opening and closing a record\n\n\n\nWhen opening a record through the list in the CSM/FSM Configurable Workspace, the list's filter is modified after closing the record.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nUX Framework\n\n PRB1966606\n\n\n\nMake UXF Caches Hard references to mitigate long build times from cache reclaims\n\n\n\nThis is a product update.\n\n\n\n \n\n
\n\nVirtual Agent\n\n PRB1878374\n\n\n\nIn Teams, conversations are stuck and run into errors after switching between instances\n\n\n\n \n\n\n\n1. Connect the Prod bot to an instance.\n2. Run a few conversations on Teams.\n3. Switch to another instance.\n4. Try running a few conversations.\n\n Expected behavior: The user is able to run conversations on Teams.\n\n Actual behavior: The user conversations are stuck and run into errors sometimes.\n\n
\n\nVirtual Agent\n\n PRB1890944\n\n [KB2338484](https://hi.service-now.com/kb_view.do?sysparm_article=KB2338484)\n\n\n\nLarge /api/now/v1/cs/ consumerAccount /unreadMessage calls from Proactive Trigger exhaust instance API resources\n\n\n\nSome users on Portal have over 1 million of /api/now/v1/cs/ consumerAccount /unreadMessage call observers in the node logs. This causes an issue as it exhausts the API rate limit and prevents people from submitting forms on the portal and other issues. The API call is constantly sent out even when the session is timed out.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nVirtual Agent\n\n PRB1893137\n\n\n\nThe Virtual Agent LLM survey displays a question twice\n\n\n\nIt's observed that there's LLM support for a survey, and the questions asked in the survey are populated twice.\n\n\n\n \n\n
\n\nVirtual Agent\n\n PRB1896593\n\n\n\nShouldn't be relying on the 'Greetings' topic for portal's Virtual Agent hand off\n\n\n\nUsers can have custom 'Greetings' topics. For those users, the hand off is broken.\n\n\n\n \n\n
\n\nVirtual Agent\n\n PRB1905962\n\n\n\nLink, text and icon menu items aren't working in Virtual Agent branding in Dynamic Window\n\n\n\n \n\n\n\n1. Navigate to our branding config record and review the menu items listed at the bottom: /sys\\_cs\\_branding\\_setup\\_list.do?.\n\nObserve that there's items for links, icons and text as menu items.\n\n2. Navigate to the portal after impersonating a valid user.\n3. Open Virtual Agent by selecting the icon at the bottom right.\n4. Select the **Support** button at the top of virtual agent window.\n\nObserve that none of the items of links, icons and text appear.\n\n\n Expected behavior: All type of menu items should display.\n\n Actual behavior: Only the phone and email are working.\n\n
\n\nVirtual Agent\n\n PRB1913154\n\n\n\nNon-actionable notifications under regular cases create interaction records for channels and NASS\n\n\n\nFor channels and NASS, it creates a conversation and does a silent handshake for NASS/NAVA. This creates a conversation and an interaction internally, which is incorrect.\n\n\n\n1. Make sure that the user has had some conversation with NASS/Channel.\n2. Trigger a non-actionable notification.\n\n Expected behavior: A conversation associated with the notification shouldn't have an interaction record.\n\n Actual behavior: An interaction record is created.\n\n
\n\nVirtual Agent\n\n PRB1927571\n\n [KB2586834](https://hi.service-now.com/kb_view.do?sysparm_article=KB2586834)\n\n\n\nSessionManager and MacMessageBatchingSession is caching rhino objects contributing to higher heap usage\n\n\n\nWith a cache using around 150+ MB, storing rhino scope objects within a cache make it unexpectedly large depending on the GlideRecord queries that they run or JavaScript objects stored in the scope.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nVirtual Agent\n\n PRB1930434\n\n\n\nMultilingual functionality is broken, and the complete flow is not working as expected\n\n\n\nThis issue was observed in Yokohama with RAG 3.0.4 after the ynowassist nightly build occurred.\n\n\n\n1. Impersonate as user with Japanese session language.\n2. Ensure 'glide.sys.language' system property is in Japanese with the system property value would be 'ja'.\n3. Create a skill.\n4. Add RAG as tool.\n5. Execute the skill.\n\n Expected behavior: The skill and RAG tool should execute successfully.\n\n Actual behavior: RAG is failing with attached error.\n\n
\n\nVirtual Agent\n\n PRB1933184\n\n\n\nThere's empty users in the sys\\_gen\\_ai\\_usage\\_log table\n\n\n\nIn SystemScriptObject, when executeSkill\\(\\), if setLicenseUsage\\(\\) is called before execute\\(\\), sys\\_generative\\_ai\\_log would not be created yet and sys\\_gen\\_ai\\_usage\\_log's user field wouldn't be populated. There may be other instances where the user calls setLicenseUsage\\(\\), but there's no conversation.getContext\\(\\).getGenAILogId\\(\\).\n\n\n\n1. Start a NAP conversation.\n2. Execute a skill \\(for example, order laptop\\).\n3. Navigate to sys\\_gen\\_ai\\_usage\\_log table.\n\n Expected behavior: The **User** field should be populated.\n\n Actual behavior: The **User** field on the record that was just created is empty.\n\n
\n\nVirtual Agent\n\n PRB1935944\n\n\n\nPost-chat survey results aren't stored in the 'Assessment instance' table\n\n\n\nThere should be a record of the feedback asmt\\_assessment\\_instance given in the post-chat survey. However, no feedback given by the user in the post-chat survey is stored.\n\n\n\n \n\n
\n\nVirtual Agent\n\n PRB1947698\n\n\n\nOnly one agentic workflow executes successfully when the same trigger fires simultaneously\n\n\n\nWhen a workflow trigger fires simultaneously multiple times, only one of the resulting agentic workflows executes successfully. The other workflows terminate immediately with an error indicating that no session ID could be found. Each trigger correctly creates a new execution plan and a new conversation record, but only one conversation proceeds, while the others fail at the start.\n\n\n\n1. Create the agentic workflow named 'Test multiple case executions'.\n2. Select three or more case records.\n3. Update them simultaneously so that the trigger fires for all at once.\n\nNotice that the three execution plans \\(sn\\_aia\\_execution\\_plan\\) and three conversation records are created. Only one conversation and execution plan executes successfully. The other conversations don't continue after the first task with the error 'No session ID found'.\n\n\n Expected behavior: Each triggered workflow should independently create or resolve its own valid session so that all conversations execute successfully, even under concurrent trigger conditions.\n\n Actual behavior: Only one conversation executes successfully. The other conversations either terminate immediately or don't continue after the first task with 'No session ID found' error.\n\n
\n\nVirtual Agent\n\n PRB1954972\n\n\n\nTeams conversations time out due to a slow tracer query as the sys\\_cs\\_fdih\\_invocation table becomes too large\n\n\n\nThe sys\\_cs\\_fdih\\_invocation table can become large with 99.9999% records without a trace\\_id \\(trace\\_id=Null\\). A slow query can be triggered: 'QueryWarning \\*\\*\\* WARNING \\*\\*\\* Large Table: Table handling an extremely large result set: 2194898. Query that got us here is: TABLENAME = sys\\_cs\\_fdih\\_invocation ENCODED\\_QUERY = trace\\_id=NULL'.\n\n\n\n \n\n
\n\nVirtual Agent\n\n PRB1956231\n\n\n\nvaVars or vaInputs variables set in a script include from an LLM input script area aren't unwrapped\n\n\n\nThe value should be unwrapped and stored as base type \\(i.e. java.lang.String\\) in task context. Instead, the value is sent as NativeJavaObject, which leads to an xstream serialization exception.\n\n\n\n1. Create a script include that takes vaVars as a variable.\n2. In that script include, set a variable on vaVars: vaVars.time = global.VAClickMetrics.getCurrentTime\\(\\); from an LLM input node script area \\(like Dynamic Choice Picker\\).\n3. Create an instance of this object.\n\n Expected behavior: The value is unwrapped and stored as base type \\(i.e. java.lang.String\\) in task context.\n\n Actual behavior: The value is sent as NativeJavaObject, which leads to an xstream serialization exception.\n\n
\n\nVirtual Agent\n\n PRB1976846\n\n\n\nSessionManager/ qlueSessionToChannelSessionMap caches rhino objects, contributing to higher heap memory usage\n\n\n\nEven if it's using a cache of 100, each item takes between 8-10 MB, causing the overall memory consumption to spike to over 800 MB.\n\n\n\n \n\n
\n\nVirtual Agent third-party integrations\n\n PRB1956730\n\n [KB2683059](https://hi.service-now.com/kb_view.do?sysparm_article=KB2683059)\n\n\n\nLive agent only mode doesn't work for third-party channels\n\n\n\nThe user messages aren't received by the agent. This message appears in the log: 'Couldn't find rich control, dropping current message'.\n\n\n\nRefer to the listed KB article for details.\n\n
\n\nVirtual Agent Web Client\n\n PRB1896591\n\n\n\nEmoji panel loading is slow in Windows OS\n\n\n\nChrome and Edge browsers freeze for one minute after the user selects an **Emoji** icon in the Virtual Agent Web Client.\n\n\n\n \n\n
\n\nVirtual Agent Web Client\n\n PRB1920035\n\n\n\nThe 'VTT' icon isn't available in previous model of Now Assist Portal \\(NAP\\)\n\n\n\nThe issue occurs when the user switches from the new model to the previous model with VTT turned on.\n\n\n\n1. Provision an instance with any of the BU skills installed.\n2. Turn on NAP with VTT.\n3. Turn on the microphone from the browser preferences.\n4. Toggle 'on' accessibility settings.\n5. Select the **NAP icon**.\n6. Ensure the **VTT** icon is available in the new model.\n7. Change the model to old model \\(Self service modal dialog\\).\n8. Refresh the page.\n\n Expected behavior: The **VTT** icon should be available.\n\n Actual behavior: The **VTT** icon is not available in the old model of NAP when the user switches from the new model to old model with VTT enabled.\n\n
\n\nVirtual Agent Web Client\n\n PRB1942157\n\n\n\nThe KB article displays an 'undefined' avatar for a guest user\n\n\n\n \n\n\n\n1. Open the /csp portal in an instance without logging in.\n2. Initiate a chat with the Virtual Agent \\(VA\\).\n3. Fill in all the details like First Name, Last Name, and Email.\n4. Select **Product Issue**.\n5. When the VA prompts to describe the issue, enter 'dishwasher'.\n6. Select **Yes** for summary accurate.\n7. Select **Show me everything** > **Get Help \\(Template\\)**.\n8. Enter 'dishwasher'.\n\n Observe that the VA comes back with the KB article, but the avatar of the KB is undefined.\n\n
\n\nVirtual Agent Web Client\n\n PRB1943211\n\n\n\nA custom image for a FAB icon doesn't occupy the entire button\n\n\n\nThe current implementation uses a now-circular-button, but the custom image passed is set to the icon property of the button, which only occupies part of the button.\n\n\n\n \n\n
\n\nVirtual Agent Web Client\n\n PRB1972561\n\n [KB2787591](https://hi.service-now.com/kb_view.do?sysparm_article=KB2787591)\n\n\n\nEnhanced chat does not pick up custom tokens in portal\n\n\n\n \n\n\n\nRefer to the listed KB article for details.\n\n
## All Other Fixes\n\nTo view a list of all other PRBs fixed in Australia, refer to [All other Australia fixes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/australia-all-other-fixes.md).\n\n**Parent Topic:**[Available patches and hotfixes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/release-notes/available-versions.md)\n\n"}}