| \n\nActivity and Subscriptions\n\n PRB2069585\n\n [KB3148451](https://hi.service-now.com/kb_view.do?sysparm_article=KB3148451)\n\n | \n\nThe 'Customer history' tab keeps loading on the front-line case page\n\n | \n\nThe tab never loads.\n\n | \n\n \n\n |
| \n\nActivity Stream\n\n PRB1991852\n\n | \n\nBase64 coded attachments can't be loaded in the activity stream in the workspace\n\n | \n\nThis likely has to do with processing large content.\n\n | \n\n1. Navigate to any record page.\n2. Create an email with a base64 encoded image.\n3. Set the email to 'sent' status.\n4. Navigate to the record and select **Show more** for the email.\n\n Expected behavior: The full body of the email is displayed.\n\n Actual behavior: The email is loading for a long time and eventually crashes the page.\n\n |
| \n\nActivity Stream\n\n PRB2017633\n\n | \n\nActivityDBListener fires too many AMB messages on bulk deletes\n\n | \n\n \n\n | \n\n1. Open an incident in a workspace.\n2. Create two emails.\n3. Open sys\\_email\\_list.do.\n4. Set both emails' type to 'sent' 5.\n5. Notice that when returning back to the 'Incident' page, there should be two emails now.\n6. Open the Network panel in the DevTool's inspect window.\n7. Reload the page.\n8. Filter by 'amb'.\n9. Select the AMB message.\n10. Select the 'Messages' tab.\n11. Clear all of the messages.\n12. In the sys\\_email\\_list.do, select one of the emails from step 4 and delete it.\n\nObserve that in the 'Network tab', there should be an AMB message for the deleted email.\n\n13. In /sys\\_email\\_list.do, delete multiple emails that are 'send-ready'.Observe that in the 'Network' tab, there should be no messages for those deleted emails.\n14. In /sys\\_email\\_list.do, delete multiple emails that are 'send-ready' and the other email from step 4.\n\n Observe that in the 'Network' tab, there should only be 1 message for the other email.\n\n |
| \n\nActivity Stream\n\n PRB2032224\n\n | \n\nOrphaned Dependent fields in the initial audit event causes an exception in SysAuditRule\n\n | \n\nWhen the support audit is passed to findFirst, which filters out support audits, it finds an empty stream and throws 'IllegalStateException: Unreachable code reached.' The exception is caught, but it causes retrieveEvents to return zero events, leaving the workspace activity stream completely empty.\n\n | \n\n \n\n |
| \n\nActivity Stream\n\n PRB2060131\n\n | \n\nWhen table rotation is set up for sys\\_audit\\_relation, audit relationship events don't display in a workspace\n\n | \n\n \n\n | \n\n1. Navigate to **Table Rotations** \\(sys\\_table\\_rotation\\).\n2. Add a record for sys\\_audit\\_relation.\n3. Set the type to 'Extension' and the 'Duration' to 1 hour or less.\n4. Create new audit relationship changes.\n\n Expected behavior: The audit relationship changes are displayed in the workspace Activity Stream.Actual behavior: The audit relationship changes are not displayed.\n\n |
| \n\nActivity Stream\n\n PRB2066570\n\n | \n\nIn Activity stream primary Journal **field** ordering, work\\_notes are displayed before comments in UI16 and Service Portal\n\n | \n\nThe activity stream on task records \\(Incidents, Changes, etc.\\) incorrectly defaults to the 'Work Notes' input instead of 'Comments' in both the platform UI and Service Portal. This affects user workflow as agents may inadvertently post internal work notes when intending to post user-visible comments. Additionally, custom **Journal** fields configured on tables don't appear in the Service Portal activity stream widget.\n\n | \n\n1. Open any task-extended record \\(for example, Incident\\) in UI16 or Service Portal.\n2. Observe the activity stream input area.\n\n Expected behavior: 'Comments' is the default selected journal input field.\n\n Actual behavior: 'Work Notes' is the default selected journal input field.\n\n |
| \n\nActivity Stream\n\n PRB2073311\n\n | \n\nBuild backend graphQL endpoint for List Activity\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nActivity Stream\n\n PRB2073313\n\n | \n\nProvide supplemental data for returned records on the new back-end for list activity\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nActivity Stream\n\n PRB2073315\n\n | \n\nReview DT APIs for security\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAdvanced Work Assignment\n\n PRB2060584\n\n [KB3143279](https://hi.service-now.com/kb_view.do?sysparm_article=KB3143279)\n\n | \n\nThe 'Set logged out agent offline' script action shouldn't touch presence states when 'disable\\_inactivity\\_check' is set to true\n\n | \n\nA live human agent is made offline whenever they log out. However, the log out script action should bypass the agents in those presence states that have 'disable\\_inactivity\\_check' set to true.\n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2063949\n\n | \n\nSome messages are hidden on the agent's side when hideControl is true and contains searchText\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAgent Chat\n\n PRB2068933\n\n | \n\nA workspace error is observed when handling incomingmessaging interactions in Agent Workspace\n\n | \n\nIn both scenarios, the error modal occurs.\n\n | \n\nScenario 1:\n\n 1. Open a messaging interaction in the CSM workspace.\n2. As a agent, go to any other tab than the ongoing interaction.\n3. Send one or more messages from the requester.\n4. Ensure sure the ongoing messaging count is visible.\n5. Switch to the current interaction\n\n Observe the error modal.\n\n Scenario 2:\n\n 1. Open a messaging interaction in CSM workspace.\n2. Send one or more messages from the agent/requester.\n3. Refresh the page.\n\n Observe the error modal.\n\n |
| \n\nAgile Development\n\n PRB2057888\n\n | \n\nAdd script include to gate PWS-CWM functionalities\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2059351\n\n | \n\nRecord scope should override the user session scope\n\n | \n\nFor AI Agents, when any record of a user instance is used, the record scope should override the user session scope of the MSP as per the domain separation policy. However, that's not happening. For example, when an AI Agent with a retriever tool is triggered by any record in a user instance \\(like C1\\), it fetches KBs/results from all the user instances under that MSP.\n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2059390\n\n | \n\nRole masking isn't unset when running a workflow\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2061451\n\n | \n\nThe topic tool execution status is 'success to completed' before the tool completes\n\n | \n\n \n\n | \n\n1. Create a topic tool with input nodes in it.\n2. End the topic execution if the user replies back.\n3. Add it to the agent as a tool.\n\n Observe that the sn\\_aia\\_tools\\_execution record execution status should be marked as 'Success' only when topic completes.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2069685\n\n | \n\nEG mini doesn't work in the KG tool in AIA Agent\n\n | \n\n \n\n | \n\n1. Create an AIA agent with the KG tool.\n2. Select **EG mini schema** and a tag with it.\n3. Try to run the agent which calls the tool.\n\nObserve that the tool call fails.\n\n4. Select **EG as schema**.\n\n Observe that it works as expected.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\nPRB2070503\n\n | \n\nGeneric tool for mutate operations for agent-orchestrator-v2\n\n | \n\n \n\n | \n\n1. Enable domain separation.\n2. Start conversations from different domains.\n3. Ensure records are not available cross the domain.\n4. Run the abandoned conversation job.\n\n Notice that the conversations do not get properly faulted and throws an exception.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2074132\n\n | \n\nmeta.agentId is 'null' for assistant-wired tools, breaking agentic\\_context in OGScriptToolExecutor\n\n | \n\nTools that are wired directly to assistants a not to an agent have always had an empty **Agent** field on their tool M2M record. Previously this was masked because DARE resolved the default root agent \\('Otto'\\) regardless, so meta.agentId was always populated in the tool's input request. Now that the default-agent resolution is gone, meta.agentId comes through as null for these assistant-wired tools. The OGScriptToolExecutor depends on meta.agentId to populate the **agentic\\_context** field on the tool execution. With meta.agentId as 'null', the agentic\\_contex is no longer populated for any tool wired directly to an assistant.\n\n | \n\n1. Take a tool whose M2M record is wired to an assistant directly.\n2. Ensure the **Agent** field on that M2M record is empty.\n3. Invoke the tool through that assistant.\n4. Inspect the tool's input request.\n\n Observe that 'meta.agentId' is null, and OGScriptToolExecuto does not populate the agentic\\_context.\n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2074803\n\n | \n\nImplement a scriptable method for channels instead of restmessagev2\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2074876\n\n | \n\nProcess A2A primary asynchronous responses to offglide via Hybrid Queue\n\n | \n\nCurrently, external agent \\(A2A\\) primary async responses land in sn\\_aia\\_external\\_agent\\_primary\\_async\\_responses and are forwarded to offglide via a synchronous, in-transaction path \\(A2aPrimaryAsyncEventHandler\\) guarded by a raw Mutex. This blocks the event-delegator thread for the duration of the DB read and offglide POST + mark-processed sequence, and doesn't benefit from the platform's existing overflow/shutdown safety net.\n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2074920\n\n | \n\nEnable the passing of the assistant context from AI Agents to GAIC\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Agents \\(Glide Family\\)\n\n PRB2078415\n\n | \n\nAdd sys\\_og\\_conversational\\_cache\\_http\\_log with request-ID dedup for setCache\n\n | \n\nCCS adds a retry to its glide calls, and a re-tried SET\\_CACHE re-executes the configuration row's set\\_script with no record that the original attempt already applied.\n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2059453\n\n | \n\nTrue up version for the AIXF Store app\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2061584\n\n | \n\nTrue-up the AI UX Builder Store app\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Experience Framework - Glide\n\n PRB2062421\n\n | \n\nThe ACL 'Type' dropdown list does not include aiux\\_page, aiux\\_widget, or aiux\\_dashboard options\n\n | \n\nNone of these types are available when they should be included as selectable options.\n\n | \n\n1. Navigate to sys\\_security\\_acl.list.\n2. Select **New** to create a new ACL record.\n3. Open the 'Type' dropdown list.\n4. Search for aiux\\_widget, aiux\\_page.\n\n Expected behavior: The 'Type' dropdown list should include aiux\\_page, aiux\\_widget, and aiux\\_dashboard as selectable options.\n\n Actual behavior: The AIUX types are not present in the 'Type' dropdown list.\n\n |
| \n\nAI Gateway - Security\n\n PRB2041348\n\n | \n\nThe autogenerated fake sys\\_ids in AIG should be fixed\n\n | \n\nFix the files sys\\_id and corresponding ITs and UTs.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB1859571\n\n | \n\nA search retrieval agent returns an incorrect catalog item URL\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB1918638\n\n | \n\nIndexing fails for the batch due to a corrupted GZIP trailer error\n\n | \n\nTwo errors occur in the system log, resulting in some of the KBs in the batch to not be indexed.\n\n | \n\n1. Attach the problematic attachment of one KB article.\n2. Index the Knowledge indexed source.\n3. Check the system log.\n\n Notice that there are two notable errors, 'Corrupt GZIP trailer' and 'Internal Server Error.' As a result, some KBs in the same batch are not indexed due to the exception.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB1925971\n\n | \n\nThe 'Category' and 'Catalog' facets for catalog items are not using the translated values\n\n | \n\nThe facet filters remain untranslated, even though the facet filters under 'Categories' and 'Catalogs' have translated values provided.\n\n | \n\n1. Set up AIS in the /esc portal with the default esc search application and profile.\n2. Ensure the search application has these two facets configured:\n - sc\\_cat\\_item.sc\\_catalogs\n - sc\\_cat\\_item.category\n3. Activate another language plugin, such as Italian.\n4. Find an sc\\_cat\\_item that is searchable.\n5. Navigate to the **category.sc\\_catalog** field.\n6. For that catalog, ensure there is an entry in the sys\\_translated\\_text table with the following:\n - Document: Catalog sys id\n - Field name: **Title**\n - Language: Italian\n - Table name: 'sc\\_catalog'\n - Value: A translated value\n7. For that category, make sure there is an entry in the sys\\_translated\\_text table with the following:\n - Document: Category sys id\n - Field name: **Title**\n - Language: Italian\n - Table name: 'sc\\_category'\n - Value: A translated value\n8. Switch to the Italian session.\n9. Open to the /esc portal.\n10. Search for the catalog item from before.\n\n Expected behavior: The corresponding facet filters under 'Categories' and 'Catalogs' should be translated into the Italian values provided.\n\n Actual behavior: The facet filters are still in English.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2029415\n\n | \n\nWhen creating a record, recordClassName becomes the parent class\n\n | \n\nAs a result, selecting the search result in the Service portal re-directs users to a malicious form.\n\n | \n\n1. Open sc\\_cat\\_item\\_guide list /sc\\_cat\\_item\\_guide\\_list.do%3Fsysparm\\_clear\\_stack%3Dtrue.\n2. Create a new record with the following:\n 1. Catalogs: Technical Catalog\n 2. Category: Services\n3. Ensure the 'Category' is selected from 'Recent selections'.\n4. Open the AI Search Preview with the following:\n 1. Search Application: 'ESC Portal Default Search Application\n 2. Card View: Raw\n 3. Output search words: the word you input on 2.\n5. Notice the result is 'searchResults': ... 'recordClassName': 'sc\\_cat\\_item', when it should be 'sc\\_cat\\_item\\_guide'.\n6. Update the record created in step 2.\n7. Search in AI Search Preview again.\n\n Observe that the values have been updated correctly: 'searchResults': ... 'recordClassName': 'sc\\_cat\\_item\\_guide'.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2033435\n\n | \n\nTSTranslationReference loads all sys\\_translated rows for a field instead of filtering to the indexed record's value\n\n | \n\nWhen indexing a record that has a **Reference** field pointing to a table whose **Display** field is a translated\\_field type, TSTranslationReference calls TranslationUtil.getTranslatedFieldValues\\(\\), which queries sys\\_translated with only name= table and element= field – no VALUE filter. This loads all translations for every value of that field across all records.\n\n | \n\n1. Have a large sys\\_translated table with 50k+ rows for a single table/field combination.\n2. Enable a language plugin.\n3. Index a record that has a **Reference** field pointing to a table whose **Display** field is a translated\\_field type. For example, a table referencing a question where the question\\_text is translated\\_field.\n\n Observe that index events take 5s to 8s each, and the message at occurs, 'QueryWarning: 'Large Table' on sys\\_translated with query name=<table>^element=<field> \\(no value filter\\).'\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2050402\n\n | \n\nImprove search relevancy for the Hybrid search on portal for 'OR' mode with a matching threshold of 80%\n\n | \n\nBy default, the search is performed in 'AND' mode for Hybrid search on portal, which is ignoring the q.threshold parameter completely.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2052168\n\n | \n\nNo\\_answer Genius Result is streamed intermittently\n\n | \n\nA Genius Result rarely shows, but it should not show at all.\n\n | \n\n1. Navigate to /sp.\n2. Search for something that gives a no\\_answer result, like 'baseball world series'.\n\n Observe that a Genius Result rarely shows. It should not show at all.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2058047\n\n | \n\nIndexing with multiple semantic indexing configurations with the same name on different models isn't working\n\n | \n\nWhen multiple semantic index configurations are created on the same datasource with the same **Semantic** field name but different embedding models, only the first configuration is loaded into the active **Semantic index** field cache. Subsequent configurations are silently ignored, so ingestion and search only use one embedding model for that field. Only one embedding model is used for indexing and search when multiple semantic index configurations share the same **Semantic** field name. Additional configurations with the same **Semantic** field name are not visible in getSemanticIndexFieldMapping\\(\\). No error or warning is logged when the duplicate-name configurations are skipped. Thus, multi-embedding model support for a single **Semantic** field is broken. Configurations are silently lost during cache population. This affects ingestion, search, and any callers that rely on getSemanticIndexFieldMapping\\(\\).\n\n | \n\n1. Create two active ais\\_semantic\\_index\\_configuration records on the same datasource with the same semantic\\_field\\_name but different embedding\\_models values.\n2. Add valid component fields via ais\\_semantic\\_component\\_field for each record and set a valid semantic\\_snippetization\\_configuration.\n3. Flush the datasource object cache \\(AisConfigurationCacheManager.flushDatasourceObjectCache\\(\\)\\).\n4. Call AisConfiguration.get\\(\\).getSemanticIndexFieldMapping\\('kb\\_knowledge','kb\\_knowledge'\\).\n\n Observe that only one SemanticFieldConfiguration is returned for semantic\\_search and the other is silently dropped.\n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2070763\n\n | \n\nImpersonation for RAGRetrivalAPI isn't required\n\n | \n\nThis feature isn't required anymore. Going forward, it will be implemented in a different way. It is currently behind ais\\_admin role but requires other impersonation checks which are missing currently.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073296\n\n | \n\nAdd handlers to convert labels for the field types 'Table Name' and 'Field Name'\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073297\n\n | \n\nSearchability Tracer for detailed ACL and User Criteria diagnostics API\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073298\n\n | \n\nSearch Evaluation application\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073301\n\n | \n\nDiagnostics API for searchability\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073303\n\n | \n\nCatalog enrichment for Glide AIS\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073307\n\n | \n\nExpanding the **Search signal** fields logged in glide AIS\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2073308\n\n | \n\nCatalog enrichment for glide AIS\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAI Search \\(Glide\\)\n\n PRB2076604\n\n | \n\nExpose glide.ais.query.server\\_side\\_reranker\\_enabled in BP0 for reranker to be enabled by default\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Search for Service Portal\n\n PRB1998368\n\n | \n\nAI Search in Enhanced Chat's full page experience throws a console error\n\n | \n\nThe error, 'Uncaught TypeError: \\(\\(n.event.special\\[g.origType\\] \\|\\| \\{\\}\\).handle \\|\\| g.handler\\).apply is not a function : js\\_includes\\_sp\\_libs.jsx at HTMLDivElement.dispatch' occurs in the console.\n\n | \n\n1. Open the 'Assistant Designer' page for Now Assist in Virtual Agent.\n2. Enable Enhanced Chat.\n3. Open the full page experience for Employee Center portal.\n4. Open the /esc portal.\n5. Select the **Search box** or search anything in the typeahead search widget.\n\n Observe console error, 'Uncaught TypeError: \\(\\(n.event.special\\[g.origType\\] \\|\\| \\{\\}\\).handle \\|\\| g.handler\\).apply is not a function : js\\_includes\\_sp\\_libs.jsxat HTMLDivElement.dispatch.'\n\n |
| \n\nAI Search for Service Portal\n\n PRB2062818\n\n | \n\nThe sparkle Otto icon in a portal search input has an incorrect color when Enhanced Chat is turned on\n\n | \n\nThe sparkle Otto icon before the input placeholder is not visible because it is same color as the background.\n\n | \n\n \n\n |
| \n\nAI Search\n\n PRB1893398\n\n | \n\nAttempting to recreate a scenario where entries in the search term is empty in the sys\\_search\\_event table\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Search UX\n\n PRB2072005\n\n | \n\nThe fix for PRB1935844 was overwritten during a merge\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAI Search UX\n\n PRB2073716\n\n [KB3148324](https://hi.service-now.com/kb_view.do?sysparm_article=KB3148324)\n\n | \n\nFor non-admin users, search results and suggestion navigation on portals are redirecting to platform view\n\n | \n\nAfter upgrading to Australia Patch 5 or Zurich Patch 12, non-admin users performing a search on a portal \\(for example, /esc\\) experience incorrect navigation. Selecting a regular search result or a suggested search result opens the record in the platform view rather than within the portal.\n\n | \n\nScenario 1:\n\n 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12.\n2. Log in as a non-admin user.\n3. Perform a search on a portal, such as /esc or /sp.\n4. Select the regular search result that is returned.\n\n Observe that the record opens in platform view instead of the portal.\n\n Scenario 2:\n\n 1. Upgrade an instance to Australia Patch 5 or Zurich Patch 12.\n2. Log in as a non-admin user.\n3. Enter a search term on a portal, such as /esc or /sp, without submitting the search.\n4. Select a suggested search result in the typeahead drop-down list.\n\n Observe that the record opens in platform view instead of the portal.\n\n |
| \n\nAnalytics Data API\n\n PRB2002190\n\n | \n\nThe error log should be suppressed in a prefetch job\n\n | \n\nThe user is getting the error log, 'com.glide.rest.domain.ServiceException: Invalid configuration in their syslog daily at an interval of 15 minutes. This is a cause of concern as the error logs are frequent and does not give complete information to the user to stop them.\n\n | \n\n1. Open any Zurich instance.\n2. Open the syslog table.\n\n Observe that there is a message containing 'com.glide.rest.domain.ServiceException: Invalid configuration.'\n\n |
| \n\nAnalytics Data API\n\n PRB2019716\n\n | \n\nMultiple elements from a single filter can't be applied to an 'COUNT DISTINCT' or 'AVERAGE' indicator with 'Show filter as separate series'\n\n | \n\nWhen multiple elements are selected and applied from a single filter to a visualization based on an automated indicator, the filter is not applied. The 'Network' tab in the developer console shows, 'Indicator does not support multi-element aggregation'. This should not occur for automated indicators. This issue only occurs if the 'facts' table is a database view.\n\n | \n\n1. Create a PAR dashboard.\n2. Add a line visualization with the base instance indicator, 'Number of over-due incidents' as the data source.\n3. Add a filter with 'Indicators' as the filter source type, and 'Assignment Group' as the indicator breakdown.\n4. Under 'Data to filter,' add 'Indicators with Assignment Group breakdown'.\n5. Select two elements from the filter and apply it.\n\n Observe that the filter is not applied, in the 'Network' tab in the developer console, and an error occurs.\n\n |
| \n\nAnalytics Data API\n\n PRB2029673\n\n | \n\nData Visualization Library quick-access cards return '0' under the 'Bookmarked' scope when the grid sees bookmarks correctly\n\n | \n\nOn the Data Visualizations Library page, the quick-access cards display 0 when the Bookmarked type-choice filter is applied, even when the grid below correctly shows the bookmarked vizes. The same card filter without the Bookmarked scope returns the correct count.\n\n | \n\n \n\n |
| \n\nAnalytics Data API\n\n PRB2050497\n\n | \n\nThe report.view events are generated with the wrong sys\\_id and are erroring out in Australia\n\n | \n\nThese events seems to be created from the Platform Analytics Dashboard home page.\n\n | \n\n1. Open an instance.\n2. Navigate to the sysevent table\n3. Use the filter conditions, 'Queue is report\\_view'.\n4. Notice the state is 'error'.\n5. Check the instance column.\n\n Notice that the sys\\_id's are not 32 characters, and from the 'Report' view, events process jobs logging the event have an error due to an invalid reference.\n\n |
| \n\nAnalytics Export API\n\n PRB1971222\n\n | \n\n'Omit if no records' isn't honored for score visualizations\n\n | \n\nIf the record count is zero for the visualization, the email with the exported data visualization PDF should not be generated when the **Omit if no records** checkbox is checked.\n\n | \n\n1. Create a data visualization of the type 'score', 'gauge', or 'dial'.\n2. Add a data source and conditions such that the record count is zero. For example, add a condition like 'active is true and active is false' which will make the record count zero.\n3. Save the data visualization.\n4. Schedule the export of data visualization to a PDF.\n5. Enable the **Omit if no records** checkbox.\n6. Select **Send now** from the 'Scheduled export' page.\n\n Expected behavior: The email shouldn't be generated when the record count is zero for the visualization.\n\n Actual behavior: The email gets generated even though the **Omit if no records** checkbox was selected.\n\n |
| \n\nAnalytics Export API\n\n PRB2057980\n\n | \n\nThe visualization creator is not able to select existing highlight value configurations\n\n | \n\nThe visualization creator couldn't select a highlighted value configuration because the visaualization creator role doesn't have read access for the sys\\_ux\\_highlighted\\_value\\_config table.\n\n | \n\n1. Create a highlight value configuration for an incident table as an admin user.\n2. Create a list visualization \\(viz\\_creator role\\).\n3. Select the table as 'incident'.\n4. Enable the fetch highlighted value.\n5. Search for the highlight configuration created above.\n\n Observe that no result is returned in highlight value dropdown list, even though the the visualization creator should be able to read and use existing highlight value configurations.\n\n |
| \n\nAPI Access Policies\n\n PRB2065453\n\n | \n\nThe RESTAPIAccessScopeRepo map overwrite loses required authentication scopes when two sys\\_api\\_access\\_scope records share the same API signature\n\n | \n\nA 403 'User Not Authorized' error occurs.\n\n | \n\n1. Install and activate both ServiceNow Otto for Document Voice and Dynamic Guidance applications.\n2. Confirm both sys\\_api\\_access\\_scope records are active for the SNGenerativeAI API path sn\\_generative\\_ai/extensions, with all apply-all flags \\(apply\\_all\\_methods, apply\\_all\\_resources, apply\\_all\\_versions\\) set to 'true'.\n3. Call GET /api/sn\\_generative\\_ai/extensions/live-llm-configuration?solutionCapability=smartdocs\\_voice\\_qna with the Document Voice token.\n\n Observe that if the Dynamic Guidance Authentication Scope record loads last into the RESTAPIAccessScopeRepo's map, the call returns the error, '403 User Not Authorized - Missing required api access scope: Dynamic Guidance Auth Scope'.\n\n |
| \n\nApplication Manager\n\n PRB2022268\n\n [KB3156065](https://hi.service-now.com/kb_view.do?sysparm_article=KB3156065)\n\n | \n\nThe application manager sys\\_app\\_version displays duplicate records for the same application and version, which is causing the app to be 'Installation blocked'\n\n | \n\nAs part of the AI testing, it's been observed that the app installations are blocked. The sys\\_app\\_version displays duplicate records for the same application. This causes the app installations to be blocked, despite the app versions being available as well as the license checks having successfully completed.\n\n | \n\n1. Navigate to an instance.\n2. Navigate to App Manager.\n3. Open any app \\(e.g. sn\\_ai\\_itsm\\_cont\\) which is licensed and validated on CI \\(usageanalytics\\) prod, but has yet showed 'Not Licensed'.\n4. Select **Install**.\n5. It just fails with 'Installation blocked' on that app itself.\n6. Open sys\\_app\\_version table.\n7. Check the app/scope id.\n\n Expected behavior: It should have only 1 record for that app and a specific app version.\n\n Actual behavior: It has multiple records for the same app and app version.\n\n |
| \n\nApplication Manager\n\n PRB2056916\n\n | \n\nSkip a license-blocked status for all dependencies in DependencyProcessor\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nApplication Manager\n\n PRB2074238\n\n | \n\nNow Assist to Otto Rename for Application Manager\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAppointment Booking\n\n PRB1992532\n\n | \n\nThe 'Appointment Booking Select' widget fails to load for the French language \\(i18n\\) due to an AngularJS Lexer error\n\n | \n\nWhen the system language is set to French, the appointment booking slot selection widget does not load. The sn-appointment-booking-select widget fails to render, and console errors are observed. As a result, booking slots are not displayed.\n\n | \n\n1. Impersonate as system administrator.\n2. Change the language to normal French.\n3. Open the page '/esc?id=appointment\\_booking'.\n4. Select any reason and appointment type..\n\n Notice that the appointment booking slot selection widget is not loading.\n\n |
| \n\nAsset Management\n\n PRB2069476\n\n | \n\nLet asset managers review and confirm extracted contract metadata in a 'Playbook' tab so that they can ensure accuracy before saving to the contract record\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2037251\n\n | \n\nUpdate interactions post-identification and authentication\n\n | \n\nThe 'Interactions' table has only 'Guest' resolved. It should have the user reference resolved post-identification and authentication.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2066684\n\n | \n\nMatch KB identification phone numbers are ignoring special characters\n\n | \n\nQuestions with the category 'phone number' aren't matched against formatted stored phone numbers during voice agent identification flow.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2072957\n\n | \n\nEnhance telemetry for Authentication Factors\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAuthentication Factors\n\n PRB2074233\n\n | \n\nSMS OTP Authentication for human-assisted voice interactions\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nAuthentication\n\n PRB2037962\n\n | \n\nThe MCP Server registration with the Client Credentials grant fails when created via AI Agent Studio\n\n | \n\nWhen registering an MCP Server in AI Agent Studio using the Client Credentials grant type \\(manual registration\\), the form doesn't get submitted. The same MCP server registration works correctly when the Connection & Credential alias is created manually outside AI Studio on the same instance. It also works correctly when the flow is exercised via Postman/curl directly against the MCP server's '/token' endpoint. The Authorization Code grant type continues to work end-to-end through AI Studio.\n\n | \n\n1. Log in to an instance.\n2. Navigate to **AI Agent Studio** > **Settings**.\n3. Select **Manage MCP Servers**.\n4. Select **New** to add a new MCP server.\n5. Enter the MCP URL.\n6. Select **Manual Registration**for Client Registration Type.\n7. Select **Client Credentials**for Grant Type.\n8. Select **Client Secret Post**for Token Authentication Method.\n9. For Client ID, enter 'svc\\_oodp\\_dataaccess'.\n10. For Client Secret, enter a valid secret.\n11. For Auth Scopes, enter 'openid'.\n12. Enter the token URL.\n13. Select **Add**.\n\n Expected behavior: The MCP Server registers successfully, like it does for Authorization Code grants and for manually created Connection & Credential aliases.\n\n Actual behavior: The form doesn't get submitted. The **Add** button is blocked until the authentication URL is provided, which ideally would not be required for the Client Credentials grant type.\n\n |
| \n\nAutomated Test Framework \\(ATF\\)\n\n PRB2038798\n\n | \n\nCannot read the properties of the undefined \\(reading 'message'\\) after upgrading to Australia\n\n | \n\nThe sys\\_processor\\_0af16f2d5363101034d1ddeeff7b12b6.xml redirects requests to a new UI page. However, this new UI page introduced in the Australia release is not supported by ATF's 'Navigate to module' step. It is relying on the gsft\\_main to load the g\\_form on the page. This breaks the custom logic to get the g\\_form on the page, and errors occur in the console.\n\n | \n\n \n\n |
| \n\nAutomated Test Framework \\(ATF\\)\n\n PRB2053799\n\n | \n\nText and cosmetic changes for ServiceNow Otto\n\n | \n\n \n\n | \n\n \n\n |
| \n\nAutomated Test Framework \\(ATF\\)\n\n PRB2054701\n\n [KB3147951](https://hi.service-now.com/kb_view.do?sysparm_article=KB3147951)\n\n | \n\nA 'Host CPU Load Critical' alert is caused by ATF Scheduler jobs with a large amount of sys\\_atf\\_modified\\_record\\_m2m records generated\n\n | \n\nATF Tests that cause a large number of modified records \\(stored in the sys\\_atf\\_modified\\_record and sys\\_atf\\_modified\\_record\\_m2m tables\\) cause high application server CPU usage as well as high memory usage. When users check to see if a test can run now, they attempt to first acquire exclusive access to all necessary records. If the list of modified records is very large, then users can spend a lot of time trying to determine if the test can run now, and this can cause high CPU usage on the application server and high memory usage in the application node.\n\n | \n\n \n\n |
| \n\nBenchmarks\n\n PRB1989154\n\n | \n\nBenchmarkClientUtil.constructPayload fails to fetch data for Global-scope PA Scorecards\n\n | \n\nRunning the background script shows that the PAScorecard.query\\(\\) does not return results for Global-scope indicators, causing constructPayload to fail. For benchmarked indicators that exist in the Global scope, the constructPayload method fails to fetch PAScorecard details and returns 'null'. Because the PAScorecard records are not retrieved, the Global-scope indicators are not included in the upload payload, and scores are not uploaded to the central instance. As a result, instances do not receive benchmark scores for these indicators.\n\n | \n\n \n\n |
| \n\nCache\n\n PRB2025917\n\n | \n\nQuery Cache metrics aggregator do not delete data older than 14 days\n\n | \n\nThe property 'glide.query\\_cache.aggregate\\_metrics.retention\\_days' controls how many days old data should be deleted from the 'qc\\_instance\\_metric' table when the job runs.\n\n | \n\n \n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2017688\n\n | \n\nNew RCAs from the Knowledge Center to HR Core to use Open Prompt\n\n | \n\nThe Advanced Knowledge Editor page in HR Agent Workspace is being used, and contains Open Prompt, which is interactable and helps create an articles using Gen AI. For the Open Prompt to work without any issues, new RCAs are required.\n\n | \n\n1. Activate the Knowledge Recommendation plugin and Article Optimization plugin.\n2. From the Knowledge Management properties, enable the ECE.\n3. Create an article from the related list of any HR case.\n4. Add a link in the article.\n\n Observe that there are RCAs from the Knowledge Center to HR Core.\n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2039604\n\n | \n\nThe HR L1 Specialist is missing Restricted Caller Access records from the installation\n\n | \n\nAfter installing the HR L1 Specialist on a zbooted Australia instance, Restricted Caller Access records were created from ZTSD and Now Assist AI Agents scopes to the HR Core scope which that prevent the specialist from completing its tasks.\n\n | \n\n1. Create a new instance or zboot an existing one.\n2. Upgrade the instance to Australia.\n3. Install the HR L1 Specialist along with all required dependencies for the HRSD product.\n4. Configure the HR L1 Specialist.\n5. Assign the specialist to a 'Ready' HR Case.\n\n Observe the Restricted Caller Access table to attempting to find the generated RCA records.\n\n |
| \n\nCase and Knowledge Management for HR Service Delivery\n\n PRB2070954\n\n | \n\nRCAs are required for predict and transfer usecases\n\n | \n\nThere should be RCAs for the new tool call when the sys\\_id isn't mentioned in the objective when invoking the 'Predict HR Service and Transfer' case workflow.\n\n | \n\n \n\n |
| \n\nCase Management\n\n PRB2057866\n\n | \n\nTarget tables are missing required tracking fields for multi-case creation\n\n | \n\nFor multi-case creation, the target records do not have the required tracking fields to capture **Template Item** and **Template Execution**. As a result, the created Case and Case Task records cannot be fully tracked with associated Template item and execution. To support multi-case creation, the fields **Template item** and **Template Execution** need to be added to the sn\\_customerservice\\_case and sn\\_customerservice\\_task tables.\n\n | \n\n \n\n |
| \n\nChange Management\n\n PRB2061984\n\n | \n\nOn insert, if a template writable value is modified, the modification is overwritten by the template value\n\n | \n\n \n\n | \n\n1. Create a template for the normal mode which sets the **Short Description** field to **Test value from template**.\n2. Run the scripts background.\n\n Observe that the **Short description** is set to the template value, not the value set during the creation.\n\n |
| \n\nColumn Level Encryption\n\n PRB2006384\n\n | \n\nAttachments from the sn\\_si\\_incident table are created with a different hash\n\n | \n\nThere appears to be some sort of unique hashing algorithm applied only to the sn\\_si\\_incident table. Due to this hashing algorithm, attachments are being duplicated in the remote process sync feature.\n\n | \n\n1. Attach an attachment to any table other than \\[sn\\_si\\_incident\\].\n2. Attach an attachment to the \\[sn\\_si\\_incident\\].\n\n Notice that when comparing the two hashes, two unique hashes are generated for the same file.\n\n |
| \n\nCommunities\n\n PRB2003810\n\n | \n\nViews in Event Content are displaying as '2,147,483,648'\n\n | \n\nWhen the event is created through the platform, the events view count is showing high number in the community portal.\n\n | \n\n1. Attempt to create an event from the platform \\(sn\\_communities\\_event table\\).\n2. Open the same event from the communities portal.\n3. Go back and open the same event again.\n\n Notice that the views are showing as 2,147,483,648.\n\n |
| \n\nContent Experiences\n\n PRB2036902\n\n | \n\nA change in HRApprovalAccessUtilsSNC causes schedule content approvals to fail without a new RCA\n\n | \n\n \n\n | \n\n1. Provision an instance with HR Core installed.\n2. Create a schedule with approvers such that one rejection rejects the whole schedule.\n3. Approve any number of the requests, saving at least one \\(0:X-1\\).\n4. Reject one.\n\n Expected behavior: The schedule is rejected as normal.\n\n Actual behavior: An RCA error occurs.\n\n |
| \n\nContent Experiences\n\n PRB2054955\n\n | \n\nRCA for app-ex-ai-agents in Content Publishing for the getRefRecord directive\n\n | \n\n \n\n | \n\n \n\n |
| \n\nCore UI Interactive Filters\n\n PRB2073810\n\n [KB3154499](https://hi.service-now.com/kb_view.do?sysparm_article=KB3154499)\n\n | \n\nSelecting the pie chart legend/label does not filter visualizations correctly\n\n | \n\nThe pie visualization acting as an interactive filter does not apply the filter correctly when the legend items are selected.\n\n | \n\n1. Navigate to the classic reporting module.\n2. Create a new visualization with the following:\n - Table: Incident\n - Type: Pie\n - Group by: Assignment group\n3. Save it.\n4. Navigate to the classic dashboard module.\n5. Create a new dashboard.\n6. Add the '\\{Debug\\}' interactive filter.\n7. Add the visualization created in step 2.\n8. Edit the visualization widget.\n9. Select **Act as interactive filter**.\n10. Select any legend item.\n\n Expected behavior: It should show a filter condition being applied.\n\n Actual behavior: The 'Debug' homepage filters shows no filters applied.\n\n |
| \n\nCore UI Responsive Dashboards\n\n PRB2034505\n\n [KB3085059](https://hi.service-now.com/kb_view.do?sysparm_article=KB3085059)\n\n | \n\nA Platform Analytics \\(PA\\) dashboard overview can't load any dashboards\n\n | \n\nIf all of the following conditions are met, the dashboard doesn't appear on the 'All' tab of PA dashboard 'Overview' page.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nCustomer Service Case Action Status\n\n PRB2011771\n\n | \n\nKeep the 'Major Case' related list consistent in app-csm-action-status and app-major-issue-management\n\n | \n\nIf users reinstall or upgrade app-csm-action-status again after Major Case is installed, the related list on Major Case is different. The newly added-in app-major-issue-management is gone.\n\n | \n\n \n\n |
| \n\nCustomer Service Core\n\n PRB2037285\n\n | \n\nThere's slowness on every page/action for the account executive persona in a perf instance\n\n | \n\nWhen trying to perform any action in a perf environment with the account executive persona, the user observes slowness from one to two minutes.\n\n | \n\n \n\n |
| \n\nCustomer Service Management\n\n PRB2062954\n\n | \n\nCreating knowledge from a case doesn't populate the **kb\\_issue** field\n\n | \n\nThe **kb\\_issue** field is mapped in the Advanced Field Mapping of the CSM Table Map 'Case KCS Article'. It is expected to populate the first comment from the case.\n\n | \n\n1. Set the system property sn\\_customerservice.enable\\_knowledge\\_kcs to 'true'.\n2. Open a case that contains one or more comments.\n3. Select **Create Knowledge**.\n\n Expected behavior: The **kb\\_issue** field of the newly created Knowledge article is populated with the first comment from the case.Actual behavior: The **kb\\_issue** field of the newly created Knowledge article is left blank.\n\n |
| \n\nDatabase Persistence - Data Access\n\n PRB2051225\n\n [KB3141251](https://hi.service-now.com/kb_view.do?sysparm_article=KB3141251)\n\n | \n\nGlideAggregate and Platform Analytics pivot fails with 'must appear in the GROUP BY clause' when grouping or sorting by a translatable field in a non-English language\n\n | \n\nThe pivot shows 'No data available.'/'Aucune donnee disponible.' instead of the data. The node log shows com.glide.db.GlideSQLException with the PostgreSQL error, 'ERROR: column 'sc\\_cat\\_item3.name' must appear in the GROUP BY clause or be used in an aggregate function.'\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB1971093\n\n | \n\nOne-time update/delete job conditions shouldn't contain Javascript\n\n | \n\nFrom PRB1866906, if the query brought over from the table view includes javascript, the query must be removed entirely. Potential for data loss may occur.\n\n | \n\n1. Log in as user with the admin role.\n2. Browse to /incident\\_list.do?sysparm\\_query=caller\\_id=javascript:gs.getUserID\\(\\).\n3. Hover over the 'Opened' column.\n4. Select the **Column Options** \\(3 vertical dots/hamburger menu\\).\n5. Select **Data Management** > **Delete all with preview**.\n\nNotice that the user is navigated to a screen showing the sys\\_dm\\_delete record.\n\n\n Expected behavior: The condition is retained, but the javascript/dynamic content in the conditions should not be stored. It should be 'caller\\_id=the current user's id>'.\n\n Actual behavior: The condition is removed since it includes javascript, as it is in PRB1866906.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2015145\n\n | \n\nThe bulk archive restore performs poorly with the columnar archive table\n\n | \n\n \n\n | \n\n1. Test the bulk archive restore with a clone instance.\n2. Migrate ar\\_incident to the columnar storage.\n3. Run bulk restore with a list of ar\\_incident records.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2015146\n\n | \n\nDocumentIDTableFixer queries perform poorly against the columnar archive tables\n\n | \n\n \n\n | \n\n1. Migrate ar\\_incident to the columnar storage.\n2. Run the DocumentIDTableFixer job.\n\n Observe the check query performance.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2017978\n\n | \n\nThe RefCopy job experiences performance issues for columnar archive tables\n\n | \n\nThe slow query table shows the average SQL execution time.\n\n | \n\nEnable the 'Retain reference' option for the incident table's archive rule.\n\n Notice that when checking the slow query table, the user can find the average SQL execution time.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2025948\n\n | \n\nExclude raptordb columnar tables from the clone\n\n | \n\n \n\n | \n\nClone from the source to the target with the columnar table plugin active.\n\n Expected behavior: Archive tables are not cloned.\n\n Actual behavior: Archive tables are cloned.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2036545\n\n | \n\nArchive table mutability causes performance problems\n\n | \n\nThe data should be immutable other than archive destroy. However, certain operations cause mutability, such as cascade delete or reparenting.\n\n | \n\nArchive some data into an archive table, like ar\\_u\\_table1.\n\n Expected behavior: The data is immutable other than archive destroy.\n\n Actual behavior: Certain operations, such as cascade delete or reparenting, cause mutability.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2039000\n\n | \n\nArchiveResolver doesn't work with the columnar archive table\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2039435\n\n | \n\nThe URC could run slowly when executing the row count estimation on the columnar table\n\n | \n\n \n\n | \n\n1. Install Live Archive on an instance.\n2. Offload a large amount of data.\n3. Create a URC rule like for sys\\_flow\\_plan\\_context\\_binding which has a document table reference.\n\n Expected behavior: The URC runs as expected.\n\n Actual behavior: The row count estimation query is very slow.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2039436\n\n | \n\nThe URC could run slowly when executing row count estimation on the columnar table\n\n | \n\n \n\n | \n\n1. Install Live Archive on an instance.\n2. Offload a large amount of data.\n3. Create a URC rule for sys\\_flow\\_plan\\_context\\_binding which has a document table reference.\n\n Observe the time it takes for the URC to run.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2039845\n\n | \n\nThe sys\\_attachment\\_doc\\_columnar table is not created in the gateway DB when the sys\\_attachment group is on a gateway\n\n | \n\nThe sys\\_attachment\\_doc\\_columnar table is created in the primary DB instead of the gateway DB, and the list view shows no records.\n\n | \n\n1. Set up an instance with a gateway database configured for the sys\\_attachment table group \\(for example, sys\\_attachment, sys\\_attachment\\_doc, and sys\\_attachment\\_doc\\_v2 are routed to the gateway DB\\).\n2. Activate the com.glide.data\\_management.columnar\\_attachments plugin on the instance..\n3. Verify that the sys\\_attachment\\_doc\\_columnar table gets created in the gateway DB.\n\n Expected behavior: The sys\\_attachment\\_doc\\_columnar table is created in the gateway DB, the same as sys\\_attachment and sys\\_attachment\\_doc, and the list view displays the migrated records.\n\n Actual behavior: The sys\\_attachment\\_doc\\_columnar table is created in the primary DB instead of the gateway DB. However, the list view shows 0 records because the platform queries the gateway DB where the sys\\_attachment group is routed, but the data resides in the primary DB.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2051706\n\n | \n\nThe sys\\_service\\_endpoint\\_attribute exclusion rule is in the incorrect package\n\n | \n\nThe sys\\_service\\_endpoint\\_attribute clone exclusion record is in the s3\\_standard package.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2054270\n\n | \n\nTable cleaner performance issues on columnar archive tables\n\n | \n\n \n\n | \n\n1. Create a table cleaner rule targeting a columnar archive table.\n2. Execute the table cleaner job.\n\n Observe whether the rule is deactivated or not, and if no records are cleaned.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2055841\n\n | \n\nThe archive DDL sync default-value back-fill times out on columnar archive tables\n\n | \n\nThe archive table default-value back-fill does not complete.\n\n | \n\n1. Have a source table \\(for example, sn\\_customerservice\\_case\\) with a columnar archive table \\(ar\\_sn\\_customerservice\\_case\\) that contains a meaningful number of rows.\n2. Add a new column with a non-null default to the source table such as, auto\\_created\\_case \\(boolean, default '0'\\).\n\nNotice that ArchiveDDLChangeListener fires and synchronizes the schema change onto the archive table. Because the column has a default, DBUtil.updateDefaultValues back-fills existing rows via the chunk-copy path.\n\n3. Observe the per-chunk statement.\n\n Expected behavior: Adding a defaulted column to a source table with a columnar archive table should complete the archive schema sync without timing out. The back-fill should either avoid the sys\\_id-range chunked UPDATE strategy on columnar archive tables or use a columnar-appropriate approach.\n\n Actual behavior: Each chunk UPDATE runs a full column-segment scan \\(no sys\\_id index on the columnar archive table\\), executes serially one chunk at a time, and times out. The archive table default-value back-fill does not complete.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2057672\n\n | \n\nGlobal search performance issue with columnar archive tables\n\n | \n\n \n\n | \n\n1. Install Live Archive on an instance.\n2. Offload a large amount of data, including some task or problem tables.\n3. Ensure glide.ui.text\\_search.enable\\_archive\\_fallback\\_number\\_search is set to the base instance value \\(true\\).\n4. Search for a task or problem number in the global search box.\n\n Expected behavior: The result should come back quickly.\n\n Actual behavior: There could be a long delay when the record has been offloaded due to point lookup with columnar/offloaded tables.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2059007\n\n | \n\nPrevent Data Management jobs from operating on columnar archive tables\n\n | \n\nIn both scenarios, the DM Delete Job is attempting to run, but it's too slow\n\n | \n\nScenario 1:\n\n 1. Create a Data Management Delete Job targeting a columnar archive table.\n2. Execute the job.\n\n Expected behavior: The DM Delete Job should not run on columnar archive tables, it should be skipped.\n\n Actual behavior: The DM Delete Job is attempting to run and it's too slow.\n\n Scenario 2:\n\n 1. Create a Data Management Update Job targeting a columnar archive table.\n2. Execute the job.\n\n Expected behavior: The DM Update Job should not run on columnar archive tables, it should be skipped.\n\n Actual behavior: The DM Update Job is attempting to run and it's too slow.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2059138\n\n | \n\nIncrease columnar table migration thesholds\n\n | \n\n \n\n | \n\n1. Set up an Australia instance with Live Archive.\n2. Let the migration start and monitor the archive tables being migrated to columnar.\n\n Expected behavior: Only large archive tables \\(>10 GB\\) should migrate, reducing the amount of columnar queries in the future.\n\n Actual behavior: Tables as small as 100 MB are being migratedl, which leads to a lot of columnar queries with minimal space benefits.\n\n |
| \n\nDatabase Persistence - Data Management\n\n PRB2061236\n\n | \n\nLeverage local tables to locate archive records in Global Search\n\n | \n\n \n\n | \n\n1. Install the Live Archive on an instance.\n2. Offload a large amount of data, including some task or problem tables.\n3. Search for a task or problem number which has been offloaded in the global search box.\n\n Expected behavior: The result should come back.\n\n Actual behavior: The result doesn't come back.\n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2017435\n\n | \n\nThe cypher graph query generates an invalid SQL JOIN ordering when the 'Before Query' rule injects dot-walk conditions on extended tables\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2051763\n\n | \n\nThe C2R error occurs for all the WDF queries\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2052676\n\n | \n\nCache flushes are triggered, even when the cache is not used/populated\n\n | \n\nThe number of cache flush messages for the table 'cmdb\\_rel\\_ci' is in the 80 million+ range every hour. In a way, it's making 80 million inserts into the sys\\_cache\\_flush table. 'cmdb\\_rel\\_ci' is paired with 'graph\\_cmdb\\_rel\\_type\\_cache'. The cache graph\\_cmdb\\_rel\\_type\\_cache isn't enabled, but the cache pairing is still in a static block and is active.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - Graph\n\n PRB2064975\n\n | \n\nThe sub graph time increased ~200ms\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDatabase Persistence\n\n PRB1962784\n\n | \n\nProperty glide.db.alter\\_large\\_table\\_threshold can't be set large enough\n\n | \n\nWhen creating a table with greater than 2,147,483,647 rows, if glide.db.alter\\_large\\_table\\_threshold is set to 4B, it will not upgrade. The following error occurs on the upgrade: 2025-11-08 12:48:19 \\(829\\) worker.1 worker.1 txid=730511129301 DictionaryXMLParser \\*\\*\\* WARNING \\*\\*\\* Skipping table: cmdb\\_rel\\_ci \\(too large to alter\\).\n\n | \n\n \n\n |
| \n\nDatabase Persistence\n\n PRB2052093\n\n | \n\nThere's a three-way deadlock between Preferences, TableDescriptor, and TableRotationExtension, which causes node restarts in production\n\n | \n\nPreferences.get\\(\\) holds the Preferences.class monitor across a database query and table descriptor lookup, while the AMB cluster synchronizer thread holds a TableRotationExtension instance monitor across a field normalization engine call. The two lock-acquisition orders are inverted, producing a classic AB-BA deadlock that starves any thread attempting to call Preferences.get\\(\\) until one of the two owners is killed by the deadlock sweeper.\n\n | \n\n \n\n |
| \n\nDatabase Persistence\n\n PRB2075293\n\n [KB3150595](https://hi.service-now.com/kb_view.do?sysparm_article=KB3150595)\n\n | \n\nAfter the upgrade to Australia Patch 5, auto-increment columns are failing inserts with the duplicate\\_key error\n\n | \n\nAustralia Patch 5 \\(AP5\\) introduced a change to how certain database auto-increment sequences are managed. Under specific conditions, this change can cause the sequence used to generate new record identifiers to become invalid or out of sync with the database. When this occurs, attempts to create new records may fail. As a result, transient state records may not be created as expected in tables with the auto-increment field. This impacts many functional areas relying on the sequence record to track orders of states, logs or messages. This defect fix is included in the weekly patch due to its severe impact on multiple major functionalities across the platform.\n\n | \n\n \n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2038995\n\n | \n\nUnable able to join the DF table with the native UUID to other tables that use string and native UUID as a reference key\n\n | \n\nThis problem address the two failing reference scenarios for 'DF table with native UUID PK > DF table with varchar\\(32\\) UUID PK' and 'DF table with native UUID > Glide table with native UUID'.\n\n | \n\nScenario 1:\n\n 1. On a instance with postgres as primary db, create a glide table.\n2. Add a column with the the type 'UUID'.\n3. Add the attribute df\\_reference=true for the column to be used as reference key.\n4. Create multiple records for the table.\n5. Generate UUID values on the column.\n6. Open an external database that has UUID as a native datatype, such as postgres.\n7. Create a table that has the type 'UUID'.\n8. Add UUID values created in the glide table to here.\n\nNotice that in the WDF hub map, the remote table is defined in the external database. The UUID column is marked as a reference to the glide table with the UUID column as primary key.\n\n9. Open the list view as an admin user.\n\n Expected behavior: The reference column should have links available for the user to access the records of the reference table.\n\n Actual behavior: The links to the glide table are not available.\n\n Scenario 2:\n\n 1. Create two tables in a remote postgres database.\n\nNotice that the first table \\(the reference table\\) should have a column with varchar\\(32\\).\n\n2. Generates UUID values without the hyphens.\n\nNotice that the second table \\(the driving table\\) should have a column with type 'UUID'.\n\n3. Copy the same values from the previous table with hyphens.\n4. In the WDF hub create the reference table and assign the varchar uuid column as primary key.\n5. Create the driving table and have the native uuid column as type reference.\n6. Open the driving table's list view.\n\n Expected behavior: The list view should load and references should work with no issues\n\n Actual behavior: The list view fails to load and fails in trino with the error 'Cannot apply operator: uuid = varchar\\(32\\)'.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2040034\n\n | \n\nIn Australia, all database columns that start with a number have 'yy\\_' added to the start of the name, causing a syntax error\n\n | \n\nWhen querying a table in the Australia release and the DB column starts with a number, it adds a 'yy\\_' to the SQL query. This break the collection of data and making a list view show nothing. Error: 'Syntax Error or Access Rule Violation detected by database \\(ERROR: column x\\_snc\\_potatofarm\\_0\\_farmers0.yy\\_1stname does not exist. Hint: Perhaps you meant to reference the column 'x\\_snc\\_potatofarm\\_0\\_farmers0.1stname'. Position: 259\\)'.\n\n | \n\n1. Create a scoped app.\n2. Create a table.\n3. Create some data on that table.\n4. Add a column that name starts with a number.\n5. Navigate back to the list view.\n\n See that its blank, but the count displays that there's records.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2076449\n\n | \n\nA node can't start if there's a 'Formula' field on sys\\_user\n\n | \n\nThe instance node will fail to restart if there is a formula‑calculated field on the User \\[sys\\_user\\] table. When the issue occurs, the node does not restart and logs a stack overflow error. The failure occurs during the platform's schema loading phase, preventing the instance from coming online and impacting all users.\n\n | \n\n1. Create a custom field on the sys\\_user table with similar customized configuration:\n - Name: u\\_test\\_field\n - Type: String\n - Max length: 40 Select Advanced View\n2. In the 'Related lists' tab under 'Calculated Value', set the following:\n - Calculated: true\n - Calculation Type: Formula\n - Formula: if\\(name>'''', ''Not empty'',''Empty''\\)\n3. Select Submit.\n4. Restart the node.\n\n Expected behavior: The node restarts without issue.\n\n Actual behavior: The node is not able to restart and throws a stack overflow error.\n\n |
| \n\nDatabase Persistence - WDF\n\n PRB2080099\n\n | \n\nLeadingDigitLegacyColumnIT fails on Australia\n\n | \n\nOn an Australia patch, running against Oracle, any column rename involving a column whose logical name begins with a digit fails with: 'ORA-00957: duplicate column name'. This is because the generated statement collapses the source and target names into the same identifier.\n\n | \n\n \n\n |
| \n\nData Fabric Table Glide Services\n\n PRB2051005\n\n | \n\nDisable catalog caching as the default for ZCC\n\n | \n\nThis data gets cached to the sys\\_dcg\\_ext\\_meta table.\n\n | \n\nCreate a new connection in the ZCC hub and view tables.\n\n Expected behavior: There should be no data in the sys\\_dcg\\_ext\\_meta table since catalog caching should not be on by default.\n\n Actual behavior: There is data.\n\n |
| \n\nData Fabric Table Glide Services\n\n PRB2073262\n\n | \n\nImplement Personal Authentication support for Zero Copy Connectors \\(ZCC\\)\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Management Console\n\n PRB1996837\n\n | \n\nThe Data Management Console does not account for partitions while calculating table size when a table is partitioned\n\n | \n\nWhen sys\\_attachment\\_doc is partitioned, the Data Management Console for attachments reports only the size of the parent table, not the sum of all partitions. This causes the displayed table size to appear significantly smaller than the actual disk usage.\n\n | \n\n1. Open a MariaDB Instance.\n2. Migrate it to Raptor with partitioning the sys\\_attachment\\_doc table.\n3. After the migration check the attachment table on the instance.\n\n Notice that the report for attachments only reports the size of the parent table, and not the entire sum of all partitions.\n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2039058\n\n | \n\nReal time anonymization \\(RTA\\) for child tables separate from parent tables\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2063909\n\n | \n\nAuto-install applications are based on a user license once the instance is provisioned\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Privacy \\(Classic\\)\n\n PRB2072955\n\n | \n\nBring Your Own \\(BYO\\) PII Anonymization Service Integration \\(for ServiceNow Otto\\)\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Product Backend Services\n\n PRB2054113\n\n | \n\nAdd the Java plugin for semantic search and clustering of texts\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nData Product Backend Services\n\n PRB2064387\n\n | \n\nImplement sys\\_data\\_product and sys\\_data\\_product\\_content writes as a native Java scriptable API instead of a self-HTTP REST bridge\n\n | \n\nBoth 'sys\\_data\\_product' and sys\\_data\\_product\\_content' are global tables owned by the com.glide.dataproduct Java plugin, not by sn\\_data\\_product. The platform's cross-scope GlideRecord write wall blocks direct writes to these tables from our scope.\n\n | \n\nIn the sn\\_data\\_product scope, attempt to write to sys\\_data\\_product or sys\\_data\\_product\\_content via direct GlideRecordSecure insert/update.\n\n Observe the platform refuses the write with the message, 'Security restricted: Create operation against 'sys\\_data\\_product' from scope 'sn\\_data\\_product' has been refused due to the table's cross-scope access policy.'\n\n |
| \n\nDependency Views\n\n PRB1882781\n\n | \n\nThe relationship between nodes always shows up as 'Depends on::Used by' even though the relationship in cmdb\\_rel\\_ci is different for Dependency View\n\n | \n\nThe relationship between nodes is not defined as it is in cmdb\\_rel\\_ci.\n\n | \n\n1. Open the ngbsm\\_script table.\n2. Create a new record with the script.\n3. Navigate to **Dependency Views** > **View Map**.\n4. Search for 'Blackberry'.\n5. On the filter panel, select the entry created in step 1 from the 'Dependency Type' dropdown list.\n\n Notice the loaded map, and that all the relationships show as 'Depends on::Used by' instead of the actual relationship between the nodes as defined in cmdb\\_rel\\_ci.\n\n |
| \n\nDev-API Authentication\n\n Dev-API Authentication\n\n | \n\nAbility to issue a correlation token that can be exchanged for access token\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDeveloper Sandboxes\n\n PRB2028151\n\n [KB3122033](https://hi.service-now.com/kb_view.do?sysparm_article=KB3122033)\n\n | \n\nNodes are failing to upgrade during self-scheduled upgrades\n\n | \n\nAfter an upgrade, not all app nodes that were previously hosting a sandbox are upgraded. The nodes aren't in an error state and look okay. In Upgrade Monitor, users see that the node is actually not upgraded. This can happen on any upgrade and only impacts nodes that are hosting a sandbox. It can be seen in the logs that the upgrade process is checking the version of the instance and ignoring without updating the node. It's leaving a few of the nodes to fail to get upgrade. However, the change does not reflect that and it says it was successful.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nDeveloper Sandboxes\n\n PRB2054240\n\n | \n\nThe scheduler claim mutex \\(sys\\_mutex\\) isn't sandbox-aware and forces DSB nodes to contend for a cluster-wide lock, causing scheduled-job pickup delay\n\n | \n\n \n\n | \n\n1. On a multi-node instance \\(50+ nodes\\), turn on Developer Sandboxes.\n2. Create at least 20-30 sandboxes.\n3. Multiple isolated sys\\_triggers should exist in the sandboxes.\n4. Pull stats.do?include=otel.scheduler\\* on the sandbox's node.\n\nObserve that claim\\_lock\\_time averages above one second \\(expected ~13ms\\), jobs\\_lateness averaging 300+ seconds, and worker capacity used is very low.\n\n5. Compare against a controller node on the same instance.\n\n Observe that claim\\_lock\\_time is still elevated but jobs\\_lateness stays within a few seconds, because base nodes don't pin an entire platform triggers on one node.\n\n |
| \n\nDevOps Change Velocity\n\n PRB2052626\n\n | \n\nGetRefRecord scoping bypass for the 6.2.1 release\n\n | \n\n \n\n | \n\n \n\n |
| \n\nDirectSQL\n\n PRB2031660\n\n | \n\nThere's missing DBView support for Data Interfaces and DirectSQL\n\n | \n\nThe initial code was done in a branch that didn't have the dbview baseline code. This finishes it in dataaccess, which now has both needed components dbviews in directsql and data interface.\n\n | \n\n \n\n |
| \n\nDirectSQL\n\n PRB2073934\n\n | \n\nSupport data interfaces with function fields in Direct SQL\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2009621\n\n | \n\nSub account \\(LP\\) deletion strategy is retiring logical datacenter CIs\n\n | \n\nThe deletion strategy 'Mark as Retired' on the 'cmdb\\_ci\\_cloud\\_service\\_account' table for the pattern 'Azure - Sub Account \\(LP\\)' is updating the cmdb\\_ci\\_azure\\_datacenter records to the 'Retired' status. This update on the cmdb\\_ci\\_logical\\_datacenter record is triggering the business rule 'Cascade Update LDCs Resource State' which is updating the child resources contained in this datacenter to the 'Retired' status.\n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2056121\n\n | \n\nThere are incorrect or missing SNMP OID classifications, which result in SAN / fibre switches being classified as 'IP Switch'\n\n | \n\nIncorrect/ missing SNMP OID Classifications which result SAN / Fibre switches classified as IP Switch\n\n | \n\nDiscover SAN / Fibre switches.\n\n Observe that these are classified as 'IP switch'.\n\n |
| \n\nDiscovery\n\n PRB2058910\n\n [KB3156347](https://hi.service-now.com/kb_view.do?sysparm_article=KB3156347)\n\n | \n\nTypo in the script in Sensor SNMP\n\n | \n\nClassify 'his' instead of 'this.'\n\n | \n\n \n\n |
| \n\nDiscovery\n\n PRB2059465\n\n | \n\nDiscovery patterns fail to launch for sub-accounts/datacenters when glide.discovery.retire\\_stale\\_accounts is turned on\n\n | \n\nIn Cloud Discovery, schedules configured to discover all sub-accounts under a main account, with enabling glide.discovery.retire\\_stale\\_accounts and glide.discovery.cdu.auto\\_refresh\\_sub\\_accounts\\_and\\_ldcs , Discovery patterns fail to launch for sub-accounts/datacenters \\(only the service account discovery launches\\).\n\n | \n\n \n\n |
| \n\nDocument Intelligence Unified Backend\n\n PRB2073306\n\n | \n\nDocIntel glide support\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDocument Management Services\n\n PRB2039067\n\n | \n\nSmart redaction with redaction codes and notes for documents\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDocument Management Services\n\n PRB2056919\n\n | \n\nSmartDocs enablement in UI16 and ServicePortals\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nDocument Viewer\n\n PRB2038307\n\n | \n\nThe smart document skill doesn't invoke the agent and doesn't render anything on Now Assist Panel\n\n | \n\nThe **Ask Now Assist** smart document button doesn't work as expected. When the user selects the button, it opens the NAP, but it just shows the topics and doesn't load the summarization of the document.\n\n | \n\n1. Navigate to **Contract Workspace** > **Default List** > **List** > **Contract Requests** > **All**.\n2. Open any contract request.\n3. Select the 'Contract Documents' tab.\n4. Select **Preview Document**.\n5. Select a document to preview, which opens it in a new tab.\n6. Select the **Ask Now Assist** button, which opens the NAP.\n\n Observe that the NAP loads for some time and then shows topics. Selecting the button again just loads the topics.\n\n |
| \n\nDocument Viewer\n\n PRB2056915\n\n | \n\nSupport in document viewer for the doc to voice agent\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nEdge Encryption\n\n PRB1998926\n\n | \n\nThe Edge command-line installation doesn't work on java 21\n\n | \n\n \n\n | \n\n1. Ensure java 21 is running.\n2. Download the command-line install artifact.\n3. Run the command line install artifact to install edge proxy.\n\n Expected behavior: Edge proxy installs successfully.\n\n Actual behavior: An error occurs indicating java 17 is required.\n\n |
| \n\nEdge Encryption\n\n PRB2051049\n\n | \n\nThe edge decryption job doesn't decrypt audit records when an FE encryption configuration is active\n\n | \n\nDuring edge-to-cle migration, the user needs to run an edge decryption job while the CLE EFC is active. However, because it does not currently audit CLE fields, the check to see if the column is audited returns false. If the user has edge encrypted audit data, the migration \\(decryption\\) job will not migrate the audit data.\n\n | \n\n1. Inactivate the edge configuration.\n2. Configure the field with an active EFC so that it will be field encrypted.\n3. Schedule the edge decryption job, ensuring that historical data will be processed.\n4. Run the job.\n\n Expected behavior: The execution records \\(sys\\_encryption\\_job\\_execution\\) are created for the audit table's new/old value fields.\n\n Actual behavior: No execution records are created for audit table fields.\n\n |
| \n\nEmployee Profile\n\n PRB2011497\n\n | \n\nThere's a dot-walking RCA error when moving from the 'Learning' scope to the 'Employee profile' scope\n\n | \n\nAn attempt to dot-walk to table sn\\_employee\\_profile present in the 'Employee profile' scope from the 'Learning' scope was blocked. The reference field employee belongs to the sn\\_lep\\_challenge table. The operation type was: GET\\_REF\\_RECORD.\n\n | \n\n \n\n |
| \n\nEmployee Profile\n\n PRB2021875\n\n | \n\ngetRefRecord\\(\\) changes for Opportunity Marketplace \\(OPM\\) and TD Core in Employee Profile\n\n | \n\n \n\n | \n\n \n\n |
| \n\nEmployee Taxonomy Framework\n\n PRB2073966\n\n | \n\nImplement extension point for IKBViewAs in glide-taxnomy\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nEncryption\n\n PRB1982641\n\n [KB2977274](https://hi.service-now.com/kb_view.do?sysparm_article=KB2977274)\n\n | \n\nScan checks are missing null checks, causing the instance scan to fail\n\n | \n\nAfter running the 'Insecure GlideRecord Calls', if the getFunctionCallParamters\\(\\) function brings back an empty object, the instance scan fails.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nError Framework\n\n PRB2035967\n\n | \n\nThe **Reset** button doesn't work and the 'Refined Codes' section displays error codes with error\\_count=0\n\n | \n\nThe **Reset** button on the error card list component doesn't work. When the user selects the button, the filters should be reset and the same errors should be displayed. Instead, 'No actions needed' appears and no error cards are visible. Additionally, in the Discovery Admin Workspace, the 'Refined Codes' section displays error codes that have an error\\_count of 0. These zero-occurrence entries represent errors that have been fully ignored \\(captured in error\\_ignored\\_count only\\) and carry no actionable significance for the user. Showing these entries pollutes the list with noise, making it harder for users to focus on error codes that actually require attention.\n\n | \n\nScenario1:\n\n 1. Provision an instance with:\n - The 'Error Framework' plugin \\(com.glide.error\\_framework\\) installed.\n - At least one source application registered in sys\\_error\\_appl.\n - Errors ingested and aggregation run \\(so sys\\_error\\_code\\_stats has records with error\\_count > 0\\).\n2. Add the error card list component to a new workspace on the 'Error Stats' page.\n3. Verify that errors are displayed.\n4. Apply a filter to enable the **Reset** button.\n5. Select the **Reset** button.\n\n Expected behavior: The filters are reset to defaults. The same errors are displayed.\n\n Actual behavior: 'No actions needed' appears. An empty state is shown, and no error cards are visible.\n\n Scenario 2:\n\n 1. Navigate to **Discovery Admin Workspace** > **Diagnostics** > **Errors**.\n2. Check the Refined Codes list.\n\n Expected behavior: Only refined codes with error\\_count > 0 are displayed in the Refined Codes list.\n\n Actual behavior: Refined codes with error\\_count = 0 are displayed in the list.\n\n |
| \n\nError Framework\n\n PRB2058704\n\n | \n\nAllow apps to define key labels for UI Builder components \\(configurable fieldLabels/columnList/sort-by\\)\n\n | \n\nConsuming applications should be able to define UI Builder component field labels as domain-specific terms rather than generic ones. For example, if a component has a 'key' or 'source' field, a user should be able to define the field label as 'IP Address' or 'Discovery Schedule' for clarity in their implementation. Additionally, column reordering should be allowed, and so should the action for dropdown list subsections and ordering.\n\n | \n\n \n\n |
| \n\nError Framework\n\n PRB2069719\n\n | \n\nSeparate the 'Error' and 'Context' actions in EF UI Builder \\(UIB\\) components\n\n | \n\nThe EF UIB error detail panel had a single combined 'Actions' dropdown list for both error-level and context-level actions. This splits them into two distinct split-buttons aligned with the redesign: 'Mark error as ' in the properties pane for error actions, and 'Actions' in the agent context pane for context actions. App teams can configure and order actions independently for each section.\n\n | \n\n \n\n |
| \n\nEvent Management\n\n PRB2053994\n\n | \n\nThere's a null pointer exception in AlertWorkNotesHandler .updateWorkNotesAnd SilentSaveOfClosedAlert\n\n | \n\nThe race condition causes the Null Pointer Exception in AlertWorkNotesHandler.updateWorkNotesAndSilentSaveOfClosedAlert.\n\n | \n\n \n\n |
| \n\nEvent Management\n\n PRB2060447\n\n | \n\nIntermittent JDBC error 'The column index is out of range' is caused by concurrent reuse of the shared QueryCondition instance\n\n | \n\nThis issue occurred because of the race condition.\n\n | \n\n \n\n |
| \n\nExternal Content Connectors Glide\n\n PRB2068960\n\n | \n\n'Item\\_label\\_rid' field is dropped for ais\\_high\\_security\\_admin users in SearchExternalContentQueryApi\n\n | \n\nThe field is absent from the response. If 'item\\_label\\_rid' is the only field requested, the response is empty entirely. The query to AIS is skipped because no fields survive the allow list intersection.\n\n | \n\n1. Log in as a user with the ais\\_high\\_security\\_admin role.\n2. Call SearchExternalContentQueryApi.search\\(\\) against an external content table, requesting the field **item\\_label\\_rid**.\n\n Observe that the field is absent from the response. If **item\\_label\\_rid** is the only field requested, the response is empty entirely. The query to AIS is skipped because no fields survive the allow list intersection.\n\n |
| \n\nExternal Content Connectors Glide\n\n PRB2073292\n\n | \n\nExecute the Direct AI Search query and display the raw result\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nExternal Content Connectors Glide\n\n PRB2073293\n\n | \n\nExtend scriptable API work to non-maintenance users\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nExternal Content Connectors Glide\n\n PRB2073294\n\n | \n\nThe filtered list of XCC are linked to a specific search profile, such as Janus\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nField Service Task Bundling\n\n PRB2064856\n\n | \n\nDynamic bundling creates unassigned bundles\n\n | \n\n \n\n | \n\n1. Verify that Dynamic Scheduling, Task Bundling, and Task Grouping plugins are active.\n2. Enable the sys\\_property 'com.snc.dynamic. scheduling.bundle\\_ before\\_scheduling'.\n3. Set the Task Grouping rules \\(Same Location\\) and policy.\n4. Create two work order tasks \\(WOT\\) in the draft.\n\n Notice that once the WOTs are moved to the 'Qualified \\(Pending Dispatch\\)' state, the tasks should be bundled using Dynamic Bundling and Dynamic Schedule the tasks automatically.\n\n |
| \n\nFlow Engine\n\n PRB2055858\n\n | \n\nAdd flow benchmarking tests to Australia code base to monitor flow engine performance improvements\n\n | \n\nThe user is unable to run standardized micro benchmarks in Australia.\n\n | \n\n \n\n |
| \n\nFlow Engine\n\n PRB2062691\n\n | \n\nAction Fabric flow complexity is insufficient for pricing estimation exercises\n\n | \n\nThe complexity\\_bucket attribute contains values grouped into bucket\\_0\\_10, bucket\\_11\\_50, and likely no other buckets.\n\n | \n\n1. Perform MCP requests on an instance with Action Fabric telemetry.\n2. View the Action Fabric telemetry via Clickhouse or logged data.\n\n Expected behavior: The exact complexity of the MCP flows are recorded.\n\n Actual behavior: The complexity\\_bucket attribute contains values grouped into bucket\\_0\\_10, bucket\\_11\\_50, and likely no other buckets.\n\n |
| \n\nFlow Engine\n\n PRB2073167\n\n | \n\nAdd new metric for flow runtime complexity called from non-mcp\n\n | \n\nThe system currently tracks metrics for flow runtime complexity. There is a need to add a new metric specifically for flows called from non-mcp.\n\n | \n\n1. Trigger a flow execution via a non-MCP channel \\(Browser/UI, Integration channel, Mobile, or any execution path that is not MCP\\).\n\nObserve that flow runtime complexity metrics are not being recorded with the granularity/buckets defined for non-MCP execution.\n\n2. Compare against expected bucket definitions: Bucket 1 \\(1-2\\) through Bucket 24 \\(1000+\\).\n\n Expected behavior: For all non-MCP execution paths \\(Browser/UI, Integration channels, Mobile, and any non-MCP path\\), flow runtime complexity metrics are recorded using the new, more granular bucket set, without affecting existing metrics.\n\n Actual behavior: No dedicated metric/bucket set exists for non-MCP execution paths.\n\n |
| \n\nFlow Engine\n\n PRB2073745\n\n [KB3154012](https://hi.service-now.com/kb_view.do?sysparm_article=KB3154012)\n\n | \n\nRevert the change to sys-property so users can enable full reporting for flow executions in production\n\n | \n\nUsers see a yellow message stating that action details have been removed according to the report retention policy, and cannot view the detailed flow execution information in production instances. This occurs after the platform change that forces the system property com.snc.process\\_flow.reporting.level to 'BASIC' on production, automatically reverting any attempt to set it to 'FULL'. As a result, new records in sys\\_flow\\_context ;are stored at the 'BASIC' level, limiting visibility of inputs, outputs, and step-by-step details.\n\n | \n\n \n\n |
| \n\nFlows \\(Family Channel\\)\n\n PRB2067258\n\n | \n\nFeature filtering fixes for new the Flow Designer\n\n | \n\nRead only/stop editing and Undo/Redo is supported.\n\n | \n\n \n\n |
| \n\nFlows \\(Family Channel\\)\n\n PRB2074948\n\n | \n\nAPIs for skills and agents are missing from Australia and are needed for the lit rework\n\n | \n\nTwo API's were made, one for skills and one for agents, they return an error message when the tables for those items don't exist.\n\n | \n\n1. Verify the availability of APIs for skills and agents.\n2. Confirm the correctness of the APIs for skills and agents.\n3. Select a skill name.\n4. Check if the **Workflow**, **Product**, and **Feature** fields are auto-populated in the 'Execute skill' actions.\n5. Verify that each skill and agent has a description available.\n\n Observe that the APIs for skills and agents are available and functioning correctly.\n\n |
| \n\nHermes \\(Family\\)\n\n PRB2051477\n\n [KB3152907](https://hi.service-now.com/kb_view.do?sysparm_article=KB3152907)\n\n | \n\nThe Hermes topic inspector falsely displays the 'unreadable messages' pop up\n\n | \n\nA modal alert was introduced in the Hermes Topic Inspector to handle unreadable messages – conditions such as unsupported compression types that cause a page crash. An issue has been identified where this modal triggers incorrectly due to the improper evaluation of the unreadable\\_messages flag, preventing users from inspecting topics even when no unreadable messages are present. As a result, users are unable to inspect Hermes topics despite no actionable error condition existing, resulting in unnecessary disruption to monitoring and troubleshooting workflows.\n\n | \n\n1. Open the Topic Inspector.\n2. View a topic with a large amount of messages.\n3. Set the timestamp to the maximum, such as 2 days prior to the current time.\n\n Observe that the 'unreadable messages' popup appears.\n\n |
| \n\nHermes \\(Family\\)\n\n PRB2057996\n\n | \n\nSetting 'hermes.kafka.disabled' to 'true' does not help to disable Hermes jobs such as 'Hermes Failover State Refresh Job'\n\n | \n\nThis issue causes huge loads of logs.\n\n | \n\n \n\n |
| \n\nHorizon iFrame Component\n\n PRB2074065\n\n | \n\nUsers get an error when trying to access the iFrame related configurations\n\n | \n\nUsers get the following error: 'Uncaught TypeError: Cannot read properties of null \\(reading 'parent'\\) at Object.\n\n | \n\n \n\n |
| \n\nHR e-signature\n\n PRB2035247\n\n | \n\nRCA for Content Experience\n\n | \n\nSpecifically, EEsign for getRefRecord directive.\n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB1970902\n\n | \n\n'Mark When Complete' is hardcoded in the Agent Workspace for HR Case Management for i18n\n\n | \n\n \n\n | \n\n1. Set up a testing environment.\n2. Install the French language pack \\(com.snc.i18n.french\\).\n3. Install sn\\_hr\\_agent\\_ws with demo data.\n4. Install sn\\_jny with demo data.\n5. Install com.sn\\_hr\\_lifecycle\\_events with demo data.\n6. Enable 'Playbook' in sn\\_hr\\_le\\_case records in the HR Agent Workspace.\n7. Create a sn\\_hr\\_le\\_case record.\n8. Navigate through the playbook until the user sees the 'Dispatch the Onboarding Swag' lane.\n\n Observe the string 'Mark When Complete' is hardcoded.\n\n |
| \n\nHR Service Delivery\n\n PRB2018687\n\n | \n\nThe 'Edit' button does not work for the Granular Delegation rule\n\n | \n\nThe record edits are not reflected even though the Granular Delegation rule was created.\n\n | \n\n1. Install the Granular Delegation Plugin.\n2. Create a Granular Delegation Rule.\n3. Save it.\n4. Use the **Edit** button to modify the user criteria to the delegate/delegator.\n\n Notice that after the edit, the record doesn't reflect the changes.\n\n |
| \n\nHR Service Delivery\n\n PRB2057715\n\n | \n\nZTSD dare RCAs\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2059123\n\n | \n\nRCAs in the 'Requested' state for HR case assistant and HR Case Creation agent\n\n | \n\n \n\n | \n\n1. Open an instance.\n2. Ensure there is no RCA for Source as 'Tool: Add comment to HR case'.\n3. Call the Unified Orchestrator.\n4. Ask the voice agent to look up an HR case.\n\nNotice that the agent asks for soft pin. After providing soft pin, the agent confirms that user is authenticated.\n\n5. Provide the number for HR case opened.\n\n Notice that when asked to add comments to case, there is an RCA. Another RCA is generated in the 'Requested' state the when user asks for case creation.\n\n |
| \n\nHR Service Delivery\n\n PRB2063926\n\n | \n\nSemantic index changes for HR Service and HR Case for predicting the HR Service\n\n | \n\n \n\n | \n\n \n\n |
| \n\nHR Service Delivery\n\n PRB2067282\n\n | \n\nGlideHTMLSanitizer is not callable from HR scoped applications\n\n | \n\n \n\n | \n\n1. From any scoped application \\(for example, sn\\_hrbp\\_hub\\), run it in a background script.\n\nObserve it fails because 'GlideHTMLSanitizer' is not defined.\n\n2. Retry it with global.GlideHTMLSanitizer.sanitize\\(...\\).\n\nObserve it also fails with SNC.GlideHTMLSanitizer.sanitize\\(...\\).\n\n3. Run the same call from the global scope.\n\n Observe that it succeeds and returns the correctly sanitized HTML.\n\n |
| \n\nHR Service Delivery\n\n PRB2071645\n\n | \n\nAdd required RCAs for CBS AINPX in HR Scope\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nIDR - Scheduled Replication\n\n PRB1937502\n\n | \n\nThe Scheduled Replication 'Percent Complete' doesn't take updated records into account \\(%\\)\n\n | \n\nThe percentage from the Scheduled Replication 'Percent Complete' is inaccurate. For example, it says '66.56%' for 'Percent Complete' despite the status being 'Completed'.\n\n | \n\n1. Perform a scheduled replication test with inserts and updates.\n2. Update a third of the records inserted.\n\n Expected behavior: Scheduled Seeding Replication Requests show the percentage 100% when complete.\n\n Actual behavior: Only the actual number of records sent over seems to be reflected in the percentage.\n\n |
| \n\nInbound API Integration Usage Framework\n\n PRB1988771\n\n [KB3082116](https://hi.service-now.com/kb_view.do?sysparm_article=KB3082116)\n\n | \n\nIPAccessListFilter handling for malformed IP addresses\n\n | \n\nInbound REST API calls coming through proxy servers \\(x-forwarded-for header with multiple IP's\\) or malformed IP address can sometimes fail in Zurich and Australia instances.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nIndicator Management\n\n PRB2052998\n\n | \n\nWhen the indicator library name ='None' with no data, sometimes data displays intermittently on some columns and rows\n\n | \n\nThe Indicator Library shows the indicators name as 'None' and shows no other data.\n\n | \n\n1. Impersonate ITIL user.\n2. Navigate to **Platform Analytics** > **Indicators**.\n\n Observe that all rows show as 'None'\n\n |
| \n\nInstall Base Management Store\n\n PRB2059577\n\n | \n\nInstall base items and sold products should support RAC fallback mechanism\n\n | \n\nThe functions \\_skipFetchEntities and getQRfallbackRoles should be overridden in CSMRelationshipServiceSNC in CSMRelationshipService \\_InstallBaseRelatedParty to allow this fallback mechanism.\n\n | \n\n \n\n |
| \n\nInstance Clone \\(Family\\)\n\n PRB2074591\n\n | \n\nUpdate for glide version and Clone Admin Console store app\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nInstance Data Replication \\(IDR\\)\n\n PRB1994565\n\n | \n\nIf the shared key is expired before activating the consumer set, consumer set cannot be activated\n\n | \n\nThe message, 'Shared key corresponding to shared key id %s is not found.' is triggered when the shared key expires before activating the consumer set.\n\n | \n\n1. Set idr.shared.key.expiration to 300,000 on the producer side \\(5 minutes\\).\n2. Create a producer replication set,.\n3. Activate it.\n4. Create a consumer replication set.\n5. Approve the subscription from the producer side.\n6. Let the shared key expire from the producer side.\n7. Attempt to activate the consumer.\n\n Expected behavior: There is a mechanism to detect when shared key has expired, similar to auto-shared key recovery when the consumer shared key is missing.\n\n Actual behavior: The producer is not able to send the CONSUMER\\_ACTIVATION payload due to mismatched shared keys between the producer and consumer.\n\n |
| \n\nIntegration Hub\n\n PRB2033476\n\n | \n\nAfter upgrading to Australia, password actions such as 'Change User Password' and 'Reset User Password' fail\n\n | \n\nThe password actions 'Change User Password' and 'Reset User Password' are failing from Microsoft Active Directory v2 Spoke.\n\n | \n\n \n\n |
| \n\nInternationalization Features\n\n PRB2027846\n\n | \n\nChanging the country in the user preferences doesn't check the user's permission\n\n | \n\n \n\n | \n\n1. Log in to an instance.\n2. Create an ACL removing write access to sys\\_user.country for users without the 'admin' role.\n3. Impersonate a user without the admin role.\n4. Open the 'User Preference panel'.\n5. Change the country preference.\n6. Stop the impersonation.\n\n Observe whether the value for sys\\_user.country was changed for the user.\n\n |
| \n\nKey Management Framework \\(KMF\\) for Platform Encryption\n\n PRB2058369\n\n [KB3140571](https://hi.service-now.com/kb_view.do?sysparm_article=KB3140571)\n\n | \n\nMidserver is unable to fetch credentials after upgrading to Zurich or Australia\n\n | \n\nIn certain versions, there's a Unified Secrets Gateway \\(USG\\) service for credential management. During the upgrade to those versions, a system trigger script is designed to automatically execute and populate the sys\\_secret\\_identity\\_group\\_member table with the MID Server identity group mappings required for USG authentication. However, this trigger fails to complete successfully, leaving the table incompletely populated. As a result, the MID Server can't authenticate with USG and fails to retrieve credentials.\n\n | \n\n1. Upgrade an instance from a version where USG doesn't exist to a Zurich or Australia version where USG exists.\n2. Check if sys\\_secrets\\_identity\\_group\\_member is populated with all entries from ecc\\_agent.\n\n Expected behavior: All entries from ecc\\_agent are present in sys\\_secret\\_identity\\_group\\_member.\n\n Actual behavior: There are no entries in sys\\_secret\\_identity\\_group\\_member.\n\n |
| \n\nKnowledge Graph \\(Family\\)\n\n PRB2063201\n\n | \n\nAdd support for dynamic table lists in the KG Affinity API for affinity data loading\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB1975454\n\n [KB3151964](https://hi.service-now.com/kb_view.do?sysparm_article=KB3151964)\n\n | \n\nThe 'View article' link in Manager Hub is not working as expected for employee users\n\n | \n\nAfter selecting the article as an employee from the results, the article is empty because it the fields from the template article are not rendering.\n\n | \n\n1. Install the com.sn\\_ex\\_employee\\_center\\_pro plugin.\n2. Set the property 'glide.knowman.enable\\_view\\_as\\_user' to 'true'.\n3. Create a manager user.\n4. Add the 'knowledge\\_view\\_as' role to the manager user.\n5. Create an employee user.\n6. Add the 'knowledge' role to the employee user.\n7. Link the manager user as a manager to the employee user.\n8. Create a new knowledge base.\n9. Add the 'user with knowledge role' user criteria to both 'canRead' and 'canContribute'.\n10. Create a new template article \\(template article, kb\\_template\\_what\\_is etc\\) under that new KB.\n11. Link that article to any topic from the 'Connected content' related list.\n12. Create a password for the manager.\n13. Log in with the userid and password.\n14. Open /esc?id=ec\\_view\\_as\\_results.\n15. Select the employee user.\n16. Search for that newly created article.\n17. Open the article from the results.\n\n Notice that the article content is empty, as it is not rendering any fields of the template article.\n\n |
| \n\nKnowledge Management\n\n PRB1989283\n\n | \n\nm2m\\_kb\\_to\\_ block\\_history\\_list displays the state of article as 'outdated' instead of 'published'\n\n | \n\nThe state should be 'Published' and not 'Outdated'.\n\n | \n\n1. Create an article which has a block in it.\n2. Checkout the article, create a new version and publish the article.\n3. Check the state of the latest article.\n\n Notice that it says 'Outdated' instead of published in m2m\\_kb\\_to\\_block\\_history\\_list.\n\n |
| \n\nKnowledge Management\n\n PRB2000452\n\n | \n\nThe 'Edit' button isn't visible in any of the previous versions of the articles in workspaces\n\n | \n\nAfter upgrading Zurich, the **Edit** button does not appear when users open an outdated Knowledge article in the kb\\_view page of any workspace. The article is displayed in read-only mode and authors, KB owners, or admins cannot switch to the full record view to make changes. This prevents necessary updates to legacy articles.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2034151\n\n | \n\nBack link on Portal \\(Widget: HRM Back Button\\) doesn't work in certain situations\n\n | \n\nIrregular execution of events triggered while typing search inputs.\n\n | \n\n1. Apply the update set.\n2. Navigate to **Knowledge search**.\n3. Type a name in the client search.\n\nNotice that the results are displayed.\n\n4. Clear the results.\n5. Wait 1 second.\n6. Type in another result.\n\n |
| \n\nKnowledge Management\n\n PRB2037824\n\n | \n\nThe pop-up to select relevant tasks doesn't appear after selecting 'Yes, draft with Now Assist' from the knowledge base\n\n | \n\nWhen creating a new article from a knowledge base, the base instance Now Assist Skill 'Generate Knowledge Article' / 'KB generation' doesn't show the pop-up to select incidents.\n\n | \n\n1. Make all article templates inactive.\n2. 2. Navigate to **Knowledge** > **Administration** > **Knowledge Bases**.\n3. Open any knowledge base record from the list view.\n4. Scroll down to the 'Knowledge' related list.\n5. Select **New** from the related list to create a new knowledge article.\n\nObserve that it redirects to the knowledge article form. A pop-up appears, asking if the user would like to use AI to draft the article.\n\n6. Select **Yes, draft with Now Assist**.\n\nIf any language plugin is available, observe that a pop-up appears with the title 'Select options - language options are configured in Now Assist admin'. Otherwise, it shows 'Draft with Now Assist momentarily'.\n\n7. Select **Continue**.\n\n Observe that it returns the user to the form. There's no pop-up to select relevant tasks, and no article is drafted.\n\n |
| \n\nKnowledge Management\n\n PRB2058947\n\n | \n\nUpdate versions for the base instance Knowledge Management apps to include Australia and Zurich fixes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2060905\n\n | \n\nUpdating versions for the base instance Knowledge Management apps to include Australia and Zurich fixes\n\n | \n\nThere are fixes in app-knowledge-center, app-knowledge-gen-ai, app-kb-uib, and sn-enhanced-content-editor.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2061644\n\n | \n\nSupport KB creation through the import feature processAttachment\\(\\) API\n\n | \n\nIt returns JSONObject and causes the error, 'Error: Evaluator.evaluateString\\(\\) problem: java.lang.SecurityException: Method returned an object of type JSONObject which is not allowed in scope sn\\_ia\\_config. JSONObject parsing is not possible in scoped app.'\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2073317\n\n | \n\nCreate a new article type in the UI16 flow\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2073319\n\n | \n\nUpgrading NAKM, KC, KCInWorkspaces and ECE to Brazil\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2076447\n\n | \n\nThe Auto-fix plugin update blocks the Australia Patch 5m upgrade in loadsim release testing\n\n | \n\nThe plugin upgrade thread handling becomes stuck in an error loop triggered by a null pointer. It never exits or advances, leaving the upgrade 'hung'. This happens when the upgrade plugin loader reaches the knowledge center update that adds in the auto-fix and auto-fix enable property.\n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2077445\n\n | \n\nUpdating versions for the base instance Knowledge Management apps to include Australia and Brazil fixes\n\n | \n\n \n\n | \n\n \n\n |
| \n\nKnowledge Management\n\n PRB2083241\n\n | \n\nTrue up for Australia and Brazil\n\n | \n\n \n\n | \n\n \n\n |
| \n\nLifecycle Events\n\n PRB2013721\n\n | \n\nThe **Resume Case** UI Action doesn't work as expected for certain users\n\n | \n\nWhen a user with the admin role accesses an HR case but is restricted by a COE Security Policy, the **Resume Case** UI action does not restore the activity set to the 'Running' state. Instead, the activity remains in the awaiting\\_trigger state, preventing the case workflow from continuing.\n\n | \n\n \n\n |
| \n\nList Administration\n\n PRB2024845\n\n | \n\nThe ListHighlighted ValueService cache key is missing highlightedValueConfigId, and causes cache collisions between requests with different configuration IDs\n\n | \n\nThe highlighted values in the Workspace list render intermittently. It works right after cache.do then stop after a few minutes, because ListHighlightedValueService's cache key omits highlightedValueConfigId. There are multiple requests for the table, workspace, and fields but different \\(or null\\) configuration IDs collide on the shared static cache. As a result, whichever request populates the cache first determines the result for all subsequent requests until the entry expires.\n\n | \n\n1. Create a sys\\_highlighted\\_value for table=incident, field=state, with a simple condition where the state is not empty, color=blue, and status=positive.\n2. Create sys\\_ux\\_highlighted\\_value\\_config 'A' with M2M-linked to the highlighted value through sys\\_ux\\_m2m\\_highlighted\\_value\\_config.\n3. Create sys\\_ux\\_highlighted\\_value\\_config 'B' with no M2M link to any highlighted value.\n4. Navigate to **cache.do** to flush the caches.2. Navigate to sys.scripts.do.\n5. Run the script.\n\n Expected behavior: It should be 'CONFIG\\_B=0, CONFIG\\_A=1'.Actual: Notice that it is 'CONFIG\\_B=0, CONFIG\\_A=0,' and A reuses B's cached empty result.\n\n |
| \n\nList Administration\n\n PRB2033285\n\n | \n\nThere's an Australia update issue with roles not appearing in the 'Table/workspace' view\n\n | \n\nHaving a dictionary entry with 'Use Dependent Field' turned on and pointing to a boolean dictionary entry on the same table causes the values on the list to not display.\n\n | \n\n \n\n |
| \n\nList Administration\n\n PRB2036908\n\n [KB3097895](https://hi.service-now.com/kb_view.do?sysparm_article=KB3097895)\n\n | \n\nA list fails to load when a catalog variable with a reference qualifier on a large table is added as a column\n\n | \n\nThe page times out. An error occurs reading, 'Sorry, an error occurred or this page isn't available'.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nList Administration\n\n PRB2039348\n\n | \n\nIn the List view, the first choice is shown and is not the selected choice for the lookup select box variable in the workspace\n\n | \n\nIrrespective of whatever option the user might have selected, it will show the first choice in the workspace List view.\n\n | \n\n \n\n |
| \n\nList Column Menu\n\n PRB2077157\n\n | \n\nGrouping by any field displays a '$c66360ca901b4a5387c58a30a4270909\\[ListProperties.getGrandTotalRows\\(\\)\\] total $c66360ca901b4a5387c58a30a4270909\\[ListProperties.getTitle\\(\\)\\]' on the list view\n\n | \n\nThis issue was observed in an Australia instance.\n\n | \n\n1. On an Australia instance, open sc\\_cat\\_item.list.\n2. On the 'Short description' column, right click on the 3 dots.\n3. Use 'Group By Short description.'\n\n Notice on the top banner, there is a $c66360ca901b4a5387c58a30a4270909\\[ListProperties.getGrandTotalRows\\(\\)\\] total $c66360ca901b4a5387c58a30a4270909\\[ListProperties.getTitle\\(\\)\\] getting displayed at the top.\n\n |
| \n\nList Controller\n\n PRB1989084\n\n | \n\nIn Platform Analytics, a loading indicator appears in the mid-page of the scheduled export list after applying filters\n\n | \n\nIn the Scheduled Export List, when applying any filter, the loading indicator is displayed in the middle of the web page rather than at the top. As a result, users must scroll down to notice that the page is loading, which can cause confusion.\n\n | \n\n \n\n |
| \n\nList Controller\n\n PRB1990422\n\n | \n\nA relative timestamp \\(time ago\\) in a workspace's 'List' view doesn't refresh unless the record itself is updated\n\n | \n\nIn the Service Operations Workspace list view, the relative timestamp displayed under **datetime** fields, such as **Updated** and **Opened**\\) does not refresh when the user selects the **Refresh** button, unless the underlying record has been updated. This results in a stale relative time value being continuously displayed, even though the actual absolute timestamp shown above it is correct. The issue was validated on a base instance, confirming that no customizations were involved. This behavior causes confusion for agents who rely on relative time indicators when monitoring active incident lists.\n\n | \n\n1. Log in to a Zurich base instance with Service Operations Workspace enabled.\n2. Navigate to **Service Operations Workspace** > **Incidents** > **Open**.\n3. Identify any incident with visible **Updated** or **Opened** datetime fields.\n\nObserve the relative timestamp directly under the **datetime** \\(for example, '1m ago\\).\n\n4. Wait several minutes without modifying the incident.\n5. Select the **Refresh** button on the Workspace list view.\n\nObserve that the relative timestamp does not change, and it continues to show the original value \\(1m ago\\), even though more time has elapsed.\n\n6. Update the same incident record in the background by adding a comment.\n7. Return to the list.\n8. Select **Refresh** again.\n\n Observe that the relative timestamp updates to the correct value \\(2m ago\\).\n\n |
| \n\nList Filters\n\n PRB1982205\n\n | \n\nData visualizations don't translate to the selected language\n\n | \n\nThe data visualization column is displayed in English instead of Swedish. Only the left sidebar is translated into Swedish.\n\n | \n\n1. Provision an instance with the French language pack \\(com.snc.i18n.swedish\\) installed.\n2. Open Visualization Designer in Platform Analytics Workspace.\n3. Create a new visualization.\n4. Change the session language to Swedish.\n\n Observe that the column is displayed in English instead of Swedish. Only the left sidebar has been translated into Swedish.\n\n |
| \n\nLive Archive\n\n PRB2022491\n\n | \n\nThe count of records is missing before and after the columnar migration\n\n | \n\nThe log message is missing.\n\n | \n\n1. Open an Australia instance with the latest RaptorDB.\n2. Install Tier 2 Live Archive.\n3. Offload data to include attachments.\n4. Inspect the node queries.\n\n Expected behavior: There is a log message detailing the number of records in each table, and sys\\_attachment\\_doc\\_columnar before and after migration.\n\n Actual behavior: This is missing from logs.\n\n |
| \n\nLive Archive\n\n PRB2056631\n\n | \n\nThe two-pass sparse fetch on sys\\_attachment\\_doc\\_columnar forces a sequential scan, and not an indexed lookup. Pass 2 filters by sys\\_id even though the table is physically ordered by sys\\_attachment\n\n | \n\nDuring attachment downloads, the chunk row resolution against sys\\_attachment\\_doc\\_columnar performs a sequential scan instead of an indexed lookup. This adds latency to attachment reads that use the columnar \\(RaptorDB/S3-offloaded\\) attachment storage backend.\n\n | \n\n1. Ensure an attachment's chunks are stored in sys\\_attachment\\_doc\\_columnar with columnar/RaptorDB storage enabled.\n2. Download that attachment so that loadPrefix\\(\\)/chunk iteration resolves a sparse row on sys\\_attachment\\_doc\\_columnar.\n3. Capture DB query stats/timing for the resulting 'WHERE sys\\_id = ?' pass-2 query.\n\n Expected behavior: The pass-2 row fetch performs comparably to the same fetch against sys\\_attachment\\_doc \\(indexed lookup\\).\n\n Actual behavior: The pass-2 fetch against sys\\_attachment\\_doc\\_columnar performs a sequential scan because sys\\_id is not the table's primary\\_ordering column, causing measurable added latency, especially as the table/segment grows.\n\n |
| \n\nLive Connect \\(Server\\)\n\n PRB2038719\n\n | \n\nUpdate all server side 'SQL API' references to 'Live Connect'\n\n | \n\n \n\n | \n\n \n\n |
| \n\nLive Connect \\(Server\\)\n\n PRB2062273\n\n | \n\nAllow user accounts to access Live Connect\n\n | \n\nOnly service accounts were allowed to use Live Connect.\n\n | \n\n \n\n |
| \n\nMicrosoft Reconciliation\n\n PRB1980380\n\n | \n\nAn incorrect 'Bring your own license' \\(BYOL\\) unlicensed reason is provided when the setup does not have any relation to BYOL\n\n | \n\n \n\n | \n\n1. Create CIS Suite with different components, with the entitlement per processor.\n2. Create installs without any **Cloud** fields.\n3. Notice that there should not be any BYOL tags in the key value table.\n4. Run recon.\n\n Notice that the unlicensed reason is 'BYOL Not Supported for Per Processor Licensing on This Installation.'\n\n |
| \n\nMicrosoft Reconciliation\n\n PRB2039492\n\n | \n\nResource value for bug bash observations\n\n | \n\nThe PO line needs license metric changes on UI 16 same as alm\\_license. The description is missing for volume based LM configurations, and the license metric tier related list should not have a license metric configuration column.\n\n | \n\n \n\n |
| \n\nMID Server\n\n PRB2063491\n\n | \n\n'LinkedHashMap$Entry' objects connected to the LRU take a couple MB\n\n | \n\nThese objects are from 'ecc\\_queue\\_authorization\\_policy'.\n\n | \n\n1. Open a local instance.\n2. Connect to the MID Server.\n3. Create a heap dump.\n\n Notice that entries of 'LinkedHashMap$Entry' for ecc\\_queue\\_authorization\\_policy have over 3MB for each entry.\n\n |
| \n\nMID Server\n\n PRB2067544\n\n | \n\nScopedProcessFlowScriptSource.getSourceName\\(\\) returns display label 'Process Automation' instead of a valid table name, causing the invalid ScriptRecordDescriptor on the transaction\n\n | \n\n \n\n | \n\n1. Navigate to **Process Automation** > **Flow Designer**.\n2. Create a new Action \\(for example, 'Test Process Automation Table Name'\\).\n3. Add a script step.\n4. Save and publish the action.\n5. Select **Test**.\n6. Navigate to ecc\\_queue\\_authorization\\_policy.list.\n\n Expected behavior: The policy record has a valid initiator\\_table \\(sys\\_hub\\_step\\_instance\\) and the populated initiator sys\\_id.\n\n Actual behavior: The policy record has initiator\\_table = 'Process Automation' \\(which is invalid and not a real table\\), initiator = empty and scope = NA.\n\n |
| \n\nMobile Platform\n\n PRB2021795\n\n | \n\nThe checklist string value ampersand is saved as '&'\n\n | \n\n.\n\n | \n\n \n\n |
| \n\nMobile Platform\n\n PRB2033117\n\n | \n\nIn Now Agent, the work order task questionnaire is truncated if the questionnaire is more than 100 characters\n\n | \n\n.\n\n | \n\n1. Open the Now Agent App.\n2. Impersonate a user whose preferred language isn't English and a has work order task \\(WOT\\) questionnaire assigned to them.\n3. Select the **My work** option.\n4. Select the WOT.\n5. Take the questionnaire.\n6. Scroll through the queries.\n\n Observe that queries above 100 characters are truncated.\n\n |
| \n\nMulti-Instance Framework - Core\n\n PRB2063884\n\n | \n\nMIF Hermes doesn't refresh the cluster configuration when the local hermes\\_cluster\\_config has no primary or after a datacenter-rule change, causing stale/failed cluster resolution for remote owners\n\n | \n\nWhen instance A sends a MIF async message to instance B, it needs B's Hermes cluster details from datacenter and Kafka bootstrap servers. Instance A keeps a saved copy in the hermes\\_cluster\\_config table and reads it in HermesProducerClient.getClusterInfoSet. Today that method only calls B's live endpoint \\(/api/now/hermes\\_cluster\\_info, tier-2\\) when A has no saved rows for B.\n\n | \n\n1. Verify that Instance A has a saved Hermes cluster rows for instance B \\(service MIF-Hermes\\) pointing to B's old datacenter, or a single row that isn't marked primary.\n2. Send a MIF async message from A to B.\n\n Expected behavior: A resolves B's current cluster details and sends to the correct datacenter.\n\n Actual behavior: A uses the old/incomplete saved config and sends to the wrong datacenter, or fails with 'No primary cluster found'.\n\n |
| \n\nMulti-Instance Framework\n\n PRB2040054\n\n [KB3146783](https://hi.service-now.com/kb_view.do?sysparm_article=KB3146783)\n\n | \n\nThere's a flood of 'Unable to find vtable operation for operation id \\{\\}' messages that's generating millions of records in an instance for every Flow Designer execution\n\n | \n\nIn a cloned instance, the root cause of the flood of errors messages 'Unable to find vtable operation for operation id \\{\\}' in the syslog is that sn\\_mif\\_vtable\\_ operation\\_context.vtable \\_operation is empty.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nMulti-Instance Framework\n\n PRB2066107\n\n | \n\nDB listener MIFVTableListener fails with IAE before/after DB actions and breaks the normal upgrade flow\n\n | \n\nDuring an upgrade, a database listener throws an IllegalArgumentException at two points in the plugin-install lifecycle - both before and after DB actions run. This prevents the normal upgrade flow from completing for a number of plugins, resulting in files not being properly installed/loaded.\n\n | \n\n \n\n |
| \n\nMultimodal Service \\(Family Channel\\)\n\n PRB2073299\n\n | \n\nMMS Glide update\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nMultimodal Service \\(Family Channel\\)\n\n PRB2073300\n\n | \n\nVision Agent and MMS Glide\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nMultimodal Service \\(Family Channel\\)\n\n PRB2076357\n\n | \n\nUpdate system properties default values for MMS\n\n | \n\nMMS is not queuing enough records. The system propertyies 'glide.platform\\_mm\\_service.job.batch\\_size' should be set to '10' and 'glide.platform\\_mm\\_service.async\\_http\\_max\\_outstanding\\_requests' should be set to '20'\n\n | \n\n \n\n |
| \n\nNext Experience Unified Navigation\n\n PRB1720952\n\n | \n\nThe 'Not Found' tab on workspace\n\n | \n\nAfter opening the workspace, the user will notice a 'Not Found' tab.\n\n | \n\n1. Import xmls attached.\n2. Open console.\n3. Select the **iframe**scope.\n4. Provide the script 'openFrameAPI.openCustomURL\\('interaction\\_list.do'\\);'.\n\nNotice that the Interaction list will open in the platform view.\n\n5. Open the workspace.\n\n Notice the 'Not Found' tab.\n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2034126\n\n | \n\nA collapsible menu \\(for example, 'Self Service' or similar\\) text color does not change when the user hovers over it in the navigation filter menu\n\n | \n\nIt remains black when other entries turn white when the user hovers.\n\n | \n\n1. Open a theme where the top-level collapsible menu is set to black.\n2. Navigate to the **All** menu.\n3. Hover the mouse over different menu items.\n\nObserve that most menu items change text color from black to white on hover.\n\n4. Hover over 'Self Service'.\n\n Notice that the text remains black instead of changing to white.\n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2054933\n\n | \n\nGlide custom menu updates\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2079773\n\n | \n\nSet token\\_exchange\\_allowed to 'true' on an OffGlide AIEX oauth entity record\n\n | \n\nNotice that token\\_exchange\\_allowed is 'false' which needs to be 'true', otherwise oauth will fail for guest users.\n\n | \n\n \n\n |
| \n\nNext Experience Unified Navigation\n\n PRB2081424\n\n | \n\nSet bff\\_cookie\\_exchange\\_allowed to 'true' on OffGlide AIEX oauth entity records\n\n | \n\nbff\\_cookie\\_exchange\\_allowed is set as 'false', which need to be 'true', otherwise oauth will fail for the guest user.\n\n | \n\n \n\n |
| \n\nNow Assist in Virtual Agent\n\n PRB2056609\n\n | \n\nChange the Knowledge Graph \\(KG\\) defaults in NAVA and Now Assist Portal\n\n | \n\nToday, the KG default is User NLQ graph. That should be changed so the defaults are: In Now Assist Virtual Agent for natural language query, change the graph to Enterprise Graph \\(Small\\) and select the tag as 'VIRTUAL AGENT DEFAULT TAG'. In Now Assist Panel for natural language query, change the graph to Enterprise Graph \\(Small\\) and select the tag as 'NOW ASSIST PANEL DEFAULT TAG'.\n\n | \n\n \n\n |
| \n\nNow Assist Nextwave Experience\n\n PRB2059502\n\n | \n\nAdd sys\\_props for caching in sys\\_og\\_conversational \\_cache\\_configuration\n\n | \n\nIf props are enabled on the instance, that should be reflected via cache service instantly.\n\n | \n\n \n\n |
| \n\nNow Assist Nextwave Experience\n\n PRB2061245\n\n | \n\nSessionController shouldn't try to refresh AuthorizationInfoBundle, as this is done in the Glide handshake process\n\n | \n\nWhen a topic execution is initiated, the conversation ID isn't available in certain Glide log entries' context maps This complicates troubleshooting across different trace IDs instead of a unified conversation ID. The conversation ID should be available in the cache and topic execution context map in the syslog table.\n\n | \n\n \n\n |
| \n\nOneExtend\n\n PRB2056745\n\n | \n\nGuardian pre-process flow resolves getGeoRoutingDetails\\(\\) multiple times per request in NowLLMIntegration GuardianProvider\n\n | \n\nNowLLMIntegration GuardianProvider. shouldUseGatewayService\\(\\) and addLLMGatewayRoutingHeader\\(\\) each independently call through to GeoRoutingServiceImpl .getGeoRoutingDetails\\(\\) > resolveGeoRoutingDetails\\(\\). ShouldUseGatewayService\\(\\) itself is invoked from multiple call sites across a single request's lifecycle. None of these calls are memorized, so resolveGeoRoutingDetails\\(\\) re-executes its full resolution logic \\(potentially including the licensing entitlement API call\\) on every invocation within the same request, even though the underlying geo-routing state can't change mid-request.\n\n | \n\n1. Trigger a Guardian moderation request that routes through NowLLMIntegration GuardianProvider \\(LLM\\_GENERIC\\_SMALL\\_MODERATIONS model\\).\n2. Trace/log calls into GeoRoutingServiceImpl .resolveGeoRoutingDetails\\(\\) \\(or set a breakpoint\\) during a single request's transformRequest\\(\\)/getUrl\\(\\) lifecycle.\n\n Observe that resolveGeoRoutingDetails\\(\\) executes repeatedly \\(up to six times found via code trace\\) instead of once per request. When the 0$ SKU entitlement isn't active, each of these calls re-invokes the expensive isEntitlementActive WithLicensingAPI\\(\\) licensing call, since resolveGeoRoutingDetails\\(\\) has no per-request memorization. Only the underlying getGeoRoutings\\(\\) /getGeoRoutingConfigs\\(\\) cache calls are cached via ADomainAwareCache.\n\n |
| \n\nOneExtend\n\n PRB2057127\n\n | \n\nMultiple GenAI logs are created in skill chaining execution\n\n | \n\nOneExtend Execute and ExecuteSecure are missing the offGlideChainingEnabled flag.\n\n | \n\nExecute a skill chaining.\n\n Observe that the Generative AI logs are created two times.\n\n |
| \n\nOneExtend\n\n PRB2059503\n\n [KB3142021](https://hi.service-now.com/kb_view.do?sysparm_article=KB3142021)\n\n | \n\nSummarization records aren't displaying a proper response\n\n | \n\nIncident, Change, and Case summarizations are failing with errors when users select the 'Summarize' button: 'Summarization could not be completed because access to the base table Case was unsuccessful'. Error logs: 'Error sending to unified\\_short\\_url\\_active\\_1...Status 500 - \\[Internal Server Error\\] \\[\\{'success':false,'statusCode':429,'message':'Too many concurrent data insert operations in progress - additional rebuild request being ignored','timestamp':'2026-07-17T07:00:17.752637494Z','results':\\{\\}\\}\\]'.\n\n | \n\n \n\n |
| \n\nOneExtend\n\n PRB2064726\n\n | \n\nThe Mosaic response translation to the user's preferred language is failing\n\n | \n\n \n\n | \n\n1. Set the user's preferred language to a non-default language.\n2. Generate a Mosaic token for the given userId.\n3. Run the Mosaic capability.\n\n Expected behavior: The Mosaic response should be translated and returned in the user's preferred language.\n\n Actual behavior: The Mosaic response is not translated to the user's preferred language and is returned in the default language.\n\n |
| \n\nOneExtend\n\n PRB2073758\n\n | \n\nAutoChat off-glide implementation changes\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nOneExtend\n\n PRB2076738\n\n | \n\nUpdate the model display names in the Gen AI model configuration table\n\n | \n\n \n\n | \n\n1. Update the model display names.\n2. Make the Gemini pro model as 'active=false' and the 'lifecycle' state as 'deprecated'.\n3. Make the Gemini 3 flash as the action 'delete'.\n\n |
| \n\nOneExtend\n\n PRB2078604\n\n | \n\nAdd caching for BYO PII\n\n | \n\n \n\n | \n\n \n\n |
| \n\nPerformance Analytics\n\n PRB2014301\n\n | \n\nIn the Classic Formula indicator form, the elements list is not visible when configuring breakdowns of contributing indicators in the formula\n\n | \n\nA null table appears and an error is thrown without showing the elements list.\n\n | \n\n1. Open WDF enabled instance.\n2. Navigate to Formula Indicators list through the 'All' menu navigation.\n3. Open any existing indicator or create a new formula indicator.\n4. Select on **Browse** for an indicator.\n\nNotice that under the 'Formula' tab, a modal with **Indicator**, **Breakdown** and **Element** fields opens up.\n\n5. Select any indicator and breakdown.\n\n Expected behavior: The list of elements for the selected breakdown from the respective target table are shown.\n\n Actual behavior: When selecting the **Search** icon on the **Elements** field, the popup opens with a null table, and throws an error without showing the actual elements list.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2035261\n\n | \n\nAdvanced Filter doesn't work as expected for certain filters in the Data Visualization dashboard in Platform Analytics\n\n | \n\nAdvanced filters in data visualizations aren't honored for both date range \\('Between'\\) and keyword conditions, resulting in all the records being returned regardless of the configured filter criteria.\n\n | \n\nScenario 1:\n\n 1. Log in to an Australia base instance.\n2. Navigate to **All** > **Data Visualizations**.\n3. Open any visualization.\n4. Select the **Advanced Filter** button.\n5. Select the **Created** field.\n6. Choose the 'Between' operator.\n7. Specify a valid start date and end date.\n8. Apply the filter.\n\n Expected behavior: Only records with a created date within the specified date range are returned.\n\n Actual behavior: The visualization returns all records, ignoring the configured date range filter.\n\n Scenario 2:\n\n 1. Log in to an Australia base instance.\n2. Navigate to **All** > **Data Visualizations**.\n3. Open any visualization.\n4. Select the **Advanced Filter** button.\n5. Select the **Keyword** field.\n6. Configure the condition as 'Keyword is SLA'.\n7. Apply the filter.\n\n Expected behavior: Only records matching the keyword value 'SLA' are returned.\n\n Actual behavior: The visualization returns all records instead of only the matching records, indicating that the filter condition isn't being applied correctly.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2075362\n\n | \n\nThe domain path is empty for many reports\n\n | \n\n \n\n | \n\nUpgrade the Zurich instance to Australia.\n\n Expected behavior: The domain path is populated for all reports \\(sys\\_report\\).\n\n Actual behavior: The domain path is empty for many reports.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2076990\n\n | \n\nThe AIDE **Explore** button shown on all lists, including 'All Table Discovery' entities\n\n | \n\nThe AIDE **Explore** button is being shown on all entity lists, including entities that should not have it. Only entities marked 'Active=true' and 'population\\_source=Table configuration' should display the **Explore** button. Entities with 'population\\_source = All Table Discovery' \\(or inactive entities\\) should not show the **Explore** button.\n\n | \n\nOpen an entity list that is marked as 'All Table Discovery'.\n\n Observe that the **Explore** button is present.\n\n |
| \n\nPlatform Analytics Component API\n\n PRB2079191\n\n [KB3152739](https://hi.service-now.com/kb_view.do?sysparm_article=KB3152739)\n\n | \n\nRemove sys\\_script\\_fix\\_ee3a858a4b8203101a31117f2974612b.xml\n\n | \n\nThe script sys\\_script\\_fix\\_ee3a858a4b8203101a31117f2974612b.xml introduced in Australia Patch 5 is causing upgrade delays due to the huge number of records.\n\n | \n\n1. Log in to a Zurich instance.\n2. Ensure that there are more than 100K records in report\\_table.\n3. Verify that the following isn't present:\n 1. The report\\_table field in report\\_stats table\n 2. The analytics\\_visualization\\_metadata table\n4. Verify that the script is not present in the instance: /nav\\_to.do?uri=sys\\_script\\_fix.do?sys\\_id=ee3a858a4b8203101a31117f2974612b.\n5. Upgrade the instance to Australia Patch 5.\n\n Observe that there are significant delays due to sys\\_script\\_fix\\_ee3a858a4b8203101a31117f2974612b.xml.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB1997164\n\n | \n\nUsers are unable to sort the 'Saved Data Visualization' library when adding an element\n\n | \n\nA component was replaced with PresentationalListBuilder and deliberately sets enableSort to 'false' because the API doesn't support sorting.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2001651\n\n | \n\nWidget creation on a fresh dashboard in the second tab has unnecessary DB calls\n\n | \n\n \n\n | \n\n1. Create a Next Experience dashboard.\n2. Add 2 tabs.\n3. In the second tab, add a new data visualization widget.\n4. Save the dashboard.\n\n Expected behavior: There should be only one insert to par\\_dashboard\\_widget.\n\n Actual behavior: There is first an insert, then a delete, and then another insert. The delete is tracked in the sys\\_audit\\_delete table with the table name as par\\_dashboard\\_widget.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2004040\n\n | \n\nEnable dashboard logging by default as a system property\n\n | \n\nUI logs are not captured because it is set to 'false' by default.\n\n | \n\n1. Open the Platform Analytics dashboard.\n2. Make some changes in Edit mode.\n3. Save the changes.\n\n Observe that in indexDB, there's no UI logs captured because it is set to 'false' by default in 'const isLoggingEnabled = getBooleanProperty\\( 'com.snc.pae.dashboard.logging', false \\);'\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2031048\n\n [KB3144237](https://hi.service-now.com/kb_view.do?sysparm_article=KB3144237)\n\n | \n\nPlatform Analytics dashboards aren't loading and are stuck in a loading state indefinitely\n\n | \n\nThis fix is to gracefully handle the NullPointerException \\(NPE\\) which Usage Analytics license entitlement engine throws. This doesn't solve the issues inside Usage Analytics license entitlement engine nor it introduces NPE exception itself. It simply doesn't send 'actions.canAccessInsights' in a dashboard payload when there's a NPE in the code. The dashboard would still load. The only consequence of this NPE from Usage Analytics license entitlement engine is now, if the user has insight access, they still can't see it.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2033980\n\n [KB3129184](https://hi.service-now.com/kb_view.do?sysparm_article=KB3129184)\n\n | \n\nText index processing delay on analytics\\_visualization\\(column=type\\) after upgrading to Australia\n\n | \n\nAfter upgrading to Australia, the user observed increased processing times related to text indexing events on the 'type' column of the analytics\\_visualization table. This results in a backlog of index events.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2053337\n\n [KB3152732](https://hi.service-now.com/kb_view.do?sysparm_article=KB3152732)\n\n | \n\nThere's an increased response time of Core UI dashboards in Australia\n\n | \n\nThe response times of Pa\\_Dashboard transactions degraded by 2000ms compared. This is coming from increase in SQL time.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2058867\n\n [KB3152710](https://hi.service-now.com/kb_view.do?sysparm_article=KB3152710)\n\n | \n\nReduce the call cost on calling isPaPremium for every dashboard get call\n\n | \n\nOn instances with large dashboard counts \\(thousands of dashboards\\), this multiplies an expensive entitlement check across the full dataset. This causes high memory usage, semaphore exhaustion, node failover, and an out of memory error.\n\n | \n\n \n\n |
| \n\nPlatform Analytics Dashboard API\n\n PRB2059204\n\n | \n\nNon-admin users can't read a localized tab name on PAR dashboard in a scoped application\n\n | \n\nA non-admin or dashboard\\_admin user can't change the localized tab name on the scoped application's dashboard.\n\n | \n\n1. Create a dashboard in the application scope.\n2. Add tabs.\n3. Share it with a non-admin user as an editor.\n4. Impersonate to the user.\n5. Change language except for English.\n6. Change tab names.\n7. Save the dashboard.\n8. Reload.\n\n Expected behavior: The tab names have been changed.\n\n Actual behavior: The tab names were not changed.\n\n |
| \n\nPlatform Analytics Migration API\n\n PRB2037846\n\n | \n\nThe Migration Center summary count doesn't match the list count for fully migrated dashboards\n\n | \n\nThe Get Migration Summary Scripted API needs to be updated so that it calculates the total number of migrated dashboards in the same way as the Migrated List.\n\n | \n\nScenario 1:\n\n 1. Create a few Core UI dashboards.2. Migrate them.\n2. Navigate to the PAR Dashboards table.\n3. Delete one or more migrated dashboards.\n\n Observe that the Migrated List count and the Summary count don't match.\n\n Scenario 2:\n\n 1. Create a Core UI dashboard containing a Dynamic Content widget.2. Migrate the dashboards.3. Navigate to the par\\_coreui\\_migration \\_bridge\\_dashboard table.\n2. Remove the record\\(s\\) associated with the dashboard that contains the Dynamic Content widget.\n\n Observe that the Migrated List count and the Summary count don't match.\n\n |
| \n\nPlatform Analytics Migration API\n\n PRB2064612\n\n | \n\nDashboard owner migration creates new pa\\_dashboard records when triggered from a child domain\n\n | \n\n \n\n | \n\n1. Install the domain plugin with demo data.\n2. Create a core UI dashboard in TOP/MSP domain.\n3. Add a report in the global domain.\n4. Switch to the child domain TOP/MSP/MSP Technicians.\n5. Migrate it from the dashboard banner.\n6. Switch to the global domain.\n7. Open pa\\_dashbaords.list and expand domains.\n\n Observe that there are two core UI dashboards.\n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2056633\n\n | \n\nA Playbook activity start delay doesn't work if its less than 11 seconds\n\n | \n\nThe 12 second start delay seems to be the minimum honored threshold.\n\n | \n\n1. Create a simple playbook with 1 stage and 2 instruction acts.\n2. Configure activity 2 to have a start with delay for 11 seconds.\n3. Test the playbook.\n4. Notice that the activity is set in progress after activity 1 completed and there is no 11 second delay.\n5. Configure activity 2 with a 12 second start with delay.\n6. Test the playbook\n\n Observe that after activity 1 is complete, the delay is honored, and activity 2 doesn't start until after 12 seconds.\n\n |
| \n\nPlaybooks \\(Family Channel\\)\n\n PRB2062029\n\n | \n\nChanges to the permission sets are not working as expected\n\n | \n\nThe users should have the pd\\_author role.\n\n | \n\n1. Create a new playbook that uses 'incident' as the parent table.\n2. Add two stages. Each stage should include at least on activity.\n3. Activate it.\n4. Open the 'Process properties' side panel.\n5. Select the 'Runtime permissions' tab.\n6. Add a permission set of type users.\n7. Dot-walk to the 'Assigned to' value of the parent record\n8. Activate the playbook..\n9. Test the playbook using the incident that involves the users set up with the permissions for it.\n10. View it in 'Preview'.\n11. Impersonate the caller of the incident.\n12. Return to the playbook preview.\n13. Refresh it.\n\n Expected behavior: The user should see nothing.\n\n Actual behavior: The user can see the playbook execution.\n\n |
| \n\nPredictive Intelligence\n\n PRB2061744\n\n | \n\nPrevious records of 'ml\\_model\\_artifact' are still present in the sys\\_attachment table for the Data Analysis capability\n\n | \n\n \n\n | \n\n \n\n |
| \n\nProcess Mining\n\n PRB2035128\n\n | \n\nMeter-based guardrails and controls\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nProcess Mining\n\n PRB2035129\n\n | \n\nPre-fill process configuration fields with AI\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nProject Management\n\n PRB1993708\n\n | \n\nWhen moving a story from one project to another, the actual effort doubles on the story\n\n | \n\nWhen assigning a story with actual hours more than 24 hours, suppose 40 hours, the story takes it as 1 day and 16 hours. However the project only adds the hours and not the days, therefore the project actual hours become just 16 hours.\n\n | \n\n1. Navigate to an existing project with a story, or create a new one.\n2. Locate another project, or create a new one.\n3. Take one of the stories with logged 'Actual Hours' and move it to a different project.\n4. Navigate to the **Stories** \\[rm\\_story\\] list view.\n5. Delete the existing **Project** field and change it from here.\n6. Choose a project.\n\n Observe the 'Actual effort' has doubled on the story.\n\n |
| \n\nProject Management\n\n PRB2036275\n\n | \n\nProjectTemplate.java calls extension point outside null guard, so applyTemplate\\(\\) silently returns zero tasks within flow execution context\n\n | \n\nWhen PTGlobalAPI\\(\\).applyTemplate\\(\\) is called within a flow action \\(for example, 'Implement SPM Oversight'\\), the Customer Project record is created but zero project tasks are generated. The same applyTemplate\\(\\) call succeeds from Background Scripts on the same project record. The ProjectTemplate scripted extension point \\(sys\\_script\\_include.1e6e73619f001200598a5bb0657fcfc2, line 24\\) performs a GlideRecord.get\\(\\) call where the table name resolves to null within the flow transaction context. This causes applyTemplate\\(\\) to silently return zero tasks. The PPM engine then attempts to recalculate the project, but the planned\\_task record doesn't exist yet, producing the following error: 'com.snc.planned\\_task.core.PlannedTaskAPI: PPM Unable to Recalculate Task : \\[sys\\_id\\] Cannot invoke 'com.snc.planned\\_task.core.PlannedTask.getStartDate\\(\\)' because 'task' is null'.\n\n | \n\n1. Configure CSM Order Management project oversight with decision tables, field mappings, and project/task templates \\(template tasks table = customer\\_project\\_task\\).\n2. Submit a customer order via REST API that triggers a flow containing the 'Implement SPM Oversight' flow action.\n\nObserve that the flow action calls OrderLinePrjUtilOOB.createProjectForOrderLine\\(\\), which calls PTGlobalAPI\\(\\).applyTemplate\\(projectSysId, templateId, actualStartDate\\) at line 58 of OrderLinePrjUtilOOB.js. The Customer Project is created but zero Customer Project tasks are generated. The short description remains unchanged.\n\n3. Check the logs for the error 'com.snc.planned\\_task.core.PlannedTaskAPI: PPM Unable to Recalculate Task : \\[sys\\_id\\] Cannot invoke 'com.snc.planned\\_task.core.PlannedTask.getStartDate\\(\\)' because 'task' is null'.\n4. Run the identical applyTemplate\\(\\) call from Background Scripts on the same project record.\n\nObserve that tasks are created successfully.\n\n\n Expected behavior: applyTemplate\\(\\) creates Customer Project tasks from the template within the flow action.\n\n Actual: Zero tasks are created. The ProjectTemplate extension point encounters a null table name because the project record isn't fully committed in the flow transaction.\n\n |
| \n\nProject Management\n\n PRB2050675\n\n | \n\nAllow the change of constraint date at the parent task level\n\n | \n\nEnure the child task start date honors both the parent task and its constraint dates.\n\n | \n\n \n\n |
| \n\nProject Management\n\n PRB2052767\n\n | \n\nAn incorrect auto-update for the multi-currency setup in the project workspace\n\n | \n\nRemove the logic to allow the negative budget from the business rule 'Validate Cost Breakdowns.'\n\n | \n\n \n\n |
| \n\nProject Management\n\n PRB2066164\n\n | \n\nCertain users do not see all the dropdown list values within a grid cell in the 'RIDAC' tab\n\n | \n\nThis issue occurs only in the grid view.\n\n | \n\n1. Open the Project Workspace.\n2. Navigate to **RIDAC**.\n3. Open a project.\n4. Expand 'Risk.\n\n Observe the dropdown list for the **Impact** field.\n\n |
| \n\nProject Management\n\n PRB2071094\n\n | \n\nDisplay a message if the parent change fails due to schedule conflicts\n\n | \n\n \n\n | \n\n \n\n |
| \n\nRemote Process Synchronization \\(Family Release\\)\n\n PRB1950825\n\n [KB3148345](https://hi.service-now.com/kb_view.do?sysparm_article=KB3148345)\n\n | \n\nRemote Process Synchronization \\(RPS\\) sends more records to the target than that published into the transport queue\n\n | \n\nRemote Process Synchronization \\(RPS\\) sends more records to the target than those published into the transport queue. This results in discrepancies between outbound HTTP logs and transport queue data. The issue arises from a performance optimization feature that saves last positions for outbound jobs. When multiple capture definitions \\(ih\\_sync\\_capture\\_definition\\) exceed the number of buckets, cursor backtracking occurs, leading to reprocessing of records and discrepancies in record counts. This can cause intermittent or unavailable connections between consumer applications with general usage of RPS. The issues manifest as slow response times, frequent disconnections, and periods where the connection appears down despite the RPS connection showing as 'active'. However, remote task records remain in the 'New' status and do not progress, creating a risk of transaction impact.\n\n | \n\n \n\n |
| \n\nRemote Process Synchronization \\(Family Release\\)\n\n PRB2052613\n\n | \n\nExtremely slow processing of the RPS queue on Impact\n\n | \n\nWith the number of connections increasing, slow processing occurs exponentially.\n\n | \n\n1. Log in to Impact.\n2. Check the transaction time.\n3. Query the sn\\_transport\\_queue table to get the volume of the 'ready' transaction.\n4. On a subprod instance, onboard the instance via the impact onboarding process.\n5. Run the data migration.\n6. Verify the time it takes to migrate the data.\n\n Notice that with one or two connections, the transaction seems fast. But as the number of connections increase, performance issues happen exponentially.\n\n |
| \n\nRemote Process Synchronization \\(Family Release\\)\n\n PRB2055484\n\n | \n\nProcessSyncReplicationTable's queryShard includes null labels\n\n | \n\nBoth labeled and unlabeled entries are returned.\n\n | \n\n1. Write an unlabeled entry into a cdc\\_queue\\_ih shard table.\n2. Write a second entry with a valid label.\n3. Trigger an RPS outbound poll for that valid label.\n\n Expected behavior: Only rows matching the requested label\\(s\\) should be returned, unlabeled entries should never match.\n\n Actual behavior: Query returns both the labeled entry and the unlabeled entry.\n\n |
| \n\nRemote Process Synchronization \\(Family Release\\)\n\n PRB2066418\n\n | \n\nAdd debug logging to OutboundQueueDao.fetchNextValidEntry\n\n | \n\n \n\n | \n\n1. Set up RPS on an instance.\n2. Navigate to **RPS properties**.\n3. Turn on 'Activate debug logging'.\n\n Notice there is no timing information for fetchNextValidEntry\\(\\) in the logs.\n\n |
| \n\nRequest Management\n\n PRB2075931\n\n | \n\nCart item hints do not get copied when ordering from a draft item\n\n | \n\n \n\n | \n\n1. Create a draft cart item.\n2. Add the hint to update the request parent to some incident.\n3. Checkout the cart item.\n\n Notice that the cart item hint doesn't gets populated to the request.\n\n |
| \n\nRoles\n\n PRB2023810\n\n | \n\nInstances without explicit roles throw an error when invoking agents with a 'Nobody' role mask\n\n | \n\nThe following error appears in the logs: 'Role 'snc\\_external' not found. Cannot be automatically created: no thrown error'.\n\n | \n\n1. Open an instance that doesn't have the explicit roles plugin.\n2. Trigger an AI Agent that has a role mask on the **Nobody** field.\n\n Observe the error in the logs: 'Role 'snc\\_external' not found. Cannot be automatically created: no thrown error'.\n\n |
| \n\nRoles\n\n PRB2052882\n\n | \n\nInherited roles aren't added back when patcher is on and the state of 'User has role' is changed from pending\\_approval to active\n\n | \n\nWhen the user updates the state of the 'User has role' record to active, no records are created for inherited roles.\n\n | \n\n1. Enable the glide.security.inh\\_count\\_patcher.enabled property to true.\n2. Assign a user with an admin role and with the state as pending approval.\n\nNo 'User has role' records should be created for inherited roles.\n\n3. Update the state of the 'User has role' record to active.\n\n Expected behavior: 'User has role' records are created for inherited roles with the state as active.\n\n Current behavior: No 'User has role' records are created for inherited roles.\n\n |
| \n\nSchedule Optimization\n\n PRB2022407\n\n | \n\ngetRefRecord\\(\\) scoping bypass for the 1.0.1 release\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSearch Suggestions\n\n PRB2051556\n\n | \n\nThe scheduled job deletes search suggestion and business rules, and should leave ones with the global namespace alone\n\n | \n\nThe business rules created should not get deleted by the scheduled job.\n\n | \n\n1. Create a business rule on some table.\n2. Set the business rule to run on the update and delete.\n3. Name it starting with 'Disable'.\n4. Set the script.\n5. Run the scheduled job, 'Remove obsolete search suggestion BRs' under sysauto\\_script.\n\n Observe that the business rule created was deleted, and shows up in the sys\\_update\\_xml table.\n\n |
| \n\nServer-side scripts\n\n PRB2056793\n\n [KB3141731](https://hi.service-now.com/kb_view.do?sysparm_article=KB3141731)\n\n | \n\nESLatest sibling scopes shouldn't use scoped sandbox scopes\n\n | \n\nESLatest sibling scopes are created when 'Ecmascript 2021' mode is turned on for global scripts. When they interact with something that requires sandbox script execution, they end up inadvertently creating an isolated scope for what essentially should be the global sandbox scope. There's a specific code path in KittyScriptEvaluator that attempts to re-initialize GlideElement in a scoped sandbox where it's not available leading to re-initialization errors seen in the logs and triggering the causal chain that invokes this path.\n\n | \n\n \n\n |
| \n\nServer-side scripts\n\n PRB2076586\n\n [https://support.servicenow.com/kb?id=kb\\_article\\_view&sysparm\\_article=KB3151029](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB3151029)\n\n | \n\nPlugin scripts aren't registered in some app nodes\n\n | \n\nOn some instances, a subset of nodes can experience the mega menu in Employee Center being broken. The following error appears on the screen when navigating to Employee Center, and users are unable to use the menu: 'ErrorServer JavaScript error 'sn\\_taxonomy' is not defined.'\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nService Catalog Builder\n\n PRB2033462\n\n | \n\nWhen creating a catalog item via Catalog Builder, UI policies configured in a previous step aren't visible on the 'Review and Submit' step\n\n | \n\nIt appears that the GraphQL query is not being triggered for the catalog\\_ui\\_policy table.\n\n | \n\n1. Open Catalog Builder.\n2. Create a new catalog item.\n3. Configure a UI Policy, Client Script, and any other required details.\n4. Navigate to the **Review and Submit** step.\n\n Notice that the UI Policy is not displayed, even though one has been configured.\n\n |
| \n\nService Catalog Builder\n\n PRB2033565\n\n | \n\nA UI policy action created from Catalog Builder can't be seen in the platform\n\n | \n\n \n\n | \n\n1. Log in to Catalog Builder.\n2. Create a question on a catalog item.\n3. Create a UI policy and associate an action from the 'UI Policy' tab.\n4. Open the item in 'Edit in Advanced View' to get the item in the platform.\n5. Open the UI policy from the related list.\n6. Open the UI policy action.\n\n Notice that the variable name is empty, and the valid options are not seen on the right side.\n\n |
| \n\nService Catalog Builder\n\n PRB2063629\n\n | \n\nThe **UI Policy Action** field message fields re-appear after variable selection in Catalog Builder\n\n | \n\n \n\n | \n\n1. Open the catalog item in the CB wizard.\n2. Navigate to **UI Policy** > **Add behavior** > **Actions** > **Add action**.\n3. Select the **Plain Label/Rich Text Label/Container Start** variable.\n4. Wait 3 seconds for onChange.\n\n Expected behavior: The field message should not be displayed in the UI policy.\n\n Actual behavior: The fields re-appear after the policy refresh.\n\n |
| \n\nService Catalog Portal Widgets\n\n PRB2018000\n\n | \n\nPerformance issues with the Employee Center Standard Ticket Page Widget\n\n | \n\nThis issue was observed in Australia, but the function works as expected in Zurich. This impacts the Service Portal 'Standard Ticket Header Widget.' The user observed that the RITM 'Show details' dropdown list alignment is off, and the REQ **Show/Hide Details** dropdown list button option is shown even if there are no additional details to show.\n\n | \n\n1. Open the Employee Center Portal \\(esc\\).\n2. Submit a Request.\n\nOn the standard ticket page, observe that the **Show/Hide Details** button is shown even if there are no additional details to show.\n\n3. On the 'Requested items' tab, select on **RITM** number.\n\nNotice that it will redirect to the standard ticket page for the RITM.\n\n\n Expected result: The RITM alignment is aligned without padding-left at 0px.\n\n Actual result: The RITM **Show details** button alignment is off, and the REQ **Show/Hide Details** dropdown list button option is shown even if there are no additional details to show.\n\n |
| \n\nService Catalog\n\n PRB1972924\n\n | \n\nThe 'Generate sequence' UI action gives a missing start rule error on Playbook 28.2.1\n\n | \n\nThis issue was observed in Playbook 28.2.1, but not in 28.0.8.\n\n | \n\n1. Open any order guide.\n2. Generate the sequence.\n3. Open the playbook created.\n\n Observe the missing start rule errors.\n\n |
| \n\nService Catalog\n\n PRB2033096\n\n | \n\nCatalog redirection throws a 404 error page when accessed from the chat responses\n\n | \n\n \n\n | \n\n \n\n |
| \n\nService Catalog\n\n PRB2040266\n\n | \n\ng\\_form.clearValue should clear the value of the Lookup Select Box, even when there are no reference qualifiers\n\n | \n\nWhen loading the XML files, this creates Lookup Select Boxes. One file creates an item option named 'user\\_group' under the 'AWS account request' catalog item, which is a is a Lookup Select Box that references the sys\\_user\\_group table and its reference qualifier is 'javascript: 'manager=' + current.variables.user'. Another file creates an item option named 'user' under the 'AWS account request' catalog item, which is a Lookup Select Box that references the sys\\_user table. The next file is a catalog script for the 'AWS account request' catalog item, which logs the value of the **user\\_group** field when there is a change to the user field.\n\n | \n\n1. Load the XML files.\n\nNotice that these XML files create a item options named 'user\\_group' and 'user' under the 'AWS account request' catalog item, and that Lookup Select Boxes are created.\n\n2. Navigate to the catalog item.\n3. Change the **User** field to any value.\n\n Expected behavior: The **User Group** field should be cleared, and the alert should show an empty value.\n\n Actual behavior: The **User Group** field is cleared in the UI, but the alert shows the previous value.\n\n |
| \n\nService Catalog\n\n PRB2070973\n\n | \n\nAdd Now Assist AI-usage tracking fields and options to the catalog\\_builder\\_analytics table\n\n | \n\nExtend the catalog\\_builder\\_analytics table to support tracking of Now Assist AI usage during catalog building.\n\n | \n\n \n\n |
| \n\nService Catalog\n\n PRB2073331\n\n | \n\nFamily changes for AIX STP\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nService Catalog\n\n PRB2073333\n\n | \n\nFamily changes for the AIX catalog item form\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nService Mapping\n\n PRB2040618\n\n [KB3137540](https://hi.service-now.com/kb_view.do?sysparm_article=KB3137540)\n\n | \n\nThe 'Application Service Manual Ep Cleanup' job doesn't work\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nService Mapping\n\n PRB2052536\n\n | \n\nIn Service Map, additional related list tabs \\(Changes-current/past, Incident, Problem\\) are permanently stuck on 'Loading...'\n\n | \n\n \n\n | \n\n1. Open any Operational Service in the Event Management View.\n2. Add indicators.\n3. Select on the added tabs for the indicator.\n\n Notice that it's permanently stuck on 'Loading...'.\n\n |
| \n\nServiceNow Data Catalog \\(Glide\\)\n\n PRB2009278\n\n | \n\nMetadata collectors can generate graphs too large to upload as attachments\n\n | \n\nThe mysql collector ran to completion, but uploading the attachment failed as the attachment was too large.\n\n | \n\n \n\n |
| \n\nServiceNow Data Catalog \\(Glide\\)\n\n PRB2064415\n\n | \n\nUpdate glide-process-flow to support SnowsK8s workflow action steps\n\n | \n\nThe glide-process-flow needs to support SnowsK8s workflow action steps, and connectivity between SnowsK8s and glide requires a certificate definition to be installed.\n\n | \n\n \n\n |
| \n\nServiceNow Data Catalog \\(Glide\\)\n\n PRB2070138\n\n | \n\nUpdate Glide to accommodate a new ID for consolidated DCG \\(dcg-app\\)\n\n | \n\nThe ServiceNow Data Catalog is being re-bundled into a new, consolidated scoped application. In order to prevent collisions with previous installations of the catalog, a new scoped application ID was used.\n\n | \n\n \n\n |
| \n\nServiceNow Data Catalog \\(Glide\\)\n\n PRB2070443\n\n | \n\nFix MID compression for metadata collectors\n\n | \n\n \n\n | \n\n \n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB1831844\n\n | \n\nUsers are unable to convert a sys\\_app-based application due to a company key\n\n | \n\nThe user is unable to convert an app from an instance with the error, 'Not allowed to download application x\\_taniu\\_tan\\_core. Check that you either have maint access or have added your company key \\(e.g. sn for ServiceNow\\) to the sn\\_appauthor.all\\_company\\_keys system property.'\n\n | \n\n1. Load an open source app from a third party using Studio.\n2. Verify that it can be see.\n3. Edit the sys\\_app based scope in the instance.\n4. Open SDK.\n5. Attempt to convert it.\n\n Observe the error message.\n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB2041355\n\n | \n\nThe sys\\_gen\\_ai\\_feature\\_mapping and sys\\_gen\\_ai\\_strategy\\_mapping records are silently dropped during Now Assist skill installation via Studio and BuildAgent\n\n | \n\nAll records including feature mappings and strategy mappings should be installed successfully.\n\n | \n\n1. Login as an admin user.\n2. Open Servicenow Studio and Build Agent.\n3. Provide a prompt to create a Now Assist skill for any use case.\n4. Provide the necessary answers to the Build Agent.\n\nNotice that the Build Agent will build and install the skill.\n\n5. Open thesys\\_gen\\_ai\\_feature\\_mappin and sys\\_gen\\_ai\\_strategy\\_mappin tables.\n\n Observe whether any records are created or not.\n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB2060181\n\n | \n\nListElementLoader reinserts records if the child elements has the action attribute as 'INSERT\\_OR\\_UPDATE;\n\n | \n\n \n\n | \n\n1. Create an application on the instance with the table and list metadata.\n2. Remove the list metadata.\n3. Export the app.\n4. Reinstall the application.\n\n Expected behavior: The app should be installed and the list metadata should still remain deleted.\n\n Actual behavior: The list gets re-inserted again.\n\n |
| \n\nServiceNow SDK \\(Glide\\)\n\n PRB2067936\n\n | \n\nGlideQuery Schema.findInvalidChoiceError throws 'Cannot find function toLowerCase in object true' for non-string \\(boolean\\) values on **Choice/dot-walked** fields\n\n | \n\nA GlideQuery.where\\(field, value\\) call crashes when the value is a JS boolean \\(true/false\\) instead of a string. This occurs if the field either has a choice list configured in schema or is dot-walked \\(for example, reference.booleanField\\). The dot-walked case bypasses the choice-check guard unconditionally, regardless of whether the target field actually has choices. In production, this crashes a legacy Workflow 'if condition' script mid-transaction \\(via WorkflowScopedScriptRunner/WFActivityHandler\\). It surfaces the error as a real exception rather than silently swallowing it, faulting the workflow activity.\n\n | \n\n \n\n |
| \n\nServiceNow Studio \\(Family Channel\\)\n\n PRB2063560\n\n | \n\nTrue up the Glider Store app\n\n | \n\n \n\n | \n\n \n\n |
| \n\nService Portal Core Widgets\n\n PRB1819286\n\n | \n\nWhen updating the font-family in the EC theme, it doesn't update the font in the AI search results page\n\n | \n\nAccording to the 'Theming for AI Search in Service Portal' documentation, users can control the look and feel of AI search results. The user was attempting to update the default font family of the EC theme from Lato, Arial, sans-serif, to 'Segoe UI', sans-serif. When updating the EC theme CSS properties, this changed the font on the home page as expected, but failed to change font in the AI Search results page. Also, the faceted search widget doesn't change and was still using Lato, Arial, sans-serif.\n\n | \n\n \n\n |
| \n\nService Portal Experience\n\n PRB2051231\n\n | \n\nThe user observes the error '\\{0\\} has been rejected' in the base instance 'Approvals' widget\n\n | \n\nThe out of the box widget 'Approvals' displays an error info message '\\{0\\} has been rejected' when selecting the navigation buttons **Next** and **Previous**.\n\n | \n\n \n\n |
| \n\nService Portal\n\n PRB1913741\n\n | \n\nGuest and low-privilege users are unable to retrieve translation keys due to GlideRecordSecure Restrictions on sys\\_ux\\_lib\\_component\n\n | \n\nWhen accessing the sys\\_ux\\_lib\\_component table as an admin user, records are visible as expected. However, when impersonating a less privileged user \\(such as a user with no roles\\), the same table is not accessible, and no data is returned. Currently, one of the Service Portal widgets calls this table using GlideRecordSecure. As a result, users without the necessary roles cannot retrieve any records from sys\\_ux\\_lib\\_component. This leads to a failure in fetching translation keys, causing translations to not work for guest or unauthenticated users. This is not the expected behavior for guest users, who should still be able to see translations.\n\n | \n\n1. Log in as an admin.\n2. Open the sys\\_ux\\_lib\\_component table.\n\nObserve that the records are visible.\n\n3. Impersonate a user with no roles.\n4. Attempt to access the same table.\n\nObserve that no records are visible.\n\n\n Observe that in the Service Portal widget \\(using GlideRecordSecure\\), records are not returned for users without roles, resulting in missing translation keys and broken translations.\n\n |
| \n\nService Portfolio Management\n\n PRB2029361\n\n | \n\nThe 'Outage calculation' business rule is not working when the date format is set to DD/MM/YYYY\n\n | \n\nThe **Duration** field is not calculating correctly because the 'Outage Calculation' business rule does not work when the date format is set to DD/MM/YYYY.\n\n | \n\n \n\n |
| \n\nSession Management\n\n PRB2038268\n\n | \n\nWrite-once session values are lost after the second node move\n\n | \n\nO\\\\n a node move, the receiving node restores the session state from the previous node's saved record and folds it into its own baseline. Since the end-of-transaction save only persists changes relative to that baseline, values that were restored but not modified during the current session are excluded from the new node's saved record. The restore chain only reaches one hop back, so a value that was written once survives a single node move, but it's lost on the second move. Values re-written every hop survive because they always appear as a change relative to the baseline. Write-once values \\(for example, session properties and client data\\) are lost after the second node move.\n\n | \n\n1. Authenticate through GIG.\n2. Set a write-once session property \\(a value not updated after the initial write\\).\n3. Force a GIG re-balance \\(node A to node B\\).\n4. Verify that the property is present.\n5. Force a second GIG re-balance \\(node B back to node A, or to a third node\\).\n\n Observe that the property is now null/missing.\n\n |
| \n\nSession Management\n\n PRB2077746\n\n | \n\nIn GIG, the JSESSIONID-to-node affinity is only learned from request cookies, never from response Set-Cookie. The snc\\_session\\_affinity\\_node is set to 'Secure-only', which breaks stickiness for fresh sessions over plain HTTP\n\n | \n\nGIG's session affinity for a brand-new session depends entirely on the client echoing GIG's own snc\\_session\\_affinity\\_node cookie. GIG never learns the JSESSIONID-to-node mapping from the response that carries Set-Cookie: JSESSIONID. Additionally, snc\\_session\\_affinity\\_node is always emitted with the secure attribute, and the plain HTTP standard cookie stores it and never sends it back. As a result, it does not echo the affinity cookie, and gets every follow-up request load-balanced, including requests that already carry a valid JSESSIONID.\n\n | \n\n \n\n |
| \n\nSidebar \\(Family Release\\)\n\n PRB2058602\n\n | \n\nTyping indicator no longer works\n\n | \n\n \n\n | \n\n1. Open two browsers.\n2. Log in as two different users.\n3. Create a sidebar chat for the two users.\n4. Start typing.\n\n Observe that there is no typing indicator.\n\n |
| \n\nSmart Assessment Glide Family Platform Dependencies\n\n PRB2074438\n\n | \n\nAPI for CSV export of assessments\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSmart Assessment Glide Family Platform Dependencies\n\n PRB2074439\n\n | \n\nApache POI java class\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSoftware Asset Management\n\n PRB2018383\n\n [KB2986694](https://hi.service-now.com/kb_view.do?sysparm_article=KB2986694)\n\n | \n\nA Microsoft per-core license metric isn't visible after a Zurich or Australia upgrade\n\n | \n\nThe MS per core metric was moved from the apply\\_once folder to the update folder. The fix script to set the metric group was overwritten, since the update folder file insert ran after. Thus, the MS per core uploaded with no metric group.\n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nSoftware Asset Management\n\n PRB2071875\n\n | \n\nFinalize the list of license metrics to be shipped\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSoftware Asset Management\n\n PRB2073947\n\n | \n\nCreate samp\\_software\\_filter and samp\\_software\\_custom\\_filter tables in app-itam-sam for software junk filtering\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSoftware Asset Management Publisher Pack for Oracle\n\n PRB2062263\n\n | \n\nThe Oracle option extension for Windows not working with Oracle Wallet changes for Windows\n\n | \n\n \n\n | \n\n1. Create applicative credentials for the CI type 'cmdb\\_ci\\_db\\_ora\\_instance' for the Oracle Instance to the ServiceNow instance.\n2. Identify if the discovery process is utilizing the applicative credentials stored on the ServicNow instance or external credential vault.\n3. Execute the command on the target server.\n\n Observe that the User/Credential combo printed in plain text in the Windows server shell log is utilizing the Oracle SQL\\*Plus utility.\n\n |
| \n\nSoftware Installation Deduplication\n\n PRB2068830\n\n | \n\nEach dedup UPDATE should carry at most BATCHSIZE sys\\_ids, bu it carries the sum of the sys\\_ids from 100 \\_markActive calls, with no upper bound\n\n | \n\nThe 'SAM - Deduplicate Install Table' scheduled job issues UPDATE statements against cmdb\\_sam\\_sw\\_install \\(SET deduplicated='1', active='1', primary\\_install=NULL\\). Most executions complete in roughly 200 milliseconds, but intermittently a single execution takes over 40 minutes and causes database impact. The code that produces this statement was written to cap each UPDATE at a fixed batch size, but the cap doesn't take effect. Each UPDATE can therefore carry an unbounded number of sys\\_ids, which produces the intermittent long-running statements.\n\n | \n\n \n\n |
| \n\nSoftware Spend Detection\n\n PRB2040404\n\n | \n\nUpgrades to spend detection\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSource Control Engine\n\n PRB2054438\n\n | \n\nA re-link of a customized Store app to git via Source Control fails with an error code '1030'\n\n | \n\nThe application should link to the git repository without the error code 1030 occurring.\n\n | \n\n1. Provision two instances \\(DC/TD\\) with apprepo setup and at least 1 instance with midserver.\n2. Create an application in the instance.\n3. Publish that application.\n4. Now the instance with midserver, install the published application.\n5. Make a change in that application.\n6. Source control this application to git using a MID server.\n7. Delete the sys\\_repo\\_config for this application this will un-link the application from git.\n8. Attempt to link to the source control again to the same repository using a mid server.\n\n Expected behavior: The application smoothly links to the git repository.\n\n Actual behavior: The error code 1030 occurs.\n\n |
| \n\nStream Connect Core\n\n PRB2054184\n\n | \n\nStream Producer update\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSystem Archiving\n\n PRB1974369\n\n | \n\nCompaction is not working for archived tables in the columnar format\n\n | \n\nAn error occurs after migrating the columnar format, updating the compaction properties, and running the background script.\n\n | \n\n1. Migrate ar\\_ table to columnar format.\n2. Update the compaction properties.\n3. Run the background script, 'new GlideTableCompactor\\(\\).compact\\('tableName'\\);'\n\n Notice that there is an error, 'Table didn't compact as... Sys\\_id not indexed on root storage table.'\n\n |
| \n\nSystem Archiving\n\n PRB2056839\n\n | \n\nCompaction should not be attempted for columnar tables\n\n | \n\n \n\n | \n\n1. Migrate ar\\_ table to columnar format.\n2. Update compaction properties.\n3. Run the background script.\n\n Expected behavior: Compaction should be blocked because this is a columnar table.\n\n Actual behavior: The error occurs, 'Error: Table didn't compact as... Sys\\_id not indexed on root storage table.'\n\n |
| \n\nSystem Events\n\n PRB2063610\n\n | \n\nFor NowMQ redistribution, extend the UI-only participation property to a comma-separated, node-type exclusion list\n\n | \n\nCurrently, UI nodes don't participate in NowMQ event redistribution/delegation by default. A property \\(nowmq.allow.ui.node.redistribution, default false\\) was introduced previously to let UI nodes opt in to participating in delegation. Dedicated worker nodes exclusively process P0-P4 flow engine event jobs for a tighter SLA \\(~20s\\). These dedicated nodes should process events routed directly to them, but must not receive delegated/redistributed events from other nodes. Accepting the delegated load would consume capacity reserved for the dedicated workload. Health-statistics and check-in from NowMQHealthMonitor currently don't account for this.\n\n | \n\n1. Provision a dedicated worker node type \\(for example, Worker.EmOnly.Primary\\) intended to exclusively process P0-P4 flow engine jobs.\n2. Note that NowMQHealthMonitor still sends check-in/health stats for this node to the delegator.\n\n Observe that the delegator can still delegate other P5+ events to this node, since only UI nodes are excluded today via nowmq.allow.ui.node.redistribution. This consumes capacity reserved for the dedicated P0-P4 workload.\n\n |
| \n\nSystem Events\n\n PRB2068908\n\n | \n\n'Flow Engine Interactive Event Handler' jobs shouldn't participate in thread pool event processing\n\n | \n\nThe flow.fire events should be processed by either two threads or by the three 'Flow Engine Event Handler' jobs. Instead, the P5 events are processed by the 'Flow Engine Interactive Event Handler' jobs that are reserved for P0-P2 event processing.\n\n | \n\n \n\n |
| \n\nSystem Events\n\n PRB2080453\n\n | \n\nNowMQ events never get delegated on Worker.Default nodes due to a broken participation check\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSystem Import Sets\n\n PRB2053898\n\n | \n\nThe import set telemetry is causing 3 extra queries per import set row\n\n | \n\n \n\n | \n\n \n\n |
| \n\nSystem Import Sets\n\n PRB2073197\n\n | \n\nParallel loading on a data source overrides scheduled import 'Run as' user context on sys\\_import\\_set records\n\n | \n\nWhen a scheduled\\_import\\_set is configured with a data source that has enable\\_parallel\\_loading = true, the resulting sys\\_import\\_set record is created with sys\\_created\\_by = system instead of the user specified in the **Run as** field of the scheduled\\_import\\_set. This causes the import to execute in global domain context, breaking domain separation for staging table records.\n\n | \n\n1. Create a data source with enable\\_parallel\\_loading = false.\n2. Create a scheduled\\_import\\_set with **Run as** set to a domain-specific user.\n3. Execute the scheduled import.\n\nObserve the sys\\_import\\_set record sys\\_created\\_by = the **Run as** user.\n\n4. Change the data source to enable\\_parallel\\_loading = true.\n5. Execute the scheduled import again.\n\n Observe the sys\\_import\\_set record sys\\_created\\_by = system \\(incorrect\\)\n\n |
| \n\nSystem Web Services\n\n PRB2074287\n\n | \n\nTelemetry Data Connector update\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSystem Web Services\n\n PRB2074288\n\n | \n\nAction fabric metering for billing\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nSystem Web Services\n\n PRB2074289\n\n | \n\nUpdate for the AF Usage Dashboard app\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nTime Card Management\n\n PRB2051508\n\n [KB3139332](https://hi.service-now.com/kb_view.do?sysparm_article=KB3139332)\n\n | \n\nThe **user.manager** field shows as empty when opening the 'Pending Approval' module for Time sheets\n\n | \n\nThe filter is empty for the **user.manager** field.\n\n | \n\n1. Impersonate a user with submitted time sheets.\n2. Navigate to **Time Sheet** > **Pending Approval**.\n\n Notice that the filter shows empty for **User.Manager**.\n\n |
| \n\nTrace Collector - Family Release\n\n PRB2059215\n\n | \n\nAzure classic trace collector doesn't consider Credential IDs for AI and ML services\n\n | \n\nAzureTraceCollector ignores credential IDs supplied as configuration update parameters. It only considers credential alias names.\n\n | \n\n \n\n |
| \n\nTrace Collector - Family Release\n\n PRB2074229\n\n | \n\nTrace collector MID code for Google Cloud custom agents\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nTrace Collector - Family Release\n\n PRB2081553\n\n | \n\nConvert app-domain-util app as a hosted plugin\n\n | \n\n \n\n | \n\n \n\n |
| \n\nTransaction Management\n\n PRB2035673\n\n | \n\nGIG path doesn't block requests to /WEB-INF and /META-INF, which is a Servlet Spec 10.5 violation\n\n | \n\nIt's expected that all requests return HTTP 404. Instead, requests sent through GIG pass through to the servlet/filter chain.\n\n | \n\nScenario 1:\n\n 1. Start a Glide instance with GIG enabled.\n2. Send a request to a protected path through GIG: 'curl -v h gig-host:gig-port/WEB-INF/web.xml'.\n\n Observe that the request reaches the servlet layer instead of being rejected with 404.\n\n Scenario 2:\n\n 1. Start a Glide instance.\n2. Send the same request directly to the Tomcat port \\(bypassing GIG\\).\n\n Observe that Tomcat returns 404 \\(blocked by StandardContextValve\\).\n\n |
| \n\nTransaction Management\n\n PRB2068154\n\n | \n\nRemove glide.gig.enable from the property list so a default xml record can be shipped\n\n | \n\nThe glide.gig.enable property isn't present, despite this record. Also, the com.glide.gig plugin is installed.\n\n | \n\nProvision a new instance on the main branch.\n\n Notice that the glide.gig.enable property isn't present, despite the record and the fact that the com.glide.gig plugin is installed.\n\n |
| \n\nTransaction Management\n\n PRB2070038\n\n | \n\nThe semaphore usage metric \\(semaphore mean\\) reports the gateway fixed thread pool usage when Glide Ingress Gateway \\(GIG\\) is turned on. This inflates the value and triggers false monitoring alerts\n\n | \n\nWhen GIG is turned on, the semaphores\\_used metric \\(xmlstats semaphores mean; legacy cmdb\\_metric\\_semaphores.semaphores\\_mean\\) reports much higher values than in non-GIG mode. This is because the metric is measuring the shared gateway fixed thread pool instead of the legacy per-node semaphore pool. Monitoring alerts keyed on semaphore mean fire spuriously.\n\n | \n\n \n\n |
| \n\nUI Field Administration\n\n PRB1948198\n\n | \n\nThe Service Operations Workspace \\(SOW\\) **Template creation** field dependencies are working inconsistently\n\n | \n\nWhen users fill out templates for incidents, the behavior of the dependent fields such as **Category** and **Subcategory** are inconsistent. If the user creates the template from a pre-existing record, they will be able to see the proper subcategory options unless they attempt to change the category on the new template.\n\n | \n\n1. Open a base instance.\n2. Open Service Operation Workspace.\n3. Open a new incident.\n4. From right contextual sidebar, select the **Templates** icon.\n5. Create a new template.\n6. Add the **Category** and **Subcategory** fields if it isn't already there.\n7. Set the **Category** field.\n8. Try to set the **Subcategory** field.\n\n Observe that the user doesn't see options that should be there, such as CPU, Disk, Mouse.\n\n |
| \n\nUI Field Administration\n\n PRB2024073\n\n | \n\nAn **HTML type** field doesn't always display as full size when its in read-only\n\n | \n\nWhen creating an **HTML type** field and applying a UI policy or client script to make it read-only, it doesn't always show its full size. It shows in a collapsed form until the entire page is refreshed.\n\n | \n\n1. Open an Australia instance.\n2. Navigate to **incident.LIST**.\n3. Open any incident which is in the 'In progress' state.\n4. Under 'Sections', navigate to **Related Records**.\n\n Expected behavior: The field value should get displayed fully in read-only mode.\n\n Actual behavior: The field doesn't show its full size, and it gets collapsed.\n\n |
| \n\nUI Field Administration\n\n PRB2040359\n\n | \n\nThe 'Attachments' component isn't working for multiple files when the 'Show preview' modal during an upload option is turned off\n\n | \n\nWhen the option on 'properties' show the preview modal, the upload is disabled when attempting to upload multiple files, and does not work.\n\n | \n\n1. Open any workspace in UI Builder.\n2. Add an attachment component.3. Leave the option.\n3. Allow 'Multiple file upload' enabled.\n4. Disable 'Show preview modal during upload.'4. Test this the workspace, attaching multiple files at once.\n\n Observe that only one file gets uploaded.\n\n |
| \n\nUI Field Administration\n\n PRB2073310\n\n | \n\nSupport the **Markdown** field type in UI16, Seismic, and LIT\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUI Field Administration\n\n PRB2082758\n\n | \n\nThe Advanced Qualifier Reference is getting skipped while doing a List edit operation for a **Reference** field\n\n | \n\n \n\n | \n\n1. In incident table, set up advanced reference qualifier for 'Assigned to field'.\n2. On SOW workspace, navigate to the incident list.\n3. Try to list edit the assigned to field.\n4. Select the **Look up** icon.\n\n Expected behavior: The advanced reference qualifier should be applied.\n\n Actual behavior: Advanced reference qualifier is getting skipped.\n\n |
| \n\nUpgrade Center\n\n PRB2016580\n\n | \n\nAfter upgrading instances from Zurich to Australia, several records show up on the skipped list belonging to the sn\\_glider or sn\\_build\\_agent. It shows the error 'Unable to compare, unable to find a current record'\n\n | \n\nAfter upgrading a Zurich instance to Australia the upgrade monitor will have a list of skipped records. But when trying to resolved issue, users observe the error: 'Unable to compare, unable to find a current record' when trying to compare to current.\n\n | \n\n1. Provision a Zurich instance.\n2. Make sure that the plugin sn\\_glider and sn\\_build\\_agent are not on the latest version.\n3. Upgrade the instance to Australia.\n4. Post upgrade review the skipped records.\n5. Filter for scripts or records that are part of the sn\\_glider or sn\\_build\\_agent.\n6. Open a record that is skipped and click on the UI action Compare to Current.\n\n Observe the error.\n\n |
| \n\nUpgrade Center\n\n PRB2075225\n\n | \n\nCloning an AI-generated sys id in the client script causes zboot errors\n\n | \n\n \n\n | \n\n \n\n |
| \n\nUpgrade Center\n\n PRB2076321\n\n | \n\nApply defaults on the loading of XML records with apply\\_defaults=true attribute\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nUX Framework\n\n PRB2028133\n\n | \n\nThe alm\\_asset form breaks when configuring the **Activity** fields due to a service worker error\n\n | \n\nThis issue was observed when using Firefox V90.0.2 from locked down dev versions.\n\n | \n\n1. Navigate to **alm\\_asset.do**.\n2. Fill in the mandatory fields.\n3. Save the record.\n4. In the 'Activity tab', select the **Filter** button.\n5. Select **Configure Available Fields**.\n6. Add or remove the **Comments** field.\n7. Save it.\n\n Observe that the URL will stay in slushbucket.do and the form will be broken or blank. Buttons such as the **Filter** in the Activity stream and **Reference** icons will be broken, causing the test failure.\n\n |
| \n\nUX Framework\n\n PRB2054946\n\n | \n\nKeyboard shortcut remapping for admins and users\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nVersatile Node and Cluster Configuration\n\n PRB2072954\n\n | \n\nFrontend Service for Glide POC\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nVersatile Node and Cluster Configuration\n\n PRB2080145\n\n | \n\nGIG ports can reorder glide nodes and select the wrong default database\n\n | \n\nMulti-node Glide ITs can select a different default Glide node when GIG is enabled. GlideNodeScanner sorts nodes using GlideNode.getPort\\(\\), but getPort\\(\\) intentionally returns the effective ingress port. Because GIG ports are allocated independently, enabling GIG can reverse node order even though the Glide topology is unchanged. This caused VirtualAgentTimeoutConversationsIT on track/tsmgmtalpha to open the second isolated database through GIG, while AC\\_UpdateSetIT had activated the Virtual Agent public-page records only in the first database. The browser received 302 /session\\_timeout.do and stalled waiting for VA initialization.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB1980327\n\n | \n\nA chat dynamic greeting isn't localized correctly\n\n | \n\nThe message doesn't go down the correct API path to resolve to sys\\_ui\\_message, so it can't honor the dynamic greeting.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB1999511\n\n | \n\nMessage preview and unread badge count don't work upon page refresh\n\n | \n\nWhen the user refreshes the page, the message preview doesn't show up. On standard chat, there's also no unread badge count.\n\n | \n\n1. Navigate to /sp.\n2. Query 'What is spam'.\n3. While standard or enhanced chat is processing, close the VA.\n\nObserve that there is an unread badge count \\(1\\) and the message preview pops up.\n\n4. Refresh the page.\n\n Expected behavior: There is still an unread badge count and the message preview shows up.\n\n Actual behavior: The message preview doesn't show up. On standard chat, there's also no unread badge count.\n\n |
| \n\nVirtual Agent\n\n PRB2013952\n\n | \n\nRemove the deprecate system property 'com.glide.cs.conversation.entity.cache.enabled'\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2014908\n\n | \n\nThe unread message notification and message preview are not displayed for the users\n\n | \n\nThe user should see the notification of the unread message on the **Engagement Messenger \\(EM\\) Launch** Icon. The message preview popup should be displayed when the EM is closed and then logged in again.\n\n | \n\n1. Log in to the instance as admin.\n2. Navigate to **Engagement Messenger \\(EM\\)** > **Modules**.\n3. Ensure the module is activated.\n4. Setup an asynchronous chat.\n5. As an agent, log in as Abel Tuter.\n6. Navigate to the **/now/cwf/agent/inbox**.\n7. Mark the agent status as 'Available'.\n8. Open the EM page in new window.\n9. 4. Log in as Abraham Lincoln.\n10. Select **Start a Chat** > **Show me everything** > **Live Agent Support**.\n11. In the Agent window, accept the chat to start the conversation.\n\nObserve that as Abraham Lincoln, the agent greeting message appears.\n\n12. Close the EM window.\n13. As an agent, send a message to Abraham Lincoln.\n\n Observe that in the EM page, Abraham Lincoln doesn't receive the notification of the unread message on the **EM Launch** icon. The message preview is also not displayed when the EM is closed and then logged in again.The user gets a notification sound, but the notification is not displayed.\n\n |
| \n\nVirtual Agent\n\n PRB2033259\n\n | \n\nThe Language detection doesn't work properly with Agentic mode for both the standard and Enhanced chat\n\n | \n\n \n\n | \n\n1. Setup NAVA on latest track/bnowassist.\n2. Install 'Dynamic Translation for Virtual Agent' and the Spanish language plugins.\n3. Open the 'sys\\_now\\_assist\\_deployment\\_channel' table.\n4. Set 'experience' to 'Chat widget' for Service Portal.\n5. Navigate to **Conversation** > **Settings/assistants**.\n6. Set the display experience to 'Standard' for Service Portal.\n7. Enable the language detect in **Conversation** > **Settings** > **Virtual-agent** > **Parameters** > **Ace-nav** > **Virtual-agent**.\n8. Turn on Dynamic Translation in now-assist-admin/language-region.\n\n Notice that language detection doesn't work.\n\n |
| \n\nVirtual Agent\n\n PRB2035888\n\n | \n\nA Guardian-triggered async\\_search early-return leaves a stale task ID in the context\n\n | \n\nThe second utterance result becomes dropped.\n\n | \n\n1. Send a prompt that Guardian flags.\n\nObserve that it's displayed correctly. Also, observe that the first request is still active but times out later.\n\n2. Send a second utterance that triggers skill Discovery immediately.\n3. Wait for a timeout from the first message to occur to display a 'sorry' message in the conversation.\n\n Expected behavior: The second utterance responds normally.\n\n Actual behavior: 'Sorry, there was a problem on my side' appears. The second utterance result is dropped.\n\n |
| \n\nVirtual Agent\n\n PRB2037636\n\n [KB3108272](https://hi.service-now.com/kb_view.do?sysparm_article=KB3108272)\n\n | \n\nAgent messages containing URLs aren't displaying correctly in the internal transcript\n\n | \n\n \n\n | \n\nRefer to the listed KB article for details.\n\n |
| \n\nVirtual Agent\n\n PRB2051719\n\n | \n\nExecuting the topic from \\_na\\_max\\_wait\\_time\\_ fails with an exception when transferred chat times out\n\n | \n\nAn error message occurs and an exception appears in the logs.\n\n | \n\n1. In Enhanced Chat, transfer to a live agent.\n2. As another agent user, accept the chat.\n3. Transfer the chat to another queue using the /tq quick action.\n4. Do not accept the chat and allow max wait time topic to trigger.\n5. When prompted, select the topic.\n\n Expected behavior: The topic executes successfully.\n\n Actual behavior: The message, 'I'm having technical issues and won't be able to continue this conversation' is shown and an exception is in the logs.\n\n |
| \n\nVirtual Agent\n\n PRB2052769\n\n | \n\nThere's a 'sorry' message after a user tries to enter a different topic after a survey message\n\n | \n\nUsers receive a 'sorry' error message when attempting to continue a conversation after the survey prompt appears, such as by asking a new question or creating an incident. The issue occurs because the survey handling logic incorrectly classifies non-feedback responses, causing the survey to be re-triggered and the conversation to terminate unexpectedly. This prevents users from completing their intended actions and causes the chat session to end unexpectedly.\n\n | \n\n1. Enable the survey in Enhanced Chat.\n2. Run an agentic execution.\n3. After the survey is presented, continue the chat and ask something else.\n\nNotice that the survey should not be shown again.\n\n4. Ask for a live agent.\n5. If the agent is not available and the incident option is shown, try to create an incident.\n\n Notice that it errors out and closes the conversation.\n\n |
| \n\nVirtual Agent\n\n PRB2057199\n\n | \n\nFollow-up questions from the APM Home **Ask Otto** button hangs indefinitely for the Q&A agent\n\n | \n\n \n\n | \n\n1. Select the **Ask Otto** button \\(ai-sparkle icon\\).\n2. Notice that the greeting appears in NAP after ~12 seconds: 'Hello – I'm Enterprise Architecture Explorer for Analysis and Queries, and I'm ready to help...'\n3. Enter the following: 'list all capabilities associated with 'Deliver Services''.\n4. Hit **Enter**.\n\n Notice that the spinner appears briefly, then stops, and no response shown.\n\n |
| \n\nVirtual Agent\n\n PRB2058703\n\n | \n\nGenerating a KB article throws an error\n\n | \n\nThe following error appears: 'Configured callback URL for the KB generation topic is invalid.'\n\n | \n\n1. Create an instance, following the documentation for setting up NextWave instances.\n2. Navigate to now-assist-admin.\n3. Make sure the KB Generation skill is active and the display for NAP\\(OTTO\\) channel is active.\n4. Give the prompt 'Create the KB for INCXXXXXXX' or 'Generate KB article'.\n\n Observe that there are three potential outcomes. First, the AI output could be: 'I wasn't able to generate the KB article because the configured callback URL for the KB generation topic is invalid'.\n\n Second, the AI output could be: 'I will help you create a knowledge article. Let me first retrieve the incident details to understand what information should be included in the KB'. Then the execution stops. It doesn't collect any information nor create any article. The error code is 200102.\n\n Finally, it might not use the KB Generation skill. Instead, it uses knowledge graph or basic reasoning to form a draft article in the NAP window.\n\n |
| \n\nVirtual Agent\n\n PRB2059089\n\n | \n\nThe Otto session isn't aware of the logged-in user for 'assets managed by me' queries\n\n | \n\nThe Otto/AICT chat session isn't aware of the logged-in user by default. When a user asks a question like 'Can you give me the assets managed by me?', the assistant returns the complete/unfiltered list of assets. Instead, it should apply a managed\\_by = current user filter. The filter is only applied when the user explicitly names themselves in the query. The assistant should recognize 'me'/'my' references. It should automatically apply the logged-in session user's context without requiring explicit clarification.\n\n | \n\n1. Log in as an AICT user.\n2. Ask Otto, 'Can you give me the assets managed by me?'.\n\nObserve that the full/unfiltered asset list is returned instead of being filtered to the current user.\n\n3. Ask explicitly by name, for example: 'assets managed by username '.\n\n Observe that the managed\\_by = current user filter is correctly applied.\n\n |
| \n\nVirtual Agent\n\n PRB2059128\n\n | \n\nIn Language Detection, the loaded choices remain in the wrong language after switching from English to French via the Conversational catalog\n\n | \n\nWhen Language Detection is enabled, it automatically switches the conversation language from English to French after receiving 'Bonjour'. The user observes that the reference variable choices and loaded values appear in the wrong language \\(English\\) instead of French.\n\n | \n\n1. Configure NextWave-Conversation-Server with Language Detection enabled.\n2. Set the Topic Block and Agent Execution priority, with Agent Execution higher priority.\n3. Use a conversational catalog item with a 'reference' variable type.\n4. Start the chat in the English profile/session language.\n5. Send the message 'Bonjour' to trigger Language Detection.\n6. Verify that the chat language switches to French.\n7. Wait for the French question to load \\(with reference variable choices\\).\n\n Observe the loaded choices for the reference variable.\n\n |
| \n\nVirtual Agent\n\n PRB2059632\n\n | \n\nBuildPolicyConfig should be aligned with sys\\_now\\_assist\\_va\\_persona\\_detail schema\n\n | \n\nNo policy configs are returned because buildPolicyConfig doesn't target sys\\_now\\_assist\\_va\\_persona\\_detail and doesn't filter by persona\\_detail\\_type = Policy.\n\n | \n\n1. Create an active record in sys\\_now\\_assist\\_va\\_persona\\_detail:\n - Deployment = a valid deployment sys\\_id.\n - Persona\\_detail\\_type = Policy.\n - Name = Test Policy.\n - Description = Test policy description.\n - Prompt\\_value = Test policy instruction.\n2. For the same deployment, create another active persona-detail record with persona\\_detail\\_type = Tone and prompt\\_value = Friendly.\n3. Trigger the assistant-config handshake for that deployment via next wave.\n4. Inspect policyConfigs in the response.\n\n Expected behavior: One policy config entry is returned, containing the sys\\_id, name, description, active, and instruction from the policy persona-detail record. Non-policy persona-detail records are excluded.\n\n Actual behavior: No policy configs are returned because buildPolicyConfig doesn't target sys\\_now\\_assist\\_va\\_persona\\_detail and doesn't filter by persona\\_detail\\_type = Policy.\n\n |
| \n\nVirtual Agent\n\n PRB2060579\n\n | \n\nLink is broken for showing ticket details in the Otto chat\n\n | \n\nThe URL is incorrect when the user selects the link in the card when using the Otto chat.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2060897\n\n | \n\nThe 'promoted-skills' API doesn't return non-discoverable skills\n\n | \n\n \n\n | \n\n1. Create a skill.\n2. Call the 'promoted-skills' API.\n\n Expected behavior: The skill should be returned.\n\n Actual behavior: The skill isn't returned.\n\n |
| \n\nVirtual Agent\n\n PRB2061042\n\n | \n\nFixes are needed for guest user support for OffGlide\n\n | \n\nAdditional rest endpoints need a public role. The NextWave token needs to be turned on for bff exchange.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2061520\n\n | \n\nCalling the 'Bg channel' API with the same session ID isn't resuming the conversation\n\n | \n\n \n\n | \n\n1. Create a incident and assign it to the ZTSD worker.\n2. Once solution is proposed, reply with new comments.\n\n Expected behavior: The conversation, which is waiting for input, should resume back.\n\n Actual behavior: Creating a conversation and execution plan with the workflow as 'Default VA Workflow'.\n\n |
| \n\nVirtual Agent\n\n PRB2062579\n\n | \n\nThe OneApi/OneExtend 60-second execution timeout causes silent failures with no graceful error handling for users\n\n | \n\nWhen the OneExtend capability execution exceeds the 60-second Transaction.executeWithTimeout budget in FlowObjectExecutor.executeQuick, the platform cancels the transaction silently. The user receives no structured error response and the user sees the UI stuck with no feedback.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2063396\n\n | \n\nParallel tools execution aren't running in record domain\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2064355\n\n | \n\nAuto Chat executions are faulted\n\n | \n\nThere is an intermittent failure in fetching the JWT token from CS, which is causing the faulted conversations.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2064833\n\n | \n\nA domain is set to null after user input\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2065894\n\n | \n\nTopic slot filling sometimes does not work\n\n | \n\n \n\n | \n\n1. Open NAP.\n2. Ask, 'I want to order a coffee. Dark roast and hot.'\n\n Notice that it is still asking the user if it is hot or cold, when it should've been filled from the utterance.\n\n |
| \n\nVirtual Agent\n\n PRB2066077\n\n | \n\nAdd the reduce\\_items\\_list\\_polling toggle\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2066110\n\n | \n\nWhen ending the conversation, it moves the interaction to a 'Closed Abandoned' state without starting the conversation after creating it using CREATE\\_CONVERSATION\n\n | \n\nThe interaction moves to a 'Closed Abandoned' state instead of a 'Closed Complete' state.\n\n | \n\n1. Create a conversation using the CREATE\\_CONVERSATION action.\n2. Pass the context variables live\\_agent only to 'true'.\n3. End the conversation using the END\\_CONVERSATION action without starting the conversation\n\n Expected behavior: The interaction must move to 'Closed Complete' state.\n\n Actual behavior: It is moving to a 'Closed Abandoned' state.\n\n |
| \n\nVirtual Agent\n\n PRB2066112\n\n | \n\nUPDATE\\_CONTEXT\\_VARS is not working when used immediately after CREATE\\_CONVERSATION\n\n | \n\nAn error is thrown, and context variables must be updated with out any errors.\n\n | \n\n1. Create a conversation using the CREATE\\_CONVERSATION action.\n2. Try updating context variables using UPDATE\\_CONTEXT\\_VARS immediately after the creating conversation.\n\n Notice that it is throwing error.\n\n |
| \n\nVirtual Agent\n\n PRB2069447\n\n | \n\nSemantic filtering Virtual Agent global flags aren't set when invoked from AO via topic tool execution\n\n | \n\n \n\n | \n\n1. Start a NextWave conversation.\n2. Trigger sensitive detection for HR fallback.\n3. Select **Create case**.\n4. When prompted for a description on the case, provide the same utterance that triggers semantic detection.\n\n Expected behavior: It proceeds and creates a case.\n\n Actual behavior: The user utterance is flagged for semantic filtering.\n\n |
| \n\nVirtual Agent\n\n PRB2069651\n\n | \n\nThe client hangs without feedback when exceptions are thrown in the OGCS layer during topic callback processing\n\n | \n\nDifferent exceptions throughout the flow must be caught and a feedback message has to be sent to client so that the client doesn't hang.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2069708\n\n | \n\nUsers don't see logged in user details passed for DARE in skuld\n\n | \n\n \n\n | \n\nFrom the Now Assist Portal, ask a simple question such as 'who am i'.\n\n Observe that it produces incorrect results along without passing user context.\n\n |
| \n\nVirtual Agent\n\n PRB2070048\n\n | \n\nThere's an OGCS error on skillPicker due to bad sys\\_gen\\_ai\\_skill data\n\n | \n\n \n\n | \n\n1. Add a sys\\_gen\\_ai\\_skill record which doesn't have a valid skill\\_document ID.\n2. Attempt to run a valid topic.\n\n Expected behavior: A topic should execute and log warning message that there's an invalid sys\\_gen\\_ai\\_skill record.\n\n Actual behavior: A topic won't execute.\n\n |
| \n\nVirtual Agent\n\n PRB2070336\n\n | \n\nA guest user isn't able to upload images\n\n | \n\nTwo issues prevent a guest user from uploading images: the conversation-server returns a 500 error due to a table level ACL on sys\\_cs\\_conversation and conversation-server returns a 401 error: 'unable to find guest session - Guest cookies are not passed through to upload request'.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2072690\n\n | \n\nSupport workspace tags derivation from workspace/page URL in DARE + KG\n\n | \n\nDARE and KG does not support workspace tags.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2073250\n\n | \n\nA conversation from another domain doesn't work if the user default domain doesn't have access to the current session domain\n\n | \n\nWhenever there is a hybrid queue into play, the worker impersonates the user and updates the session, but doesn't touch the domain. When impersonated normally, the domain will be the default domain for the user. This might no have access to the conversation because its started in a different domain. So whenever we read some data that is not accessible like conversation, the flow fails.\n\n | \n\n1. Enable domain separation.\n2. Update any field on a user record.\n\nOnce updated, the default domain to the user moves to TOP/Default unless specified.\n\n3. Switch the domain to a different domain \\(some sibling domain or a parent domain\\).\n4. Start the conversation.\n\n Observe the responses would not be received for any query.\n\n |
| \n\nVirtual Agent\n\n PRB2073833\n\n | \n\nThe AiAgentSecurityHelper lacks an API to create compound deny\\_unless security-attribute ACLs, blocking sn\\_voice\\_aia from securing voice agent endpoints\n\n | \n\nThere must be a gate for sn\\_voice\\_aia for certain voice agent endpoints behind a compound ACL using a custom security attribute with a deny\\_unless decision policy. A compound ACL with deny\\_unless requires setting 'decision\\_type', 'local\\_or\\_existing', and 'security\\_attribute' on sys\\_security\\_acl. Scoped apps cannot do this directly, and a global helper is required.\n\n | \n\n1. Open an instance with com.sn.voice\\_aia and com.glide.cs.genai installed.\n2. Attempt to configure a voice AI agent endpoint that requires compound ACL security, specifically an ACL using a custom security attribute with a deny\\_unless decision policy.\n3. From the sn\\_voice\\_aia scope, call new AiAgentSecurityHelper\\(\\).createAclWithSecurityAttribute\\(...\\) to delegate compound ACL creation to the global helper.\n\n Expected behavior: sn\\_voice\\_aia should be able to delegate compound ACL creation to the global AiAgentSecurityHelper utility, the same as it does today for role-based ACLs via createAclAndRoles.\n\n Actual behavior: The method does not exist on AiAgentSecurityHelper. sn\\_voice\\_aia cannot create sys\\_security\\_acl records with compound security attributes directly from a scoped context.\n\n |
| \n\nVirtual Agent\n\n PRB2074044\n\n | \n\nSupport 10 files and a total support of 50 MB for PDF native, PDF OCR, Word, PPTX, Excel, CSV, TXT, JPEG, PNG\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2074992\n\n | \n\nHandshake fails when duplicate preferred-skill entries exist for the same skill\n\n | \n\nAn error message occurs and an exception is found in the logs.\n\n | \n\n1. In Enhanced chat, transfer to a live agent.\n2. As another agent user, accept the chat.\n3. Transfer the chat to another queue using the /tq quick action. Do not accept the chat and allow max wait time topic to trigger.\n4. When prompted, select the topic.\n\n Expected behavior: The topic executes successfully.\n\n Actual behavior: The message, 'I'm having technical issues and won't be able to continue this conversation' is shown and an exception is in the logs.\n\n |
| \n\nVirtual Agent\n\n PRB2076214\n\n | \n\nA java.lang.NullPointerException occurs, 'Cannot invoke 'com.glide.script.GlideRecord.setValue\\(String, Object\\)' because 'gr' is null'\n\n | \n\nThis issue was observed in hiprojectsc while investigating a ZTSD issue.\n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2076609\n\n | \n\nThe 'Timeout conversations' job fails to close conversations on cross domains\n\n | \n\n \n\n | \n\n1. Enable domain separation.\n2. Check the Nextwave service user domain.\n3. Make any update on the user if needed so that the domain gets changed to TOP/Default.\n4. Start a conversation and run a topic.\n\n Observe that it fails.\n\n |
| \n\nVirtual Agent\n\n PRB2077222\n\n | \n\nAn issue in the fallback logic for a re-witten query in SearchAndRerankProcessor\n\n | \n\nThis results in the conversation erroring out.\n\n | \n\n1. Open a zurichcqemonthly10 instance.\n2. Impersonate a user.\n3. Open NAP.\n4. Send 'Summarize CS0000871'.\n\n Notice that the conversation errors out.\n\n |
| \n\nVirtual Agent\n\n PRB2078011\n\n | \n\nThe Virtual Agent greeting is not showing, or shows the wrong message, when the system language is non-English\n\n | \n\nThe session saved in English is shown instead of saving and showing the greeting message created in the Japanese session.\n\n | \n\n1. Set glide.sys.language to 'ja'.\n2. Open VA assistant.\n3. Update the message to something that is not base instance.\n4. In the English session, test the assistant.\n\nNotice that no message is shown.\n\n5. Switch to a Japanese session and save any greeting message.\n6. In the Japanese session, test the assistant.\n\n Observe that the message saved in the English session was shown.\n\n |
| \n\nVirtual Agent\n\n PRB2078683\n\n | \n\nThe Topic execution is not working if the Nextwave user is in the TOP/Default scope\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2081066\n\n | \n\nThe page-not-found issue occurs with all apps and instances\n\n | \n\n \n\n | \n\n \n\n |
| \n\nVirtual Agent\n\n PRB2083220\n\n | \n\nsetCache is not honoring the **Domain** field\n\n | \n\nThis issue occurs when impersonating the actual user.\n\n | \n\n \n\n |
| \n\nVirtual Agent Web Client\n\n PRB2065785\n\n | \n\nThe client sends uiMetadata as 'null' when selecting the 'Stop' button after a page refresh during a Dynamic Loader message\n\n | \n\nWhen a Dynamic Loader message arrives and the page is refreshed while it's still loading, selecting the 'Stop' button after reloading sends a stop\\_flow action message with 'uiMetadata: null' instead of the expected contextual action metadata.\n\n | \n\n1. Start a chat session.\n2. Trigger a flow/skill that sends a Dynamic Loader message.\n3. While the loader is still in progress \\(before it resolves/completes\\), refresh the page.\n4. Wait for the session to restore and the loading state to reappear.\n5. Select the **Stop** button.\n6. Inspect the outgoing message for the stop\\_flow action.\n\n Expected behavior: richControl.uiMetadata should contain the contextual action metadata.\n\n Actual behavior: richControl.uiMetadata is null.\n\n |
| \n\nVisual Task Boards\n\n PRB2059581\n\n | \n\nUsers are unable to move a card from one visual task board \\(VTB\\) to another after an Australia upgrade\n\n | \n\nThe 'Move' dialog does not display any swimlanes.\n\n | \n\n1. Set the system property glide.invalid\\_query.returns\\_no\\_rows to 'true'.\n2. Create two Task Boards:\n - Board A with at least one card\n - Board B with two or more lanes\n3. Open a card on Board A and select **Move**.\n4. In the dialog, select **Board B** as the target Task Board.\n5. Select the **Lane** field and search.\n\n Observe that the dropdown list displays 'No matches found', even though Board B has valid lanes.\n\n |
| \n\nWork Order Management\n\n PRB2066103\n\n | \n\nFix the getLocation API on FSMGeneralUtil and unit tests\n\n | \n\n \n\n | \n\n \n\n |
| \n\nZero Copy Connectors \\(Glide\\)\n\n PRB2073259\n\n | \n\nEpic for glide changes for Rest connector\n\n | \n\nThis is a product update.\n\n | \n\n \n\n |
| \n\nZero Trust Access\n\n PRB2052933\n\n | \n\nUsers are unable to maintain session roles when accessing the VTB dashboard\n\n | \n\nThis issue occurs when an instance has ZTA policies configured with IDP Attributes filter condition used in the Adaptive Authentication policy condition, for any user who access the VTB dashboard with the filter, filterLIKEjavascript^ORfilterLIKEDYNAMIC', and if there is no channel responder record created for it yet. The flow receives an NPE \\(NullPointerException\\), and the roles in the session are not loaded properly. There are no roles for the user causing the user to see the 'Security Restricts Access Prevention' message on screen.\n\n | \n\n1. Ensure the instance has Zero Trust Access \\(ZTA\\) configured with at least one active Adaptive Authentication policy.\n2. Log in to the instance as any non-admin user.\n3. Navigate to any Visual Task Board \\(VTB\\) dashboard that contains a board filter matching.\n4. Confirm that no channel responder record exists for this filter combination.\n5. Load/open the VTB dashboard.\n\n Notice the 'Security Restricts Access Prevention' message occurs.\n\n |
\n