Australia Patch 3
The Australia Patch 3 release contains important problem fixes.
- Australia Patch 3 was released on June 16, 2026.
-
- Build date: 06-12-2026_1106
- Build tag: glide-australia-02-11-2026__patch3-05-25-2026
For more information about the release cycle, see the ServiceNow Release Cycle.
For a downloadable, sortable version of the fixed problems in this release, click here.
Overview
Australia Patch 3 includes 501 problem fixes in various categories. The chart below shows the top 10 problem categories included in this patch.
Changes in Australia Patch 3
- Activate a pre-release feature
- Activate a pre-release feature on the instance so your users can try it out and provide feedback to the product team.
- Activate Data snapshots
-
- Starting with Australia Patch 3, if the instance is eligible, this plugin is installed automatically.
- Activate Data snapshots for each eligible indicator, either one-at-a-time or in bulk.
- Authentication release notes
-
- Email OTP as an authentication factor for AI voice service: Use Email OTP as a standalone factor, a primary factor, or a secondary factor in AI voice agent authentication flows. When a caller reaches the voice agent, a one-time password is sent to their registered email address. The caller provides the password to complete authentication.
- KBA for AI voice service: Use the KBA setup to configure Knowledge-Based Authentication (KBA) for the voice channel. Choose from base system questions at both the identification level and the authentication level. AI voice service mappings are populated automatically from your Assistant Designer selection, so manually mapping voice services is no longer a mandatory step in the KBA setup.
- Authenticate callers at the start of every call: Prompt callers for authentication or identification details at the start of every call, before the voice-only assistant responds to any request, using the Authenticate at the start of the call option on the Assistant Designer's Caller verification page.
- Clone Admin Console release notes
- The ServiceNow® Clone Admin Console application copies data and metadata from one ServiceNow instance to another ServiceNow instance to easily synchronize your instances. Clone Admin Console was enhanced and updated in the Australia release.
- Code Signing actions and required roles
- Reference table of Code Signing actions, their descriptions, and the roles required to perform them.
- Create a Universal Request from the Supplier Collaboration Portal
- Create a Universal Request (UR) in Employee Center when your request involves multiple departments or the right department to contact is unclear.
- Data snapshots and multiple breakdowns
- If you have Australia Patch 3 or later, the plugin is installed automatically on qualified instances.
- Data snapshots jobs and tables
- Instance Eligibility Check Job for Data Snapshots and Instance readiness for Data snapshots Scheduled jobs installed.
- Deactivate a pre-release feature
- Deactivate a pre-release feature if it is not working as expected or if you no longer need the feature.
- Feature Preview Program
- The Feature Preview Program provides access to pre-release capabilities on your instance. You can activate, test, and provide feedback on individual features before they are generally available.
- Hermes background jobs
- These background jobs are associated with Hermes settings. The table lists their default run frequencies and descriptions.
- Hermes Settings page
- The Hermes Settings page is a centralized interface that enables Hermes administrators and maintenance users to monitor and control the configuration properties that govern the Hermes Messaging Service.
- Install Universal Request for Sourcing and Procurement Operations
- Install the Universal Request for Source-to-Pay Operations [sn_fsc_ur_common] plugin to enable the Universal Request in Sourcing and Procurement Operations.
- Limitations and requirements for Data snapshots
- If you have Australia Patch 3 or later, the Data Snapshots (com.snc.pa.mlb) plugin is installed automatically on eligible instances. This includes instances with domain separation, but on such instances the Data snapshots feature is disabled when the first job runs.
- Manage a background job in Hermes Messaging Service
- Manage background jobs in Hermes Messaging Service to control when and how often scheduled tasks run. You can make a job inactive, re-enable it, or adjust its interval from the Hermes Settings page.
- Managing Hermes settings
- View, modify, and manage configuration properties that control the behavior of Hermes Messaging Service. You can update property values, manage background job states, or adjust settings where automated detection is unavailable.
- Performance Analytics release notes
- If you have Australia Patch 3 or later, the Data snapshots plugin is installed automatically if you have RaptorDB Professional. If your instance is also domain separated, the Data snapshots feature is installed but disabled.
- Reviewing prediction errors with the Observability Dashboard
- View this table's records directly by entering ml_predictor_error_logs.list in the navigator.
- ServiceNow AI Platform core feature release notes
-
- The Feature Preview Program provides a centralized location to discover, activate, and test pre-release capabilities on your instance. When a pre-release feature is added to your instance, you receive a notification and can access the Feature Preview Program to review feature details, activate features for testing, and provide feedback.
- Use the Feature Preview Program to choose which pre-release capabilities to activate and test on your instance.
- Theming for AI Search in Service Portal
transparent- Update Hermes messaging settings
- Review and modify the current the Hermes configuration properties to control Apache Kafka integration, topic management, and other messaging behavior.
Notable fixes
The following problems and their fixes are ordered by potential impact to customers, starting with the most significant fixes.
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Change Management PRB2021441 |
Unable to rollback the plugin 'com.snc.itsm. foundation.license _control' |
Refer to the listed KB article for details. |
|
|
Database Persistence - Data Access PRB2007256 |
The text search doesn't return results in non-English languages | After downloading language plugins and switching the system language to a non-English language, results aren't returned when the property 'glide.db_ query.replace_ distinct_with_ groupby' is set to 'false.' When the language is set to English, results are returned. |
Refer to the listed KB article for details. |
|
Password2 Encryption PRB2015257 |
There's excessive growth on the sys_rollback _incremental table and higher binlog generation due to the 'Mass Encryption' job | This causes a large increase in the disk space on the database server. |
Refer to the listed KB article for details. |
|
Related Lists PRB2025356 |
A user can't add records in a related list because of the strict ACL check and missing ACLs for required roles | Users with missing ACLs are not able to add new records in the related list due to a strict ACL check. |
Refer to the listed KB article for details. |
|
Server-side scripts PRB1994381 |
Discovery has issues on some node after upgrading in Australia | After upgrading to Australia, JavaScript running in app nodes fails to call Java functions. The following warning appears: '*** WARNING *** Evaluator: com.glide.script. RhinoEcmaError: undefined is not a function.' This impacts various features, including Discovery and Event Management. |
All other fixes
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Access Analysis Instrumentation API PRB1984283 |
Analyze Access in any record's hamburger menu isn't working | Adding 'access-management' into the URL doesn't work either; it navigates to Access Analyzer's 'Analyze Permissions'. |
Expected behavior: The page redirects to Access Analyzer to analyze that record. Actual behavior: 'The page you are looking for cannot be found'. It navigates using the previous URL. |
|
Access Analyzer PRB1993028 |
(Access Analyzer) Instance scan jobs can hang and are not terminated due to checks not being optimized | Instance scan jobs triggered by the Access Auditor Suite, which is a part of the Access Analyzer (sn_access_analyzer) store application, may hang or fail to terminate. This may cause multiple jobs to accumulate over several days, consuming multiple workers and preventing other jobs from running. This may cause performance issues on the instance. This issue affects Access Analyzer (sn_access_analyzer) versions 6.0.0 through 6.0.5, as well as version 6.1.0. |
Refer to the listed KB article for details. |
|
ACL Engine PRB1998171 |
The store_app_write_audit_acl table was created in a Store app scope instead of the global scope | ||
|
Activity Stream PRB2005727 |
Navigation fails for sources beyond sliding windows in an activity stream | When selecting a citation source in an incident summary response, navigation doesn't work properly if the cited activity (comment or email) is more than three pages away or above the current activity stream view. The user receives a message stating 'The source may be hidden in your current view', even though the source exists and isn't filtered. |
|
|
Activity Stream PRB2008384 |
The Copy button on journal entries doesn't always copy text or notify users correctly | This is reproducible in UI16 and Workspace. |
Expected behavior: When rich text is copied, a notification should display saying 'Copied to clipboard'. When pasted into a plain text editor, there shouldn't be [code] tags around the text. Actual behavior: When rich text is copied, a notification doesn't display, and when pasted into a plain text editor, there shouldn't be [code] tags around the text. |
|
Activity Stream PRB2011415 |
AI skill attribution issue in an activity stream | Activity stream entry grouping logic should account for AI skills registered via setValueWithAuditIdentity. The grouping currently does not use sys_updated_by as the grouping key when UserAgentContext isn't set, so field-level audit entries attributed to distinct AI skill sys IDs along with the session user involved are not getting shown as expected. | |
|
Activity Stream PRB2013162 |
Add filter a configuration, such as a slushbucket | This is a product update. | |
|
Activity Stream PRB2013164 |
Integrate translations into the Java REST API | This is a product update. | |
|
Activity Stream PRB2013167 |
Dynamic translations in the activity stream convert to Lit | This is a product update. | |
|
Activity Stream PRB2013171 |
Create a Java REST API | This is a product update. | |
|
Activity Stream PRB2016617 |
Unguarded Jelly expression in form.xml causes RhinoEcmaError warnings on every classic form load | On any classic UI16 form load, the platform Jelly template evaluator throws a RhinoEcmaError warning in the system log. The warning is present on every classic form, regardless of application scope or record type. There is no functional outage; forms load and save correctly, and all transactions return HTTP 200 with normal response times. The main impact is high-volume system log noise. |
Expected behavior: No RhinoEcmaError warnings are generated during a standard form load. Actual behavior: On forms without an activity stream, one warning entry is generated per form load. On forms with an activity stream, two warning entries are generated per form load. |
|
Activity Stream PRB2018487 |
A citation URL is retained and fields are highlighted when a user logs in to an instance again |
Expected behavior: The citation URL shouldn't be preserved after triggering the citation source flow. Actual behavior: The URL that is created after selecting a citation source is preserved, and causes the citation scroll and highlight to trigger. |
|
|
Activity Stream PRB2023624 |
For the Core UI only, update the activity stream icon for AI specialist vs Agentic Workflow | This is a product update. | |
|
Activity Stream PRB2033885 |
A new activity comment has the type as 'Field changes' instead of 'Comments' |
Note that the comment type (top right of tile) is 'Field changes [dot timestamp]' instead of 'Comments [dot timestamp]'. |
|
|
Advanced Work Assignment PRB1996219 |
The END_WRAP_UP event is published twice when wrap-up is timed out | This behavior causes 'openframe_wrap_up_submitted' to trigger twice, which isn't expected while users are using OpenFrame to handle wrap up with external systems. | |
|
Advanced Work Assignment PRB2026676 |
Enhanced updateSegment API (wrap-up) to support agent-initiated wrap-up | As a CCaaS Developer, the updateSegment API should be able to be used in the CCaaS plugin. This API should allow users to update a wrap-up segment at the same time as closing/updating the segment without requiring a separate API call. This allows the voice plugin to support agent-initiated wrap-up. Agents should have the ability to initiate a wrap-up before the call ends. If the system has wrap-up with a timer, they should get a timer on the wrap-up modal to provide the count down timer until the wrap-up is submitted. | |
|
Agent Chat PRB1992614 |
Dirty screens in Document Object Model (DOM) experience data loss if one of the middle tabs are closed, triggering a screen reorder and refresh | Screens between deleted screens lose edited data due to incorrect DOM detachment/reattachment. When incident is closed, screens 2 and 4 are removed. The updateChildren algorithm uses two-pointer comparison (from both ends). Elements at the ends that match are patched in place, but elements in the middle that need repositioning are moved via insertBefore. This movement triggers a re-render of sn-canvas-screen, and due to vnode-DOM desynchronization (the view renders a p but loadScreen manually replaces it with the macroponent), the section element is destroyed and recreated. This causes hook-insert to fire, which calls loadScreen again, recreating the macroponent and losing all unsaved data. |
See that the focus shifts to an interaction record and the edited field values are lost. |
|
Agent Chat PRB1993857 |
Agent chat inbox notifications appear in HTML | The incident card on the agent chat appears as HTML on a desktop notification. | |
|
Agent Chat PRB2000390 |
The date format is incorrect in the Active Chat window | The date/time format is displayed as 'MMM DD, YYYY HH:MM AM' instead of 'DD-MM-YYYY HH:MM:SS' in the Active Chat window. |
Expected behavior: The date/time format should display as 'DD-MM-YYYY HH:MM:SS' at the top of the Active Chat window. Actual behavior: The date/time format is displayed as 'MMM DD, YYYY HH:MM AM' in the Active Chat window. |
|
Agent Chat PRB2013947 |
Inbox Advanced Work Assignment (AWA) interactions are not presented according to the Configuration field and order for the walkup experience | When an agent receives multiple chats in Service Operations Workspace (SOW), they are initially displayed in descending order, with the most recent chat at the top. However, after a refresh, the chat order appears to change and seeimingly displays in a different order. |
Notice that the chat order is jumbled in a different order. |
|
Agent Chat PRB2014178 |
Optimize the request to fetch previous interactions for a requester to show conversation history in Agent chat | If there are no custom filters, there is no need to create the list of interaction records by going through all the returned records from the DB query. |
Observe that the server memory has gone up significantly. |
|
Agent Chat PRB2021490 |
Enhance the chat desktop notification | When the user selects the new chat message desktop notification, they should get focused back on the workspace tab. The workspace tab that the new chat message belongs to should also be focused and opened. | |
|
Agent Chat PRB2022900 |
AWA workItem responder changes | Update WorkItemResponder's onEnter and OnExit to add and remove notifications in the ui_notification_inbox table. Also, create a system property (glide.awa.work_item.notifications.enabled) to determine whether to show or hide user preference at the agent level. | |
|
Agent Chat PRB2022906 |
Add user preference for app shell notifications | Add support to display a new user preference 'Inbox Workspace Notifications' based on the system property glide.awa.work _item.notifications .enabled. | |
|
Agent Chat PRB2022911 |
Next Experience app shell changes | This is a product update. | |
|
Agent Chat PRB2022913 |
Component inbox logger changes | ||
|
Agent Chat PRB2023682 |
Add the interaction number to desktop notifications to differentiate between interactions | The desktop notification should contain the IMS number to indicate which chat the notification is for. |
Expected behavior: The desktop notification contains the IMS number to indicate which chat the notification is for. Actual behavior: The desktop notification only says that a new chat arrived. |
|
Agent Chat PRB2026678 |
Dynamic wrap-up timer update on the UI when a call has ended | Agents should have the wrap-up timer updated automatically when CCaaS provides the wrap-up context after a call has ended. The wrap-up modal should be refreshed automatically without intervention. The wrap-up modal shouldn't require users to close or open to have the timer count down. | |
|
Agile Development PRB2022589 |
Add 'None' choice to the rm_epic.status field and make it the default for new epics | The Epic Status field (rm_epic.status) currently doesn't include a 'No status' option, which prevents epics from having an unset/neutral status. This causes ambiguity in reporting and makes it difficult to distinguish between epics that have not yet been assigned a status versus those intentionally marked as green, yellow, or red. |
Expected behavior: 'No status' is available as a selectable option to represent epics with no status assigned, enabling accurate status transition tracking for usage analytics. Observed: 'No status' isn't available as an option in the Status field list. Available options are limited to green, yellow, and red. |
|
AI Agents (Glide Family) PRB2011068 |
Data to Glide from offGlide isn't getting logged with the actual user | Any record update or creation doesn't have the created_by or updated_by set as the actual user. |
Make a set cache call to Glide from offGlide. Observe that any record update or creation doesn't have the created_by or updated_by set as the actual user. |
|
AI Agents (Glide Family) PRB2018916 |
AI Agent execution fails with 'Tool access denied' for triggering user after the update set migration | After migrating AI Agents (built in Agent Studio) from a development environment to a client test environment via update set, the agents fail to execute. The triggering user receives an error indicating that they don't have access to the agent's tools, and the agent never starts. |
Observe that the agent fails to start. An error states that the triggering user doesn't have access to the agent's tools. |
|
AI Agents (Glide Family) PRB2022336 |
Caching improvements for NextWave architecture | This is a product update. | |
|
AI Agents (Glide Family) PRB2022344 |
Java changes for conversation history support for a Knowledge Graph tool in AI Agent Studio | This is a product update. | |
|
AI Agents (Glide Family) PRB2022649 |
AI Agents are stuck indefinitely and the facts response is empty | When running AutoEval for the Enterprise Architecture Explorer – Query Agent, the evaluation run gets stuck indefinitely while processing certain questions and datasets. During execution, AutoEval doesn't progress to completion, progress keeps retrying without advancing, and the run never completes successfully. GenAI logs repeatedly show: 'JSON{ "facts": []}Show more lines'. Despite retries, no new facts are generated and the evaluation pipeline makes no forward progress. |
Observe that the evaluation stalls on certain questions, AutoEval keeps retrying internally, and the run never completes. |
|
AI Agents (Glide Family) PRB2025221 |
Cache service intermittently fails and gets calls across different keys | ||
|
AI Agents (Glide Family) PRB2025859 |
The OffGlideScriptObject. generateAuthorizationInfo API creates JSON Web Tokens (JWT) with current session users | The API sn_cs_offglide. OffGlideScriptObject. generateAuthorizationInfo() creates JWT with current user sessions, even though the userID value is passed in the request. | |
|
AI Agents (Glide Family) PRB2025974 |
A user session is logged out when opening AI-generated interaction records | The user session is logged out when opening AI-generated interaction records that were created/updated by the incident_intelligence_agent. The interaction record remains in the WIP state, even though the associated conversation has been marked as faulted. The issue is specific to the in Service Operations Workspace (SOW) workspace view, as opening the same record in platform view works without issue. | |
|
AI Agents (Glide Family) PRB2030410 |
An instance isn't invoking DARE calls due to new properties not being allowed in the cache configuration's invalidation script |
Expected behavior: The response should be received from DARE. Actual behavior: The response is coming from NextWave. |
|
|
AI Agents (Glide Family) PRB2030948 |
Tools using data stream actions aren't able to retrieve data in NAVA |
Observe that the tool isn't able to retrieve data. |
|
|
AI Experience Framework - Glide PRB1980207 |
Implement the logic of 'Mark as read' in the notification | ||
|
AI Experience Framework - Glide PRB1986457 |
The icon color on notifications uses a hard-coded hash value | ||
|
AI Experience Framework - Glide PRB1994093 |
'Mark all as read' isn't working due to GlideRecordSecure and updateMultiple methods being used |
Notice that it's not marking as read in the background. |
|
|
AI Experience Framework - Glide PRB2010223 |
Glide assets release | This is a product update. | |
|
AI Experience Framework - Glide PRB2011879 |
Allow the 'Notification content' table to have separate records per experience | Currently, users can only map a single experience for the portal. Allow the 'Notification content' table to have separate records per experience and also allow content configuration to map multiple experiences. | |
|
AI Experience Framework - Glide PRB2012479 |
AIX Webserver Glide integration | This is a product update. | |
|
AI Experience Framework - Glide PRB2018366 |
/api/now/aiux_service/sysprops doesn't enforce an allowlist | ||
|
AI Experience Framework - Glide PRB2024769 |
Chat gate service uses a GlideRecord query with ACL evaluation, blocking non-admin users from reading the 'Deployment channel' table | In chat-gate-service.js (line 13), the chatEnabled check uses glideRecord_query to query the 'Deployment channel' table. This evaluates all ACLs for the current user, so only admin users have the necessary read access to that table. Non-admin users are blocked from fetching chatEnabled, which prevents the chat from functioning for them. |
Expected behavior: chatEnabled is fetched successfully regardless of the user role. Actual behavior: glideRecord_query evaluates ACLs and denies non-admin users read access to the deployment channel table. |
|
AI Experience Framework - Glide PRB2027126 |
AIX Webserver Glide integration | This is a product update. | |
|
AI Experience Framework - Glide PRB2027128 |
Migration in Glide | This is a product update. | |
|
AI Experience Framework - Glide PRB2027770 |
Remove the 'Applicability' table (sys_aix_applicability) and move the fields applicable for and not applicable for glide_list (user_criteria) into a multi-theme table | This is a product update. | |
|
AI Gateway PRB2010156 |
A scheduled job overwhelms a clickhouse service in sk8s with queries | An app has a scheduled job that runs daily that uses a query service to query AI Gateway data for the previous day. There's a large number of instances querying at the same time (around 12,000), causing every clickhouse node in the cluster to hit its max concurrent query limit and start rejecting incoming requests. | |
|
AI Gateway - Security PRB2024062 |
AI Gateway security Q2 complete feature backport | This is a product update. | |
|
AI Search (Glide) PRB1951236 |
In DirectUserImport, a multiple user match isn't reported | The connectors create user mapping for the first matched user, but not for the second user without reporting an error for the second user. |
|
|
AI Search (Glide) PRB1986147 |
Extend branding properties to support the update to the dynamic landing page 'Search My Servicenow' placeholder | ||
|
AI Search (Glide) PRB2001677 |
A Knowledge Graph (KG) NLQ call should pass the caller ID in the Caller field, not meta |
In an instance with KG, navigate to 'Make a kgnlq query'. Observe one_api_service_ plan_feature invocation. It doesn't match the design with respect to the Caller field. |
|
|
AI Search (Glide) PRB2002346 |
When a KB only has an embedded KBB with embedded_match = false, the KB should send itself instead of the KBB | The KBB content is sent to the LLM instead of KB. |
Expected behavior: The content of the KB is sent to the LLM. Actual behavior: Only the KBB content (defhi) is sent to the LLM. |
|
AI Search (Glide) PRB2006426 |
When a document with an attachment is removed by late binding, the next attachment where the user has access is also removed | When ds_document_version parent documents are filtered by an ACL and their children are skipped (the continue at line 516–518 bypasses the recursive child processing), the sys_attachment sparse cursor falls out of sync. It was built assuming every child would be processed in order, but skipped parents leave gaps. |
Expected behavior: KB3 should be displayed with an attachment. Actual behavior: KB3 is displayed but with no attachment. |
|
AI Search for Service Portal PRB2023882 |
The 'View all results' option isn't available in the chat response shared by assistant |
Expected behavior: The 'View all results' option is visible. Actual behavior: There is no 'View all results' option in the side panel bottom. |
|
|
AI Search UX PRB1989246 |
When records are searched in global search, it isn't opening the form directly | When a user tries to search the incident number in the global search when the zoom size is 150% and left navigator is pinned, then the incident record isn't opening directly. It instead displays a search result page. However, when the zoom size is 100%, then the incident record is opening directly in a form page. |
Expected behavior: Users should see the incident form record directly. Actual behavior: Users are seeing the search results page. |
|
AI Search UX PRB1991340 |
Search input intermittently skips characters | The search input intermittently drops characters when users type quickly, especially under a heavy event load. |
Observe intermittent character loss. |
|
AI Search UX PRB1994212 |
The hidden description in the source code is visible in the chatbot for 'Order guide' and not for 'Catalog item' in Now Assist Virtual Agent (NAVA) | On the catalog item, it's possible to hide the description using the following in the code source: 'div style=''display: none;'' TEXT TO HIDE <p>.' When attempting to do the same in the order guide, it's not working properly in the chatbot, and both texts are visible. This issue occurs only on the chatbot preview of the order guide, and not when consulting it directly from portal. |
|
|
AI Search UX PRB1998976 |
Search event records don't indicate the search mode (keyword, hybrid, or semantic) | When a search is executed in an AIS-enabled portal with Hybrid Search enabled on the corresponding search application, the resulting sys_search_event and sys_search_signal_event records don't capture the search mode (keyword, hybrid, or semantic) that was used to execute the query. This makes it impossible to distinguish query types in search analytics and signal data. |
Observe that neither record contains any field or indicator specifying the search mode used (keyword, hybrid, or semantic). |
|
AI Search UX PRB2000828 |
The 'Async Genius Result Processor' Asynchronous Message Bus (AMB) channel subscription is delayed by session sync contention | The 'Async Genius Result Processor' sys_amb_processor record doesn't have dedicated_session_sync enabled. Without this flag, AMB subscribe transactions for this channel share the same global per-session lock as HTTP transactions. When long-running HTTP transactions are active in the same user session, subscribing to the Genius Result AMB channel is blocked waiting for the session lock, causing delayed delivery of Now Assist results. | |
|
AI Search UX PRB2011697 |
RAG popular search suggestion reader doesn't consider sys_rag_search _suggestion.active | The sys_rag_ search_suggestion records with active=false are still returned. |
Observe that the sys_rag_ search_suggestion records with active=false are still returned. |
|
AI Search UX PRB2012802 |
Indexed source types shouldn't be hardcoded in the API | The AISIndexSourceAPI.fetchIndexingState() method only returns for internal type indexed sources. It should include all indexed sources. | |
|
AI Search UX PRB2014138 |
$sp-search- result-title-highlight --background-color in sp-variables.scss | There is no default assigned for variable '$sp-search- result-title-highlight --background-color'. |
Notice that the variable '--search-result -title-highlight --background-color: $sp-search-result- title-highlight --background-color;' isn't resolved. |
|
AI Search UX PRB2016024 |
Synthesized responses on a mobile sized screen don't display 'Show full answer' after truncation in Zurich on Safari | The answer is truncated without the option to expand: 'Show full answer'. |
Observe that the answer is truncated without the option to expand: 'Show full answer'. |
|
AI Search UX PRB2021873 |
Facets aren't rendered as the sensitivity filter fails quietly | Facets aren't returned because of a failure to fetch hasMatch. |
Observe that facets aren't returned as a result of above line failing to fetch hasMatch. |
|
AI Search UX PRB2024551 |
New/Different experience in the search when AI Search is turned on in the portal level |
Observe that there's no follow up and articles displayed are shown previously in the enhanced chat. |
|
|
AI Search UX PRB2026614 |
Auto-Enable Hybrid Search on Now Assist for Search Installation | When a new users installs the 'Now Assist for Search' plugin, the system should automatically enable Hybrid Search for all search applications configured in the instance. This ensures new users benefit from Hybrid Search by default without requiring manual configuration. The behavior applies to all new user installations going forward and shouldn't retroactively affect existing users who have already installed Now Assist for Search. | |
|
AI Search UX PRB2031624 |
Enhanced Chat's search bar appears on portals with NextWave | Note that the NextWave omni-bar displays on the homepage as expected. However, the search bar from Enhanced Chat is also appearing on other pages unexpectedly. | |
|
AI Service - Glide Interfaces PRB1970597 |
Machine Learning (ML) trainings fail with a 401 error due to ACL errors, unless the 'Predictive Intelligence' plugin is explicitly repaired | When the ML trainer attempts to fetch data from the instance, it receives an HTTP 401 unauthorized error for gml_service, which is resolved after explicitly repairing the 'Predictive Intelligence' plugin. |
Refer to the listed KB article for details. |
|
Analytics Data API PRB1844011 |
Using 'Trend by week' leads to an incorrect record count when the new year starts | When using 'Trend by' with the options 'Opened', 'Calendar', 'Standard Calendar' and 'per-week' and running the report, the record count is 3 but the List view record count is 5. | |
|
Analytics Data API PRB1998034 |
Single score data visualization ignores the 'Apply time series to result' indicator configuration | Starting in the Zurich release, the Single Score Data Visualization with AVG (or SUM) aggregation does not respect the 'Apply time series to result' configuration on formula indicators. When this option is unchecked, the Single Score continues to display the time-series-based result instead of updating accordingly. | |
|
Analytics Data API PRB2003111 |
Pivot table using multiple data sources shows 'No data' on the widget when one of the data sources returns no data | Even though data is available, the chart shows 'No data available'. |
Expected behavior: The chart is rendered and shows the expected data with zeros. Actual behavior: The chart shows 'No data available', despite data being available. |
|
Analytics Data API PRB2005078 |
When using dynamic date ranges, appliedFilters returns incorrect dates |
Notice that data for March is now visible. |
|
|
Analytics Data API PRB2006926 |
Geomap doesn't fetch locationData correctly when the incorrect query gets applied | Locations which have valid data in cmn_location table aren't getting plotted. Every valid location should get plotted correctly. |
Observe that the created Geomap widget doesn't render all the data points and shows an error: 'Some of the data you selected cannot be visualized on the map due to latitude/longitude mapping errors'. |
|
Analytics Data API PRB2020263 |
Remove PowerMock to fix broken tests | ||
|
Analytics Export API PRB1977076 |
There's a blank page when exporting Boxplot data visualizations | Boxplot emits 2 SN_PAR_VISUALIZATION#RENDERED events, but it sends expectedRenderEvents = 1 in the export payload. That's why this fails intermittently when the chart isn't loaded completely. |
Observe that a blank page is displayed. The same issue occurs with an embedded PNG and with PowerPoint files in a dashboard. |
|
Analytics Export API PRB1996615 |
Scheduled export with omit if no records enabled, no attaching the exported file in Email log |
Expected behavior: The exported visualization should be attached there. Actual behavior: Nothing is attached. |
|
|
Analytics Export API PRB2007025 |
Dashboard PDF export doesn't apply dashboard filters on the list | Dashboard filters aren't applied to the list in the dashboard PDF exports. Only the filters configured in the list are honored. |
Observe that the filters are applied correctly on the dashboard to the list, but they aren't applied in the exported PDF. |
|
Analytics Export API PRB2019202 |
Show the total row count in the 'Analytics' list | The list-simple property 'hideTitleRowCount' should migrate to showRecordCount in the new 'Analytics' list. |
Observe that it doesn't migrate to the new list visualization and have the corresponding property set for showing count. |
|
Analytics Export API PRB2023200 |
Hide the export option when its disabled or the roles list is empty | The system provides export on demand functionality at dashboard and data visualization level (server-side) for the Next Experience. There is a need to control the availability of the export option based on system properties and user roles. |
Observe the system checks if the user's role is included in the configured list of roles (if the list is not empty). If the second system property (roles list) is empty, the export feature is available to all users when enabled. If the second system property (roles list) is populated, only users with roles in the list can access the export feature. |
|
Application Manager PRB2020279 |
Users can't uninstall the 'Universal Request' application | After installing the 'Universal Request' plugin, it isn't possible to uninstall it. There is a message stating that it can't be uninstalled because of the dependent plugin 'Universal Request: Reporting'. When attempting to uninstall 'Universal Request: Reporting', we are not able to because 'Universal Request' needs to be uninstalled first: 'This application cannot be uninstalled because one or more applications are dependent on it. In order to uninstall this application, please uninstall the below dependent applications first'. |
See that it isn't possible. |
|
Application Rationalization PRB1990668 |
Malformed sn-lucid-chart-intg.properties | There's a missing comma in a dependency list. |
Confirm that there's no comma before the backslash continuation. |
|
Application Rationalization PRB1993865 |
Base instance business rule fails to exclude the current record during duplicate name validation due to incorrect property reference | The business rule on the cmdb_ci_business_app table incorrectly blocks updates when changing the case of a Business Application name (e.g., 'abc' to 'ABC'). This happens because it uses current.sysId instead of current.sys_id, resulting in an undefined sys_id comparison. |
Expected behavior: The save is allowed because it's the same record, just with a different case. Actual behavior: The save is blocked with the error: 'A Business Application exists with the same name. Please verify.' |
|
Appointment Booking PRB2026901 |
Appointment Booking's scripted mode doesn't consider the territory resource demand feature |
Appointment Booking in scripted mode should consider agent availability based on the territory demand channel association. |
|
|
Asset Management PRB2018791 |
The navigation filter isn't applied correctly | The relevant filter should be automatically applied after navigation. |
Expected Result: The relevant filter is automatically applied after navigation. Actual Result: On navigation, the filter isn't applied. |
|
Attachments to Records PRB2018059 |
GlideSysAttachment. writeContentStream() fails in the Scripted REST API in Australia | GlideSysAttachment(). writeContentStream() fails with 'Can't find method com.glide.ui. SysAttachment. writeContentStream (object,string,string,com. glide.communications. GlideScriptableInputStream)' when called from a Scripted REST API in the Australia release. The issue is not present in Zurich. | |
|
Audit History PRB2019035 |
The sysID of sn_nowassist_skill_config is displayed in the username of the work notes | This issue is observed only in Workspace. In UI16, it's working fine. |
Observe that the sysID of sn_nowassist_skill_config is displayed in the username of the work notes, but it shouldn't be. |
|
Authentication Factors PRB2026011 |
Introduce a new MFA factor, Email OTP | This is a product update. | |
|
Authentication Factors PRB2026012 |
KBA improvements of Platform capabilities | This is a product update. | |
|
Authentication Factors PRB2026014 |
KBA session context persistence | This is a product update. | |
|
Authentication Factors PRB2026015 |
NextWave AI authentication migration to a new authentication service | This is a product update. | |
|
Authentication Factors PRB2026060 |
The kba_session_context value is not in JSON format | The kba_session_context value is logged in this format: '{q1_keyword=q1_user_input, q2_keyword=q2_user_input}'. |
Observe that the kba_session_context value for the third question is logged in this format: '{q1_keyword= q1_user_input, q2_keyword= q2_user_input}'. It should be logged in a standard json format. |
|
Authentication Factors PRB2030597 |
Fall back to secondary identification when the primary resolves a non-sys_user | In cases when the identification questions are configured to a non-sys user, then it should ask fallback questions. This isn't happening in v2 and the call is ended since the userID isn't resolved. It should fallback to the secondary identification to get the userID. In cases where both the questions lead to a non-sys_user, then it should fail. | |
|
Authentication PRB1969882 |
Log in screen performance issues on iOS 26.2 RC and in Zurich instances | After upgrading to iOS 26.2, users are unable to log in to any instance using the Now Mobile app. The login page is extremely slow or unresponsive, and it can fail to load or accept credentials. The issue affects multiple users and device models. It's reproducible across different instances, and it also impacts the Agent app. |
Observe that the screen loads slowly and is non-responsive. |
|
Authentication PRB2033124 |
Case-sensitive comparison is applied during knowledge-based authentication (KBA) answer matching | Case sensitiveness of KBA answer matching is controlled by the system property 'glide.auth_factors. kba.case_insensitive _validation'. It is by default case insensitive in previous patches, but seems to have the incorrect default value in recent tracks. |
Expected behavior: The user-given input should be matched case insensitively. Actual behavior: Answers are matched case sensitively. |
|
Automated Test Framework (ATF) PRB2015508 |
Workspace load time performance fixes in Automated Test Framework (ATF) cache |
Observe the test takes up to 40 seconds to complete successfully. Sometimes intent timeout errors are seen. |
|
|
Automated Test Framework (ATF) PRB2022891 |
MVP - UI test script (Testing Library) test step in ATF for UI testing | This is a product update. | |
|
Cache PRB1947736 |
DBVideoProvider shouldn't use a synchronized LRU | This lock displays contended in most p90+ UI transactions. | |
|
Case and Knowledge Management for HR Service Delivery PRB2015420 |
RCAs for Now Assist Agents for requestor |
See an error and see the requested RCAs. |
|
|
Change Management PRB1994240 |
Translation issues in the Conflict Checker Progress modal window | Translation issues were observed after upgrading from Yokohama to Zurich. The 'conflict_detection' header appears to be missing the message completely when it previously read 'Conflict Detection'. The message 'The conflict check is complete' is translated into Finnish, even when the user's language is in English. This issue also occurs when the instance language is set to French, and the label is translated in English. |
Notice that the progress bar title displays as 'conflict_detection' and the value is shown rather than the label, 'The conflict check is complete'. The label is translated in Finnish even though the user's instance language is set to English. |
|
Change Management PRB2011052 |
Users are unable to add a change model state attribute for a major model from a scoped app | Application access settings don't allow writes to the sttrm_state_attribute table. The ACL is restricting to set the State field on sttrm_state_attribute record. |
Observe that the record isn't generated properly. |
|
Change Management PRB2011527 |
Applying a template can lead to URL size issues and invalid encoding | This appears to be potentially two issues. The template being added to the URL to apply it on the new form causes URL size and encoding issues. Observe that there's an error message in the developer console. A 500 error is returned from the instance: 'URLDecoder: Illegal hex characters in escape (%) pattern - Error at index 0 in: |",%\'''. | |
|
Change Management PRB2021436 |
Instances should not get license restriction ACLs | This issue was observed in Australia. Licensing controls are enforced when there are entries in subscription_entitlement. |
Log in to any Australia non-prod instance. Notice that the licensing controls are enforced when there are entries in subscription_entitlement, even if the instance is open. |
|
Change Management PRB2024681 |
Add a missing entry for an advanced/change admin experience for Auto Install Framework | Auto Install Framework was shipped to Australia users. The missing entry record related to advanced admin experience should be added so that the framework installs this experience as well for net-new users. | |
|
Code Signing PRB2014768 |
Increase the code signing validity window maximum from 60 minutes to 4 hours | In the 'Scan Signatures' module, the Data source field is incorrectly set to false for records that have valid, successfully created signatures. These signatures return true when validated via a background script. The issue occurs because the effective maximum of com.snc.kmf.signature .validity_window is 60 minutes, which prevents users from configuring longer validity windows, especially when the consecutive signature generation takes time. |
Observe that the signature state for the Data source field still reflects as false. |
|
Code Signing PRB2014831 |
Scheduled scripts incorrectly appear in 'Update Set Signature States' | Currently, users are required to hold the security_admin role to perform code signing operations on update sets. This creates several operational and security challenges. Instead, there should be a separate role that grants the ability to perform code signing operations on update sets and related artifacts within the Code Signing framework. It shouldn't grant access to security policies, ACLs, encryption contexts, or other security administration functions. |
Observe that there's no option to run signing jobs unless elevated to the 'security_admin' role. |
|
Code Signing PRB2014833 |
Enable digest creation for users with the code signing role | For users with the code_signing_user role, the 'Create Digest' functionality should be enabled for Flow Designer flows and actions. The current dependency on the security_admin role should be removed. |
Observe that the user can't generate digest for flows unless they have the 'security_admin' role. |
|
Column Level Encryption PRB1978716 |
Encryption isn't applied correctly for comma separated list values in a Glide record query for IN and NOT_IN clauses | ||
|
Condition Builder in Workspace PRB2001225 |
The messaging for deleting saved filters is misleading | The confirmation dialog says 'Active will no longer be available in your saved filters. This action can't be undone.' Instead, it should be more explicit that the filter may be deleted for everyone. |
Expected behavior: The confirmation explicitly says that when a filter is deleted—especially one that has been shared to a group or globally—it is deleted for everyone. Actual behavior: The confirmation dialog opens and shows: 'Active will no longer be available in your saved filters. This action can't be undone'. |
|
Condition Builder in Workspace PRB2011310 |
The SLA field is read-only in a related condition when creating a list in Workspace | ||
|
Configuration Management Database (CMDB) PRB1992684 |
CMDB Query Builder with the system language set as Japanese displays empty results | There are missing values in queries when using Japanese. The French language can lead to errors. |
Refer to the listed KB article for details. |
|
Customer Service Portal Base PRB1966219 |
Additional comments are duplicated in the Customer Service Management (CSM) Portal if the state is 'Awaiting Info' | Duplicate comments are occurring due to two identical network calls being made with the same journalEntry content. This duplication specifically happens when the spUtil.recordWatch method (part of the client-side script) triggers these service calls under slower network conditions (3G speed simulation). |
|
|
Database Persistence - Data Access PRB1919872 |
There's duplicate edges in the output of jsFunction_getEdgeList for custom created graphs and when includeEdgesForTablesOutsideGraph is true | ||
|
Database Persistence - Data Access PRB1930279 |
Users are able to create a cyclic relation through graph hierarchy |
Notice that it creates a cyclic relation in graphs test2-parent-test1 and test1-parent-test2. |
|
|
Database Persistence - Data Access PRB1946286 |
Workflow Data Fabric (WDF) queries fail when trying to execute on connection for trino_primary | When trying to get a specific column instead of the entire record, the error occurs in the response: ''FAILED TRYING TO EXECUTE ON CONNECTION trino_primary'. | |
|
Database Persistence - Data Access PRB1962536 |
The prefix is missing on some places for the Knowledge Graph UI |
|
|
|
Database Persistence - Data Access PRB1969193 |
SELECT isn't generated correctly for a script when a business rule is active with ORDER BY for Postgres | There's an error message: 'FAILED TRYING TO EXECUTE ON CONNECTION glide.1 (connpid=3758451): SELECT...' | |
|
Database Persistence - Data Access PRB1984070 |
Trend reports and dashboard show inaccurate data by week across the end of a year | On instances using a PostgreSQL database, an incorrect year reference (yearref) is returned for the non-ISO week functions sunday_week and monday_week. As a result, the column data displays trends for future dates where no actual record data exists. This issue affects reports and dashboards that group or summarize data by week across the end of a year. Reports may display an unexplained empty week in one year, a duplicated week in another, or records appearing in the incorrect annual bucket. |
Refer to the listed KB article for details. |
|
Database Persistence - Data Access PRB1986459 |
The 'Add OR Clause' with multiple filters is not working as expected | ||
|
Database Persistence - Data Access PRB1998050 |
Glide-side changes for label population in picker tables | ||
|
Database Persistence - Data Access PRB2027220 |
ColumnName.resurrect() re-shortens long names, corrupting external store column names on deserialization | ColumnName.resurrect() reconstructs a ColumnName from its serialized form using new ColumnName(name), which re-applies the preFujiShortColumnName() 30-character shortening algorithm. However, serialize() writes the already-resolved fName directly. For external-store columns (Snowflake, BigQuery, Trino) whose physical names exceed 30 characters, the name is corrupted on deserialization — the resurrected ColumnName points to a shortened name that doesn't exist in the external store. |
Observe the resurrected name is the 30 character shortened form, not the original 37 character name — a round-trip corruption. |
|
Database Persistence - Data Management PRB1999855 |
The 'One Time Archive Max Length Sync' job widens the max length of reference fields incorrectly |
Expected behavior: The one-time job should not widen reference fields when they are already reference types created with retainReference = true. In this scenario, the reference fields are already correctly defined, and recalculating their length based on display values is unnecessary and incorrect. Actual behavior: The one-time job widens the max length of reference fields, even though the fields are already of reference type and were created with retainReference = true. |
|
|
Database Persistence - Data Management PRB2004780 |
Use batch deletion for the 'Columnar' archive table during bulk archive restore | Deleting records one by one is not efficient for a 'Columnar' archive table because it requires scanning the same bucket multiple times. Batch deletion would only scan each bucket once. |
Expected behavior: Archive restore should be performed. Actual behavior: Archive restore isn't performed. |
|
Database Persistence - Data Management PRB2005218 |
Archive-Tier2-Bulk-Restore handle has silent exceptions when missing an archive log or bucket | If there's no archive log for the relevant cidx_record during restoration to the ar_* table, the process fails silently and also moves the cidx_* record to the cidx_*_backup table. If the sys_s3_bucket value is missing in the cidx_* record, which shouldn't occur, it loses the key value needed to restore the record. In this case, the chunk is processed, but the cidx_* record remains unchanged, making it appear as though the record was not processed. sys_s3_bucket value is missing for any cidx_* records which are still pending to be offloaded. The pending cudx_* records needs to be ignored. |
|
|
Database Persistence - Data Management PRB2015142 |
There's a slow query during archiving records to the 'columnar archive' table | The archived incident has a reference field whose referenced record has already been archived; it no longer exists in the live incident table, only in ar_incident. When copyFields tries to get the display value of that reference, live table lookup fails (record already moved to archive), GlideElementReference falls back to ArchiveResolver, and ArchiveResolver confirms it's in ar_incident via sys_archive_log, then queries ar_incident to fetch the display value. | |
|
Database Persistence - Data Management PRB2016927 |
Avoid reparenting the 'Columnar' archive table with a documentID reference after restoring a record | ||
|
Database Persistence - Data Management PRB2022327 |
Data Management Console fails to load live archive object storage data | Data Management (DM) Console fails to load live archive object storage data on instances using the new Live Archive / Tier 2 archive feature (com.glide.db.columnar.archive). This is because S3StorageInfoEligibilityChecker.isEligible() calls ArchiveEntitlementAPI. passedEntitlementCheck(), which only validates the legacy plugin com.snc.tier2_data_offload via isBaseTermsAndConditionsAccepted(). Users on the new columnar archive plugin fail eligibility and the S3StorageInfo daily job aborts. |
Expected behavior: The S3StorageInfo job should run for eligible users. Actual behavior: The S3StorageInfo job isn't running for eligible users. |
|
Database Persistence - Data Scale PRB1974343 |
A query hint isn't including the change number and is causing the hint to be ignored | ||
|
Database Persistence - Data Scale PRB2002323 |
When dry run mode is false, a successful external transfer causes TM to lock itself in a failed state and prevents any automatic failover during that window | ||
|
Database Persistence - Graph PRB1923336 |
The isTableExcluded API should exclude text search tables | ||
|
Database Persistence - Graph PRB1932536 |
An error should show 'Display Name' instead of the table name |
Observe an error: 'No properties found for node sys_user'. |
|
|
Database Persistence - Graph PRB1938573 |
A 'WHERE' clause appends all query node conditions with an 'AND' operator, even when there are 'OPTIONAL MATCH 'statements | When trying to a build cypher query for the following use case, 'Identify all CI's which are connected to Database catalog or Application', in the final built cypher query the 'WHERE' clause is using all 'AND' conditions to append all node filters to the query. When using 'OPTIONAL MATCH' statements, an 'OR' logic is expected. | |
|
Database Persistence - Graph PRB1944327 |
Global graph should be the default and all other graphs should be non-default when the instance is upgraded from Yokohama to Zurich | Default graphs and global graphs are all set to non-default. |
Expected behavior: Global graph should have default = true and the other two graphs that were created in step one should have default = false. Actual behavior: Both of the created default graphs and the global graph are default = false. |
|
Database Persistence - Graph PRB1967193 |
CMDB Query Builder doesn't work when multiple OR conditions are used on location attribute | When multiple OR conditions are used on the location filter, the CMDB query builder doesn't return any results. |
Scenario 1:
Observe that once a second condition is added, the query builder fails. Scenario 2:
Observe that results are now returned. |
|
Database Persistence - Graph PRB1975732 |
There's a repeated query execution in GraphUtils #getGraphByQualifiedName for a metadata child table [sys_meta_graph] for every iteration/execution | ||
|
Database Persistence - Graph PRB1988516 |
Weeks, milliseconds, and microseconds aren't supported in a DURATION map | There's an error: 'com.glide.db. DBGraphApiException: Error executing cypher: FAILED TRYING TO EXECUTE ON CONNECTION...Syntax Error or Access Rule Violation detected by database (ERROR: function duration_between(date, date) does not exist Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 294)'. | |
|
Database Persistence - Graph PRB1988520 |
TimeKeyExpression isn't supported as a DURATION function parameter in DBSqlParser | There's an error: 'Error: com.glide.db. DBGraphApiException: Error executing cypher: FAILED TRYING TO EXECUTE ON CONNECTION...Syntax Error or Access Rule Violation detected by database (ERROR: function duration_between(timestamp with time zone, date) does not exist Hint: No function matches the given name and argument types. You might need to add explicit type casts. Position: 307)'. | |
|
Database Persistence - Graph PRB1990632 |
Node/edge types should allow special characters for GraphMetadataAPI | Predefined filters fail in the Graph API version of the CMDB query builder. After a platform upgrade, CMDB query builder throws the 'Problem Running Query' error. | |
|
Database Persistence - Graph PRB1995712 |
Weeks, milliseconds, and microseconds aren't supported in the 'Duration' map | ||
|
Database Persistence - Graph PRB1996879 |
Guardrail for maximum number of edges returned from getForTables | The number of nodes returned from getForTables is capped to 1000, but there's no such limitation for the number of edges. When inbound edges are specified and the number of nodes is at maximum, the number of edges can be quite large. |
Run getForTables for sys_user with inbound edge flag = true. |
|
Database Persistence - Graph PRB1997409 |
L2 query displays non-empty edge values |
Expected behavior: Observe with the data, there should be two L1 relationships and three L2 relationships with edge shown as '(empty)'. Actual behavior: The three L2 relationships have unexpected edge values. |
|
|
Database Persistence - Graph PRB2007566 |
com.glide.db. DBGraphApiException has an error executing cypher | There's an error: 'This user (admin) is not allowed access to table: sys_user_has_role'. | |
|
Database Persistence - Graph PRB2008809 |
Rename the ScopedGraphQueryBuilder .createNode method | To avoid potential confusion with createNode as a write operation, rename the 'createNode()' method to 'node()'. | |
|
Database Persistence - Graph PRB2020140 |
Union queries aren't supported | ||
|
Database Persistence - Graph PRB2021889 |
GlideRecord. setCategory() is used in a way that prevents routing to read-replica databases | The query is categorized as 'graphqueryexecutor' instead of 'cmdb_queries', and therefore doesn't get routed to the read replica because the category isn't a second database category. |
Expected behavior: The query is categorized as 'cmdb_queries' and is routed to the read replica. Actual behavior: The query is categorized as 'graphqueryexecutor', and since that category isn't a secondary database category, is not routed to the read replica. |
|
Database Persistence - WDF PRB1975615 |
GlideAggregate. getDisplayValue issues a separate query per each returned record for GlideAggregate | ||
|
Database Views PRB2004420 |
Data fabric (DF) tables in DBViews uses an old connection even after doing a change connection/remap flow on DF tables |
Observe that the underlying DF tables in DBView still looks for an old connection. |
|
|
Data Management Console PRB1974031 |
A repeated query with the hash -423529530 comes up when running stats gatherer | ||
|
Data Management Console PRB1976295 |
The confirmation checkbox is missing on the 'Summary' page when scheduling a rule | ||
|
Data Management Console PRB1979259 |
The data on Data Management Console (DMC) is inconsistent when the 'Stats gatherer' job runs | The data on DMC is inconsistent when the 'Stats gatherer' job runs because the latest available data is chosen, even when the data isn't completely generated. | |
|
Data Management Console PRB1980674 |
There's a potential of orphan sys_peripheral _table_stats records for a duration of 1 year with the existing Data Management Console (DMC) table's table cleaners | Revisiting the table cleaners for sys_peripheral _table_stats and sys_physical _table_stats in order to accommodate a new data model. Cascade delete should be turned on so that orphan records are cleaned up regularly. |
Expected behavior: Cascade delete should be enabled and in the sys_dictionary. The reference column's reference_cascade_rule should be 'delete'. Actual behavior: Cascade delete isn't enabled. |
|
Data Privacy (Classic) PRB2001965 |
'Run once' Data Privacy jobs take a long time to complete on large tables | As part of Zurich, Data Privacy jobs were enhanced to support incremental and recurring anonymization. As part of this, 'sys_updated_on < jobStartTime' was added to the query condition while creating segments and querying a batch of records for processing. Generally, sys_updated_on column isn't indexed. As a result, the jobs take lot of time to create segments, which require querying boundary records involving filtering on sys_updated_on and ordering by sys_id. While the sys_updated_on filter condition is necessary to support incremental, this dependency can be removed on 'Run once' jobs, where all records in a table are expected to be anonymized. |
Expected behavior: Segment creations (dp_work_item) should happen within few a minutes. Actual behavior: It takes hours to create segments (dp_work_item). |
|
Data Privacy (Classic) PRB2002556 |
Data Privacy Clone (federated) jobs can't handle pause/resume scenarios | During a clone job execution, if the node on which the clone job is executing is restarted, scheduler reschedules the job on a different node. When the job is restarted on a different node, it fails due to inability to deserialize and restore the state items (that dictate where the job should resume from). |
Expected behavior: The job should be completed. Actual behavior: The job errored out with 'Error creating job handler for type null from serialized state : [Interfaces can't be instantiated! Register an InstanceCreator or a TypeAdapter for this type. Interface name: com.glide.data_privacy.jobs.stateitem.StateItem]'. |
|
Data Privacy (Classic) PRB2006453 |
The Data Privacy job's policy child table filtering isn't working as expected if the parent table is selected as a child table filter | If a task table is selected as child table for any of its dictionary selected tasks as the child table, then it's expected to anonymize records that belong to sys_class_name = task, and the rest of the records, the incident or problem, are expected not to be anonymized. It's anonymizing the entire task table. |
After the job completion, notice that the entire task table is anonymized, but it's expected to only anonymize the task records, not any others. |
|
Data Privacy (Classic) PRB2017470 |
Job conditions aren't applied by additional jobs during parallel execution | This is caused because of dp_additional_job not applying the condition setup for the job. Since, the conditions in dp_job_condition is tied to parent job, querying from additional job won't find them unless it uses the parent job ID to query. |
Expected behavior: Only records matching the setup condition should be anonymized. Actual behavior: Record not matching the condition are also anonymized. |
|
Data Privacy (Classic) PRB2017592 |
A minimum segment size of 100K characters restricts parallelization and lacks work item table cleanup | The current minimum segment size is hardcoded at 100K characters, which artificially caps the number of segments that can be generated for a given dataset. As a result, the number of worker threads that can be utilized for parallel processing is also restricted — even when additional infrastructure capacity (CPU, memory, available workers) is available to be consumed. If the minimum segment size is reduced to improve parallelization, the number of work items inserted into dp_workitem grows significantly, accelerating the rate at which this table accumulates rows. Without a corresponding cleanup mechanism, this will lead to unbounded table growth, increased storage consumption, and potential degradation of query performance over time. |
Expected behavior: There should be at least 2 work items. Actual behavior: There's 1 work item. |
|
Data Privacy (Classic) PRB2017660 |
Users aren't able to switch to a GPU-based Named Entity Recognition (NER) service from CPU-based services for privacy jobs | ||
|
Data Product Backend Services PRB2017091 |
Users are unable to remove a source table from Data Interface | syncDataInterfaceM2MTable DAO method wasn't removing M2M rows for sources absent from the new list. Delete path lacked compensating-action registration, leaving stale rows on partial failure. |
Observe that the user isn't able to add/remove a source from the interface. |
|
Data Product Backend Services PRB2017092 |
Users are unable to add a new source to Data Interface | The syncDataInterfaceM2MTable DAO method isn't inserting rows for sources present in the new list but that are absent from the database. Insert path lacked compensating-action registration, leaving the interface with no implementors on partial failure. |
Observe that the user isn't able to add a new source to the interface. |
|
Data Product Backend Services PRB2017094 |
Users are unable to roll back if the creation or editing of a data interface fails in the middle | DataProductDAO edit methods had no rollback mechanism. A failure mid-transaction left the interface partially mutated with no way to restore prior state. |
Observe that the data interface creation failed in the process, a few artifacts were created, and a few are missing. |
|
Data Product Backend Services PRB2017095 |
Once an interface is created, the metadata JSON for existing interface tables is missing | DataProductDAO didn't call TableManager.invalidateTable for existing source tables after interface creation. Users received stale cached metadata JSON rather than the newly registered interface state. |
Observe that the metadata is missing, causing the UI to break. |
|
Data Snapshots PRB1999238 |
There's a node outage due to an out-of-memory error as a result of a memory bloat in ScriptableCDCDataCollector .jsFunction_mineAllChanges() | During the investigation, it was noticed via heapdumps that the com.snc.db.cdc. implementation. ReplicationTableReader object held an array list of size 500. Each entry in this array list held up to a max of 800 Glide record objects. The size of each of these 500 entries was ~21 MB. The Glide record objects were from the cmdb_ci_vm_instance table. These were particularly heavy in terms of row size (reaching ~400 KB). The existing sizing must be revisited to take into account this outlier. In particular, in addition to a limit on number of rows to be polled from cdc_queue_par, it should also include a limit to cap the memory size. |
Notice the memory bloat in the worker thread running for the 'All changes' job. |
|
Data Snapshots PRB2018876 |
Turn on automatic installation of the plugin com.snc.pa.mlb on eligible instances | This is a product update. | |
|
Developer Sandboxes PRB1995018 |
NowMQ messages can be claimed by an unexpected recipient | If the user sets the App Operation Queue Health Monitor job to disabled, it should prevent the sandbox from claiming any application operation queue messages in sys_nowmq_message. On an instance without sandboxes, any messages that were left unclaimed or any newly added messages should still be claimable when the job is re-enabled. |
Observe that the corresponding message from step 3 is unexpectedly gone. It should still be present but unclaimed as a result of step 2. |
|
Developer Sandboxes PRB2011753 |
Sys_flow_trigger_plan_chunk is currently shared and causing updated flows to error out | If you update the base flow, the sandbox flow errors out with 'Compiled flow not found for snapshotId'. |
Observe that, under 'Today's execution', the flow starts erroring out with 'Compiled flow not found for snapshotId'. |
|
Developer Sandboxes PRB2015080 |
The scheduled flow inherited from the main instance does not run automatically on the sandbox instance | The flow runs in main instance at the scheduled interval, but the flow doesn't run in the sandbox instance even though it exists. |
Notice that the flow is not running. |
|
Developer Sandboxes PRB2017438 |
DSB update sets aren't exported before clone | Because sandboxes are retired, update sets from a sandbox should be saved as remote update sets on the base instance on upgrade. However, due to this problem, they may not be saved correctly. |
Expected behavior: There is a way to recover the work. Actual behavior. The work is gone. Logs show jsFunction_exportUpdateSets is called. |
|
Developer Sandboxes PRB2018545 |
BA conversations are shared between sandboxes/base instance | The base instance conversation contains messages from the sandbox, and vice versa. |
Expected behavior: The conversation doesn't contain what was typed in the sandbox. Actual behavior: The conversation contains messages from the sandbox. |
|
DirectSQL PRB2000506 |
A correlated sub query loses outer table references | The correlated condition is translated incorrectly, resulting in incorrect results. |
Run the following query: SELECT number, (SELECT COUNT(*) FROM incident AS x WHERE x.priority < incident.priority) AS lower_pri_count FROM incident ORDER BY number. Expected behavior: The query returns each incident with a count of how many other incidents have a strictly lower priority value. Incidents with priority > 1 should have a non-zero count. Actual behavior: Every row returns lower_pri_count = 0, because the correlated condition is translated as x.priority < x.priority (always false). |
|
DirectSQL PRB2014682 |
DirectSQL extract epoch support is broken | Users can't extract epoch and must use unix_timestamp instead. Also, the cypher-related code may be breaking the postgres implementation. | |
|
DirectSQL PRB2016811 |
Disallow queries that use an inaccessible offrow array in non-select items | For example, select * from sys_user where roles is not null. If users don't have access to sys_userroles for the roles offrow array, then this query should error out indicating that is the case. Currently, null is substituted into the 'where' clause instead, which is confusing. | |
|
DirectSQL PRB2019852 |
SELECT * must exclude columns that don't exist in the database | Select * from a table that has a function field, like cmdb_data_management_policy, won't work because it's trying to find the function fields on the database. A filter should be added to exclude these fields. | |
|
Discovery PRB1986211 |
Discovery.complete and discovery.canceled are triggered incorrectly | Discovery may trigger both discovery.complete and discovery.canceled events for the same status, and it may trigger discovery.canceled twice. |
Observe that discovery.canceled fires twice for the same status record. The StartDiscovery error log for 'Discovery canceled on previously started schedule ... due to mid not available' appears twice. Instead, there should be a single discovery.canceled event and a single error log entry per cancelled run. |
|
Discovery PRB2014076 |
Update Discovery references to the new error framework from a scoped app to zboot | This is a product update. | |
|
Discovery PRB2016944 |
Classifier probes aren't firing if the 'First checked' probe has already been fired | Discovery should fire further probes, but instead completes prematurely. | |
|
Document Intelligence Unified Backend PRB2018937 |
Local naively checks for empty text rather than 'blank' when classifying PDF pages for DocReader | The PDF page is classified as 'digital' instead of 'scanned' because it checks for empty text instead of a blank PDF page. |
Call DocReader Local with a scanned PDF containing blank text, for example, '"\n\n\n"'. Notice that the page is classified as 'digital' rather than 'scanned'. |
|
Document Intelligence Unified Backend PRB2029867 |
Users can configure more than 50 fields per use case, which does not match the product and pricing based limitations | ||
|
Dynamic Scheduling PRB2021720 |
Capacity console isn't loading after changing the default date format |
Expected behavior: Events display for the territory. Actual behavior: No events display as demand metrics data aren't created. |
|
|
Dynamic Scheduling PRB2025038 |
Dynamic Scheduling isn't considering recurrence if more then 1 record for same resource is present in the 'Territory resource demand' table | For example, if 2 records for the same date range with da ifferent recurrence are created for same territory and demand channel, such as: May 1st to May 30th - Monday Recurrence and May 1st to May 30th - Tuesday Recurrence, then Dynamic scheduling isn't considering the Tuesday recurrence. | |
|
Edge Encryption PRB1945424 |
There's high memory utilization on proxy servers after the Yokohama upgrade | After upgrading and running Yokohama, the memory consumption is above the limit set in wrapper.conf. The user set the memory limit for 10G in the wrapper.conf, but the edge proxy doesn't respect this setting in the build. The memory goes to the physical limit and causes the proxy server to restart. | |
|
Email Notifications PRB1970107 |
There's an issue with adding an email template in Zurich |
|
|
|
Email Notifications PRB2003711 |
There's inconsistent behavior on bringing the /r response template in the email body |
See that the response template isn't displaying. |
|
|
Email Notifications PRB2006670 |
Push Notifications aren't sending the badge count | This issue occurs on mobile instances. |
Observe that the badge count isn't sent in the push payload. |
|
Email Notifications PRB2022602 |
Client script include should be created to make client scripts modular and reusable | In Zurich, the wiring's not implemented for mini composer in CSM when activity stream compose isn't present. |
Expected behavior: The pop-up is displayed based on the configuration. Actual behavior: The pop-up isn't displayed when the user selects the Send button. |
|
Employee Relations Case Management PRB2009979 |
Moving an RCA from the Employee Relations scope to the Evidence scope | ||
|
Error Framework PRB2014079 |
Migrate the error framework from a scoped app to Glide universe/zboot | This is a product update. | |
|
Error Framework PRB2014080 |
Log analysis and error refinement | This is a product update. | |
|
Error Framework PRB2014081 |
Error framework backlog for UI Builder unit tests and QoL | This is a product update. | |
|
Event Management PRB1980951 |
When text-based grouping is turned on, tag-based grouping doesn't work consistently | When text-based grouping is turned on, the related tag-based alerts aren't always grouped. This behavior isn't consistently reproducible and occurs at random. If text-based grouping is turned off, the related alerts are grouped by tags. |
Refer to the listed KB article for details. |
|
Event Management PRB1999707 |
An app node crash occurs due to OutOfMemory (OOM), and GroupingDebugLogger accumulaties log messages even if logging is disabled | After stimulating alerts for Metric rule/Event rule and checking the tables for node restarts and active transactions, the queue in the sys_trigger table is huge. |
Notice that there is a huge queue found in the sys_trigger table. |
|
Experimentation Platform PRB2027972 |
Feature flagging under the feature preview program | This is a product update. | |
|
Explicit Roles PRB2011506 |
The NullPointerException in ExplicitRoleCollisions .handleSysUserGrmember invalidates ATF rollback context during CreateUserStepRunner execution | During the scheduled nightly ATF test execution, a null pointer exception occurs in the explicit roles collision check logic, which propagates up and invalidates the ATF rollback context. This prevents automatic rollback of test-created records (e.g. Incidents, Users, Business Services), leaving orphaned data in the environment. |
Expected behavior: There is no null pointer exception in the node log. Actual behavior: There is the following null pointer exception in the node log: 'Error: java.lang.NullPointerException: Cannot invoke 'com.glide.explicit_roles. MutuallyExclusive RoleCheckResult $MutualExclusion ResultType .ordinal()' because the return value of 'com.glide.explicit_roles. MutuallyExclusive RoleCheckResult .getResultType()' is null'. |
|
Flow Engine PRB1992819 |
Impact handling of Scripting Governance disable switch | A disable switch for the Scripting Governance feature is being backported. Any ACL or Java code dependent on the scripting role/group will break if a user flips the disable switch. |
|
|
Flow Engine PRB2014479 |
Add the roles 'taas writer' and 'taas reader' with API access only, and not with table ownership | Adding the role trigger_designer directly to policy_manager was evaluated and ruled out, as the 'policy manager' role should not have access to trigger the 'designer' role. | |
|
Form Templates PRB1833484 |
A workspace template with a currency-type field fails to apply | A workspace template fails to apply if it contains a currency-type field. However, a template created from the platform applies in workspace as expected, even with a currency-type field. | |
|
Generative AI Controller PRB2026284 |
Agents aren't working in Zurich nightly with the latest snapshot |
See that the agent is stuck in starting and no context is passed to it. |
|
|
GlideRecord PRB1922298 |
Assessment Metrics (asmt_metric) in a question bank disappear after they're used in a published survey | On an instance running on RaptorDB (postresql), the assessment metric in the question bank can disappear. The issue can't be reproduced on MariaDB. | |
|
GlideRecord PRB1958518 |
A Null Pointer Exception is thrown if a table has a GlideElement WikiText type field and queries at startup before extension points are loaded | Adding a GlideElement Wikitext type field to the user table can cause an outage. The page is blank and errors are seen. On a local instance, the instance throws servlet exceptions and doesn't start. |
Refer to the listed KB article for details. |
|
Global Ranking PRB2005044 |
Remove 'defect' and 'enhancement' as options from the 'Demand' type | Removing 'defect' and 'enhancement' as drop down options in the 'Demand' type from the SPM_agile_commons plugin repository that are c entries to appear in 'Demand'. Removing these files from the repository prevent these demands from being created. | |
|
Hardware Asset Management PRB2023375 |
Stockrooms missing a distribution channel yield empty records in the 'list' view | The following exception is thrown when navigating to the 'list' view: 'com.snc.kittyscript.SecurityCallbackException: Scope objects cannot be passed as function arguments'. |
See that no records are visible. |
|
HR Service Delivery PRB2016516 |
RCA is generated for 'Populate Manager Reportee Count Using Eligible Users' and 'EmployeeHubOrg ChartReporteeUtilSNC' | The following two RCA's are generated for the new scripts, causing test failures: sys_script_include_ a302f8807873f250 f877079523d275e1 and sysauto_script_ 33a5e72453f7 b210f2ebffc 230e5e69d. | |
|
Instance Clone (Family) PRB2023467 |
Incorrect values are shown on the clone summary page | ||
|
Instance Scan PRB1992382 |
Instance scan jobs get stuck in a sleep loop for days, which causes the subsequent scans to fail | Instance scan findings are written to the database asynchronously and are tracked using a global counter. If any write fails, the counter doesn't decrement properly; it goes up but never comes back down. This causes all future scans to hang indefinitely, waiting for a counter that will never reach zero. There's no timeout or logging to flag this, so scans can get stuck silently. |
Refer to the listed KB article for details. |
|
Instance Scan PRB2017072 |
Instance scans detecting custom records instead of other records are modified from the baseline | Instance scan checks like 'Differs from baseline' are detecting custom records created by users. As per the script used, only the records which are modified should be detected. | |
|
Instance Scan PRB2022691 |
Instance Scan Linter Check fails on sys_module with an error: 'Rhino error: missing ; before statement' |
|
|
|
Integration Hub PRB1870601 |
A PowerShell step error message is no longer populated | On flow engine V1, the user ran a flow execution and can observe 'Error Code' and 'Error Message' are outputed in the 'Output Data' section when the PowerShell script returns an error. However, if users switch to flow engine V2, the same error code and error message can not be rendered into the 'Output Data' section. | |
|
Interactive Filters PRB2007031 |
Applying the filter in the Dashboard shows 'Some applied options are currently unavailable' when the filter options have a comma ',' in the value | While trying to apply an indicator filter with the 'Filter' option in the breakdown, the messages 'Some applied options are currently unavailable' and 'Unavailable option' appear. |
Notice the message, 'Some applied options are currently unavailable.' |
|
Internationalization Features PRB1892286 |
A non-admin user can't change a dashboard name by specific steps when the system language is set to Japanese | The dashboard name should be updated correctly and reflected in both the primary record and its translated fields, as it is in the Washington and Xanadu versions. In the Yokohama version, the update to the dashboard name fails silently when the Japanese language is enabled and the sys_translated record exists. |
Refer to the listed KB article for details. |
|
Issue Auto Resolution for Virtual Agent PRB1657388 |
Issue Auto Resolution (IAR) for HR isn't able to execute for users who remove HR roles from the 'admin' role due to internal data governance policies | Affects users using IT and HR products on the same instance. Due to the data internal visibility/governance policies, users have removed a number of HR roles (i.e. 'sn_hr_core.admin' role) from the admin role, resulting in users in the IT business units not having access to the HR side of the platform. Removing the roles from the admin profile prevents the 'system' user from executing the AutoResolution scripts includes. The 'system' user no longer has access to the HR tables of the instance, hence it can't extract the necessary information for auto resolution ML Configuration Language solution, auto resolution context, or write to HR records. |
Refer to the listed KB article for details. |
|
Key Management Framework (KMF) PRB1964424 |
WebServices Mutual Auth connections fail if the instances are in FIPS mode | If an instance is using FIPS mode, REST Web Services connections fail if the authentication type is 'Mutual Auth'. The following error is thrown: org.bouncycastle.tls.TlsFatalAlert: unsupported_extension(110). |
See that it fails with an error: 'org.bouncycastle.tls.TlsFatalAlert: unsupported_extension(110)'. |
|
Knowledge Blocks PRB2000541 |
There are formatting issues in the KB article view compared to the 'Details' tab view | There are differences in the formatting of the KB article between the 'Details' tab and the 'View article' view. |
Notice that the formatting in the KB article 'Details' tab and the 'View article' view are different. |
|
Knowledge Graph (Family) PRB2021133 |
Knowledge Graph (KG) description deactivator triggers long-running queries, causing HLL spikes | Post Version Upgrade Job : KG Description Deactivator triggers Long running queries and causes HLL spike | |
|
Knowledge Management PRB1976775 |
A KB's article title is empty under the 'Event property values' column in the 'Article Title' report |
Observe the exported report contains an empty field under the first column labeled 'Event property values'. |
|
|
Knowledge Management PRB2009818 |
The Recall button isn't displayed for the author of the article in Service Operations Workspace | The Recall button in a workspace is nested behind the Edit button, which is intentionally hidden from the author while the article is in review. However, authors are blocked from editing content that is currently under review. The Recall button only appears after selecting Edit, but since the Edit button isn't visible to the author in this state, the Recall button is unreachable. | |
|
Knowledge Management PRB2010029 |
Knowledge blocks aren't honoring Knowledge Center (KC) redirection properties |
Expected behavior: Knowledge blocks should honor KC redirection properties. Actual behavior: Creating or editing a from UI16 doesn't redirect to KC. |
|
|
Knowledge Management PRB2010576 |
kb_translate page padding and alignment must be revisited | There's no padding at all and the page content and buttons are near to the borders and not what users see in other workspaces. The kb_translate page should be properly padded as in other workspaces for a consistent experience. | |
|
Knowledge Management PRB2014935 |
KB Portal's image dimensions don't match with the Native UI | The image dimensions displayed in the KB Portal don't match with the dimensions configured in the article body within the Native UI, although they should. | |
|
Knowledge Management PRB2027236 |
True-up for KC and NAKM, ECE, and KC in UI Builder | This is a product update. | |
|
List Administration PRB1970036 |
List type data visualization doesn't show new lines (multi-lines) | The data visualization doesn't add new lines (multi-lines) in Zurich, but it does in Yokohama. |
Observe that the data visualization doesn't add new lines (multi-lines). |
|
List Administration PRB1989840 |
There's unintended creation of temporary list copies when refreshing a default list via address bar | When a user refreshes a default list by selecting the browser address bar and pressing Enter, the system creates a new temporary copy of the list and stores it under 'My Lists' > 'Opened by link'. When the page reloads, that view is opened. This happens without any explicit user action or intent to create or save a new list, and the newly created list is not shared with anyone by default. This behavior creates large volumes of unnecessary list views, leads to user confusion, and pollutes My Lists governance and storage with artifacts. |
Expected Behavior: Refreshing a default list via the browser address bar doesn't create a list artifact. Actual Behavior: A new temporary copy of the default list is automatically created. The list appears in , even though the user never requested a copy. The list is not shared with anyone by default. |
|
List Administration PRB1999574 |
The user has no information about who shared a list with them |
Expected behavior: There's some info or indication on who shared the list. Actual behavior: The Fred Luddy user has no information regarding who shared this list. |
|
|
List Administration PRB1999583 |
The user can't re-order the lists 'Shared with me' lists or 'Opened by Link' to keep the important lists at the top and move less important lists to the bottom | Lists can't be re-ordered in the 'Shared with me' section in the 'My List' tab. |
Expected behavior: There should be a re-ordering capability to arrange the shared lists when there are many lists in 'Shared with me' section. This should also apply to the 'Opened by Link' list. Actual behavior: The user Fred Luddy can't reorder the lists in the 'Shared with me' section. |
|
List Administration PRB2003558 |
Users are unable to select 'presentational' variables when using the list selector to build out list configurations |
Observe that it can't be found. Users would like to be able to choose presentational variables as well, even if they don't contain any values. |
|
|
List Administration PRB2009991 |
'Workflow'-type fields are displaying as 'Pending - has not started' for all values | This requires a single-line change that adds a defensive .clone() call to deep-copy the choice list before WorkflowIcons.process() mutates it. This prevents the shared cache from being poisoned by in-place label overwrites. |
Expected behavior: The display value should be as per available choices. Actual behavior: It displays 'Pending - has not started' even after changing value. 'Pending - has not started' is not even available as a choice option for a field. |
|
List Administration PRB2012758 |
List fails to load due to a DataFetchingException from NowAssistSkillConfig | The list page in Service Operations Workspace doesn't load; it looks like the page is processing. NAA code is called and throws an exception, which results in list load error. | |
|
List Administration PRB2014997 |
In Service Operations Workspace, live updates of Alert Express List displays en 'Invalid Row Data, Duplicate Row Keys' error on auto-refresh | handleLiveListChange() (~line 448) dispatches LIVE_LIST_FETCH_ROW_LAYOUT_REQUESTED for every AMB event with no in-flight deduplication. When multiple AMB events arrive for the same sys_id before the first GraphQL fetch completes, findRowByFullKey() (parentChildBehaviorUtils.js:95) returns null for each event and each event triggers its own fetch. Each fetch response then adds the row via addEnteredRowToRowDefinitions() (~line 676), resulting in duplicate row keys. hasDuplicateRowKeys() (rowBehavior.js) detects duplicates and triggers the error overlay. | |
|
List Administration PRB2023617 |
Grouping and summarization for telemetry for Multi-Record Actions (MRA) - List AI | This is a product update. | |
|
List Administration PRB2023634 |
Implement add/remove an AI indicator for the rows created/modified by an AI agent and clear an AI indicator when inline edits are made | This is a product update. | |
|
Live Archive PRB1976776 |
There's an error when restoring to long table name aliased tables | This happens with both chunking and hex based approaches. It happens in both related records and payload parsing. Also, the state in sys_archive_restore_request is set to 'complete' instead of 'Error' in this case. |
Expected behavior: All records matching the restore request conditions should be restored. Actual behavior: The chunks error out and an error is seen in the logs. |
|
Live Archive PRB1980314 |
After archiving, bulk restoring, and killing a node, checkpoint rows aren't populated in sys_archive_restore_checkpoint | ||
|
Live Archive PRB1982265 |
There's an error in the logs after running the DMscheduler daily trigger | There's an error: 'ERROR *** #808133feature= AttachmentMigration AttachmentMigrationService: Error migrating attachment sys_id: 73dec36dcc623210 f877c28b1770b27b from: ROWSTORE to: COLUMNSTORE'. |
Once job resumes, notice there's a chunk stuck in a 'processing' state and an error in the logs after running DMscheduler daily trigger. |
|
Live Archive PRB2007788 |
Data Management Console isn't reporting Tier 2 data correctly | Recently, data was offloaded to the new 'Columnar' solution for multiple tables to S3 storage. The Data Management Console displays a negative value, which is incorrect, and also doesn't match with the PG stats. |
Expected behavior: 'Tier 2 Storage Used' should match the actual amount of data offloaded. Actual behavior: 'Tier 2 Storage Used' is negative. |
|
Live Archive PRB2010081 |
Tier 2 archive plugins (com.glide.columnar.archive & com.glide.data_management. columnar_attachment) and the legacy archive plugin (com.glide.auxdb) need to be renamed | The plugin ID should remain the same. |
Expected behavior: Marketing has changed the plugin names:
Actual behavior: The incorrect plugin names are displayed. |
|
Live Archive PRB2017269 |
Archive Destroy operations against archive tables that have attachments aren't performed | The 'Destroy' job deletes attachment data from sys_attachment_ doc_columnar one attachment at a time, with each attachment requiring two SQL operations. Each attachment pair takes ~2.7 seconds. The ColumnarDeleteService is cleaning up related/peripheral records (attachments, journals) but the actual archive table row deletion either happens in a separate phase, was skipped, or happened in a subsequent chunk. |
Expected behavior: The archive destroy operation should be performed. Actual behavior: Archive destroy is taking 1hr 40mins to delete 2,000 records. |
|
Live Archive PRB2022367 |
In AttachmentMigrationService, copy-then-delete causes silent data loss through cascade delete on sys_attachment_attribute, dp_attachment_protection_history, and sys_attachment_migration_status | AttachmentMigrationService migrates attachments between the storage backends 'ROWSTORE' and 'COLUMNSTORE' by creating a new sys_attachment row with a new sys_id, and then deleting the old one. Deleting the old sys_attachment triggers reference_cascade_rule='delete' on every child table that references it, which silently destroys records that reference the old sys_id, even though a valid replacement exists. The cascade engine has no knowledge of the new sys_id, so the new sys_attachment ends up with no associated child rows. The following child tables suffer silent data loss on every migrated attachment: sys_attachment_attribute (per-attachment metadata), sys_attachment_migration_status (migration tracking history), and dp_attachment_protection_history (data-privacy / compliance audit trail). |
Expected behavior: All three child tables still contain rows for the migrated attachment, either against the same sys_id, or under copy-then-delete which is re-pointed to the new sys_id. Actual behavior: All three child tables contain zero rows for the original sys_id 'X'. The new sys_attachment record, the new sys_id 'Y', exists with the migrated chunk data, but contains no rows in any of these three child tables. The data is silently lost and no error is logged. This occurs in any instance running on a build that includes AttachmentMigrationService for track, datamanagement, and downstream. |
|
Major Incident Management PRB2030990 |
The Major Incident Management (MIM) plugin is installed automatically after upgrading in Australia | The MIM family plugin is added as a dependency on the Service Operations Workspace MIM application. The dependency of the MIM plugin should be removed from the sn_sow_mim plugin. |
Upgrade an instance to Australia. Expected behavior: The MIM family plugin shouldn't be installed on the upgrade. Actual behavior: The MIM family plugin is installed on upgrading to Australia. |
|
MetricBase PRB2008126 |
The rollup scheduling script has a race condition that allows duplicate event queuing in MetricRaptor | When no classic shards are configured and the mb_shard_mapping table is either empty or has no rows with stores_classic_data = true, there is excessive logging for ClothoClientManager and ClothoRrdWriter. The error '*** ERROR *** No endpoints available' occurs for ClothoClientManager, and '*** WARNING *** No Classic Clotho Shard Configured' occurs for ClothoRrdWriter. |
Observe that a duplicate mb_rollup event is queued because the state = 'ready' check misses the processing event. |
|
MID Server PRB1998489 |
Root Cause Analysis (RCA)/Cross Scope Access changes are casuing the 'MAW' list and record declarative actions to be blocked from execution | Changes made in RCA/Cross Scope Access on the platform side have impacted the declarative list and record actions for MAW from working. When attempting to execute any of these actions which call the MIDManage API, users see an error that the RCA record isn't present for this script execution, despite the Cross Scope Access record being defined. |
Notice that this action is blocked and the corresponding error banner displayed to the user. |
|
MID Server PRB2024310 |
MID Admin Workspace isn't auto-installed with ITOM Infra Services Workspace app | In an Australia instance, the ITOM Infra Services Workspace is installed but the MID Admin Workspace is not, though it should be. | |
|
Mobile Platform PRB1984253 |
When in offline mode for external uses, cost and currency display inaccurately | ||
|
Mobile Platform PRB1999865 |
Support onSubmit UI Rule | Configure and execute UI Rules at the time when the input form screen is submitted both online and offline. | |
|
Multi-Instance Framework PRB2019094 |
Async messages from a JavaScript layer aren't signed so they aren't validated on a receipt | MIF async messages sent from the script layer aren't signed because the two argument 'MessageSender.createTrusted (scopeName, messageProducer)' factory method uses a no-op identity augmentor instead of 'EnvelopeTrustAugmenter'. However, the Hermes receiver still expects and validates ISK signatures on all incoming messages, causing a failure when attempting to decode the null Base64 signature field. | |
|
Multimodal Service (Family Channel) PRB2022350 |
Vision Agent MMS Glide changes | This is a product update | |
|
Multimodal Service (Family Channel) PRB2022351 |
Implement improvements to the MMService plugin | This is a product update. | |
|
Multimodal Service (Family Channel) PRB2029152 |
Update vision agent AIA records to consume new multimodal service-backed video Q&A subflows | ||
|
Multimodal Service (Family Channel) PRB2029156 |
Move MMS to GA | The MMS plugin name displays 'MAINT ONLY', and should be updated. | |
|
Next Experience Unified Navigation PRB2022500 |
If a work item is assigned to the same agent repeatedly, the desktop notification stops appearing entirely | A new desktop notification should appear on every work item assignment. | |
|
Next Experience Unified Navigation PRB2034454 |
Record Summarization isn't using the page context | In Now Assist Portal (NAP), when standing on an incident record and if the user type is 'summarize this record', NAP should pick up the incident from the page context. |
Expected behavior: NAP should summarize the incident the user is seeing. Actual behavior: NAP asks the user to enter the incident record number. |
|
Now Assist in AI Search PRB1920760 |
GenAI log IDs are not returned for Now Assist Genius Results | This issue occurs in Virtual Agent, portal, Now Assist Actions, Now Assist Q&A, Synthesized Response, or anywhere a Now Assist Genius Result (GR) can be returned. Feedback is not logged even though there should be a value after the user selects the Thumbs up icon or Thumbs down icon on the Genius Result (GR). |
Expected behavior: There should be a value such as 'Rejected' for negative feedback or 'Accepted' for positive feedback. Actual behavior: The feedback is not logged. |
|
Now Assist in Document Intelligence PRB2030125 |
Support attachments where the file names doesn't contain '.type' at the end | There's an error: '{"attachment":{},"task":{"708a54b23b 810f50141a0 e0f23e45a0b":{"error_msg":"Prediction server is not able to process the attachments: begin 0, end -1, length 9"}}}'. |
Observe an error. |
|
Now Assist Panel PRB2025041 |
A mic enabled for NAVA Premium Chat is incorrectly surfaced on Enhanced Chat |
Expected behavior: The Send button appears in the input bar. Actual behavior: On-Glide mic seen in input bar. |
|
|
On-Call Scheduling PRB2030962 |
The On-Call Scheduling family plugin is installed on upgrading to Australia. | The On-call plugin has been added as a dependency for the sn_sow_on_call plugin as part of core IT changes. This is causing issues for some users. On-call is automatically installed for new users via zboot. However, upgrade users need to install it manually. Due to the new dependency on the Store app, On-call is installed for some users when the commons bundle is upgraded. The dependency of the On-Call Scheduling plugin should be removed. |
Expected behavior: The On-Call Scheduling family plugin shouldn't be installed on upgrading to Australia. Actual behavior: The On-Call Scheduling family plugin is installed on upgrading to Australia. |
|
OneExtend PRB2025105 |
Responses fix for Java flow | Validate all the Java flow from NAVA, NAP and Skill Kit. | |
|
OneExtend PRB2025250 |
Correlation Insights skill is stuck on the progress bar when off-Glide is enabled | Insights should be generated and displayed. Instead, the progress bar spins indefinitely and no generative AI logs are produced. The issue occurs because the app prepares a bulk request with three payloads and invokes it in async mode with a callback handler. When off-glide is enabled for the capability, the async callback flow ('NowAssistforSIR CorrelationInsights Callback') appears to break silently. No generative AI logs are generated, indicating the LLM call never completes or the response isn't handled correctly. | |
|
OneExtend PRB2025367 |
A cloning instance should preserve mosaic functionality in the target instance | ||
|
OneExtend PRB2025540 |
Off-glide Mosaic pipeline ignores the per-request timeout and every call falls back to the platform default, regardless of caller intent or service-plan configuration | All Mosaic calls fall back to the platform default; caller / control-setting / service-plan values are ignored. There's no phase-boundary timeout enforcement and requests run well past their stated SLA. DT translation always uses 0L. |
Expected behavior: The caller-supplied timeout is the strongest signal and is honored by every Mosaic HTTP call in the pipeline (preprocess gate, primary execute, postprocess DT translation). In its absence, the control-setting, service-plan, and 60 second default apply (in that order). Exhausting the budget at any phase returns a timeout response (status=error, errorCode=400001). Override values are persisted to one_api_service_ plan.timeout_ms and cascade. Actual behavior: All Mosaic calls fall back to the platform default; caller / control-setting / service-plan values are ignored. There's no phase-boundary timeout enforcement and requests run well past their stated SLA. DT translation always uses 0L. |
|
OneExtend PRB2025975 |
Do not log prompts or responses to Splunk for in-country routing users | Prompt and response information is removed from logs for users with in-country routing SKU. | |
|
OneExtend PRB2026081 |
There's a 100501 error with an async call | ||
|
OneExtend PRB2028533 |
Java scriptable methods aren't working in some instance nodes | ||
|
Performance Analytics Dashboards PRB1993682 |
'This report has been migrated to a visualization' banner is shown when the unified property is false | The banner message appears: 'This report has been migrated to a visualization. Migrated visualization is here.' The link redirects to a random visualization. |
Expected behavior: The banner isn't shown, as no report was migrated. Actual behavior: The banner message appears: 'This report has been migrated to a visualization. Migrated visualization is here.' The link redirects to a random visualization. |
|
Performance Analytics Dashboards PRB2005720 |
The CoreUI dashboard selector triggers excessive ACL checks | The ACL is evaluated with a different access path and context for each check, so it is re‑executed repeatedly. When there are thousands of dashboards, this results in excessive ACL evaluations and causes the instance to hang. |
Expected behavior: The dashboard selector avoids excessive ACL checks and runs one check per dashboard. Actual behavior: It triggers permission evaluation for every dashboard the user has access to, including an ACL check per dashboard and multiple field‑level ACL checks. |
|
Performance Analytics Dashboards PRB2013831 |
There's a dashboard layout issue after upgrading an instance to Australia | After an Australia upgrade, multiple users are reporting issues with alignments of reports in dashboards. While reports aren't missing, they are displayed vertically in dashboards. The issue is reproducible with core legacy dashboards. |
Refer to the listed KB article for details. |
|
Performance Analytics PRB1990900 |
The system property com.snc.pa.dm.enable.mlb is set to true on non-Raptor DB Pro instances | Users can install a plugin with Raptor DB (pro or standard). With a schedule job, they can disable the feature by disabling the global property com.snc.pa.dm.enable.mlb. |
Expected behavior: The property is set to false. The user shouldn't be able to control it and set its values. Actual behavior: The property is set to true. The user can control it and set its values. |
|
Performance Analytics PRB1995131 |
There are Query Builder (QB) and Workspace UI error popup clips in the surrounding UI if a query fails for CMDB NLQ | Turning off the NLQ Prediction server results in an error message in both QB and in the CMDB Workspace, and the UI doesn't render as expected in CMDB Workspace. |
Notice that this results in the 'Oops...' error, and the UI is incorrect. |
|
Performance Analytics PRB1999245 |
Discrepancies with Core UI on change and change percentage | The change and change percentage may be displayed on the widget but not on the data visualization. |
Notice that the widget displays the change (100) and change percentage (100%). |
|
Performance Analytics PRB2009359 |
Turn off/delete the 'Populate Indicator Source Row Count' job, as the guardrails are deprecated in Australia | ||
|
Performance Analytics PRB2014881 |
Core UI widget date settings aren't retained on dashboards |
Refer to the listed KB article for details. |
|
|
Platform Analytics Component API PRB2016214 |
oob-pa-cxo-apps are missing from the Glide distribution due to an app packaging issue | These apps have an incorrect scope and aren't included in the ZIP or DIST packaging. As a result, users aren't able to auto-upgrade to the latest versions of these apps through the monthly release pipeline. | |
|
Platform Analytics Dashboard API PRB1988004 |
Platform analytics displays an incorrect view for the most recently viewed dashboards | The Recent Dashboards list includes dashboards that were not previously accessed. While actively using the instance, the list appears to update as the user opens certain dashboards. However, after logging out and logging back in, the Recent Dashboards list resets and once again displays dashboards that haven't been used. |
Observe that the 'Recent Dashboards' list resets and displays a different, seemingly random list of dashboards instead of the ones previously accessed. |
|
Platform Analytics Dashboard API PRB1992984 |
Can't share a dashboard to all internal users (users with at least one role) | When the itil user opens the dashboard, the dashboard isn't found. |
Expected behavior: The dashboard is visible to the itil user. Actual behavior: The dashboard isn't found. |
|
Platform Analytics Dashboard API PRB1998865 |
Sys ID is automatically populated for the value in sys_translated | This happens when the user changes the value of a tab when using a non-English language. |
Notice that the value in sys_translated contains sys ID. |
|
Platform Analytics Dashboard API PRB2002552 |
Due to VCS update set collision, a dashboard save fails with a generic error: 'Your dashboard could not be saved' | This problem only happens in scopes with VCS-controlled apps, no matter where users create the dashboard. The important factor is whether the scope has a repo configuration set. | |
|
Platform Analytics Dashboard API PRB2005188 |
Override the scope of any par_dashboard_* record with the scope received from the dashboard | ||
|
Platform Analytics Dashboard API PRB2006097 |
Allow the user to turn on/off the AI summary generation in a dashboard |
Expected behavior: The NACM shouldn't appear. Actual behavior: The NACM appears again. |
|
|
Platform Analytics Dashboard API PRB2007784 |
DomainService uses DomainSupport.hasAccess instead of DomainHierarchy for validation | When the user tries to access the dashboard, an error appears: 'Error while getting domain for dashboard'. | |
|
Platform Analytics Dashboard API PRB2014426 |
A duplicated dashboard doesn't persist an AI summary generation value |
Expected behavior: The dashboard summary should be visible in the duplicated dashboard. Actual behavior: The dashboard summary isn't visible in the duplicated dashboard. |
|
|
Platform Analytics Dashboard API PRB2025067 |
The sys_translated record for par_dashboard_tab is overwritten | This can cause translations to be lost. |
Observe that the translation is lost because the sys_translated record is overwritten. |
|
Platform Analytics Filters PRB2013316 |
Addtional controls for single and multi select | For both radio buttons and checkboxes, there should be a way to clear the selection instead of using the 'Clear all filters' capability on the dashboard level. | |
|
Platform Analytics Filters PRB2014365 |
JavaScript-based sys_choice labels are rendered as raw text in dashboard filters | A sys_choice record uses JavaScript to dynamically populate the country label when the value is null. However, when this field is used in Platform Analytics dashboards (via indicator breakdown with sys_choice as the facts table), the JavaScript isn't evaluated and is instead displayed as raw text in the filter. | |
|
Platform Analytics Migration API PRB1989820 |
Users with the itil role are shown reports in read-only mode | If a user has the itil role, there should be no read-only mode. It should display in 'Edit' mode. | |
|
Platform Analytics Migration API PRB1998821 |
The Platform Analytics Migration Center summary window isn't counting all domain dashboards when doing migration in the global domain | ||
|
Platform Analytics Migration API PRB2003834 |
AppTier CPU increases by 4 points (~18%) when background jobs are turned on | AppTier CPU increased in Australia compared to the Zurich baseline when background jobs are turned on during loadsim performance testing. The primary driver is the 'events_process_0' background job, which regressed +254% in average execution time. The 'Script Action: Refresh ready_to_migrate after XML load' runs every time there is an XML load on tables pa_m2m_ dashboard_tabs, pa_tabs, sys_portal, and sys_portal_preferences. The event action runs a script that looks at all dashboards' related artifacts, makes an assessment, and fills out the 'ready_to_migrate' column on each dashboard. This action is unnecessarily long-running because it attempts to update all dashboards, most of which aren't needed. | |
|
Platform Analytics Migration API PRB2010427 |
Turn off auto-conversion of homepages to CoreUI dashboards after upgrades | 1000 homepages are migrated every day, and it triggers a business rule that migrates CoreUI automatically. | |
|
Platform Analytics Migration API PRB2022823 |
Allow users to configure the redirection of Core UI Performance Analytics widgets to the Analytics Hub instead of to 'KPI details' | Users that activated Next Experience after migrating or upgrading to Australia will be redirected to 'KPI details' when selecting a Performance Analytics widget, even if they keep using Core UI dashboards. This issue occurs because the unified_analytics property forces the re-direction to 'KPI details'. | |
|
Playbook Experience PRB2007586 |
Declarative Action marks playbook activity as complete despite throwing an error from the UI action | When a custom declarative action is configured with the action model set to 'Playbook Card' in order to display a button on a playbook activity, the expected behavior after displaying an error is as follows: if the UI action invoked by the declarative action displayed an error message, the error was displayed to the user, and the underlying activity was not marked as complete. This allowed the user to address the issue before proceeding. As of the Zurich release, this behavior has changed. When the UI action returns an error message, the error is displayed to the user; however, the activity is also marked as complete. This represents a change in the expected workflow, as the activity now progresses regardless of whether the error condition has been resolved. |
Refer to the listed KB article for details. |
|
Playbooks (Family Channel) PRB2012190 |
When any one pill value is null, it returns null for the value of the whole input field | This happens for any multi pill-text inputs. |
Expected behavior: The dynamic input value returns for the other 2 dynamic inputs set. Actual behavior: The whole dynamic input value is set to empty. |
|
Playbooks (Family Channel) PRB2021433 |
Dot-walkers aren't working on the 'Recommended actions' table for playbook inputs |
Expected behavior: The playbook inputs dotwalker should have content inside, and it's the case table meta fields. Actual behavior: The dotwalker opens to have empty content. |
|
|
Playbooks (Family Channel) PRB2023731 |
Child agent changes in playbook snapshot for hybrid agent configuration | This is a product update. | |
|
Process Mining Workspace PRB1972729 |
On the 'Opportunity details' page, when applying views on the process map, the progress tracker isn't displayed and the user has to hard refresh the page to apply views |
See that the progress tracker isn't updating and the user has to hard refresh the page to apply the view. The 'Scheduled task completed' alert is displayed but the scheduled task isn't displayed in the 'Scheduled tasks' panel of the page. |
|
|
Process Mining Workspace PRB1980574 |
The Process Mining app should be free on the store | Process Mining is shown as a licensed app on the store. However, it's auto-installed on many instances, which causes confusion when users aren't able to upgrade. |
Scenario 1:
Scenario 2:
Expected behavior: Users can update the app to the latest version. Actual behavior: Users get a license error, so they can't proceed with the app update. |
|
Process Mining Workspace PRB1984137 |
The 'Project' card gives an incorrect average duration |
Mine a playbook project. Observe the average duration on the project card and the average duration in the project itself. Notice that they are not the same. They should match. |
|
|
Process Mining Workspace PRB1990953 |
Change the default number of records per cluster in a request to '50' | Currently, it sends 200 records per cluster to create the intent and activities. Since there are 5 clusters in each request, it takes more processing time. By reducing the number to 50, the request should be processed in about 10 minutes. | |
|
Process Mining Workspace PRB1994902 |
When clustering on intermodal arcs, 'show records' redirects to a child table with 'No records to display' |
Expected behavior: The user should be shown the incidents belonging to the cluster. Actual behavior: Observe that the user is redirected to the 'Task SLA' list page with a 'No records to display' message. |
|
|
Process Mining Workspace PRB2003893 |
Duplicate results display when 'Intent and activity analysis' is applied on a filtered model |
Expected behavior: The 'View results' card shouldn't be displayed on a breakdown applied model. It's a new task altogether. Actual behavior: It triggers and 'Intent and activity analysis' and generates the duplicate results. |
|
|
Process Mining Workspace PRB2005530 |
Users can't submit an automated finding def when the left navigation search panel is opened |
Observe that the buttons are not visible/accessible. |
|
|
Process Mining Workspace PRB2008088 |
Project setup data fetch fails when a user with no role opens the shared project configuration |
Notice that data on project setup fails to load. |
|
|
Process Mining Workspace PRB2011383 |
Backport the Appsee event | ||
|
Project Management PRB1980002 |
There's an report_view ACL error for a few widgets |
Open tab in Strategic Planning workspace. Observe a report_view ACL error for the 'No Planned Cost' and 'No Planned benefit' widgets. |
|
|
Project Management PRB2009176 |
Opening the Project Status Report in the Project Workspace triggers an update to the Overall Health field on the corresponding project record | Opening the Project Status Report within the Project Workspace updates the Overall Health field on the corresponding project record to match the value from the status report. |
Notice that the Status field is automatically reverted to match the Overall Health value from the status report. |
|
Project Management PRB2021806 |
Add a 'No status' option to the Project status field | The Project status field (pm_project.status) currently doesn't include a 'No status' option, which prevents projects from having an unset/neutral status state. This causes ambiguity in reporting and makes it difficult to distinguish between projects that have not yet been assigned a status versus those intentionally marked as 'On Track' or 'At Risk'. A 'No status' option should be added to the Status field choice list. This ensures that status transitions — including from an unset state to a defined status — can be accurately captured and reflected in usage analytics. |
See that a 'No status' option should be available. |
|
Record Hierarchy PRB2013585 |
Reconciliation of record hierarchy with missing path field skipped | If the user deletes the rh.hierarchy.create event, there is no 'Reconcile Hierarchy' link under Related Links. If the user executes SNC.RecordHierarchyAPI.get().reconcilePaths(sysId), no event is posted to resume creation of the hierarchy. |
Observe that nothing happens. No event is posted to resume creation of the hierarchy. |
|
Record Hierarchy PRB2014979 |
Allow RecordHierarchies to always be usable optionally unless it is disabled | The current behavior shows that after a record hierarchy is defined, any query operations that use the hierarchy will explicitly return 'false' until every record in the hierarchy has been assigned a path. After paths have been assigned, the hierarchy is said to be 'usable' as its fully initialized and ready for queries. A GP was added to optionally allow the hierarchy to be usable while records are being assigned paths. The results for queries may be incomplete or partially stale depending on how long the initialization takes place, but should otherwise be accurate. Users are beginning to use IN_HIERARCHY conditions for all sorts of features ranging in criticality, up to and including ACLs. If the record hierarchy runs into some sort of issue, such as it can render the record hierarchy unusable and all queries would begin to fail. However, the paths assigned to all records are still valid as long as changes are minimal, and can continue to return mostly accurate results while any issues with the record hierarchy feature are addressed. This fix is to address usability; as long as the record hierarchy isn't explicitly deactivated, it can be made 'usable' and queries will return results based on whatever paths may be assigned at the time. | |
|
Record Watcher PRB2016869 |
IndirectRecordCollector. setPreviousValueFrom PreviousRecord throws an error on a null ElementDescriptor in a dotwalked path, aborting Record Watcher enqueue and stalling flows | When a sys_rw_indirect_query is configured with a dotwalked condition path that contains a field segment which does not exist on the traversed table (returns null from getElement()), IndirectRecordCollector. setPreviousValueFrom PreviousRecord at line 304 calls fieldEd.getReference() on a null ElementDescriptor and throws an error. This exception propagates up through RecordWatcherService.enqueue, aborting the entire enqueue and silently preventing all flow responders from executing for that record update. Flows waiting on a catalog task or incident completion stall permanently — the sys_flow_rw_action record is created but never processed, and DeferredResponderHandler does not recover this class of failure. |
Observe in the transaction log: 'RecordWatcherService SEVERE *** ERROR *** record-watcher: Caught error attempting to enqueue change [table.sys_id] followed by java.lang. NullPointerException: Cannot invoke "com.glide.db.ElementDescriptor.getReference()" because "fieldEd" is null at IndirectRecordCollector. setPreviousValue FromPreviousRecord (IndirectRecordCollector.java:304). Observe that any flow responder waiting on that table/record never executes — sys_flow_rw_action record is created but state never advances. |
|
ReleaseOps - Family PRB1966100 |
Deployment Analyzer forms are broken | Deployment Analyzer forms are empty, breaking reports. Users are unable to fix it because when they go to form layout, no fields are listed. |
Refer to the listed KB article for details. |
|
ReleaseOps - Family PRB2009639 |
Instance scan failure doesn't return the correct message | The scan failure doesn't mention a reason for the failure in the work notes. |
Expected behavior: The scan failure shows the reason for the failure in the work notes. Actual behavior: The scan failure doesn't mention a reason in the work notes. |
|
Resource Management PRB2003945 |
Cost plan breakdowns are duplicated | When the user changes the start date and end date from a resource plan, the business rule (BR) UpdateCostPlanAssociatedToResourcePlan launches an event. The BR 'Recreate Requested Allocations' is also launched, updating the resource plan again and changing the planned cost. In summary, when the user updates the dates, the system updates the resource plan twice, one time for the dates and another for the planned cost, practically at the same time. Both changes trigger the BR UpdateCostPlanAssociatedToResourcePlan and two events are created. Since there are two events in the system, they will try to perform the same action, and this could lead to problem concurrency. The two events are processed at the same time and the cost plan breakdowns are created twice. |
|
|
Resource Management PRB2020809 |
Updating dates in the assignment should update the resource availability | Dependent choice config should also be supported in the project workspace bottom grid. |
Observe that the dependent config isn't supported in bottom grid choices. It should be supported. |
|
Resource Management PRB2024520 |
Fetching choices with their dependent field values to prepare criteria | The created field doesn't show the choices as per the dependent config defined. |
Observe that the created field doesn't show the choices as per the dependent config defined. |
|
Restricted Caller Access (RCA) PRB2029429 |
There's a Zboot error due to a syntax error | There's an error: 'Error : *** ERROR *** invalid return (refname; line 7)'. | |
|
Security Incident Response Explorer PRB2013795 |
The sub-project oob-secops-npm-apps in oob-apps isn't picked up in a Glide build | The apps are missing in Glide's distribution. | |
|
Seismic Framework PRB1972265 |
Ancestor path retains the parent element using hard references and can make small memory leaks larger, depending on retention | In some cases, the retainer is the variable ANCESTOR_PATH, as it holds on to hard references to the ancestor elements. Since elements in the ancestor path are retained, it may make a small leak larger if the elements themselves are large in nature (lists, forms, client state data brokers, etc.). | |
|
Server-side scripts PRB2022176 |
The script name should be logged when a page title is unavailable in the 'Guarded Scripts' list entry | The page title can be empty in some cases, such as a scheduled job and probably more. It should become the script name if there isn't a page name that makes sense. | |
|
Server-side scripts PRB2022324 |
Logging for all sandbox scripts is broken |
Execute a script in the sandbox. See that it should be logged, but isn't. |
|
|
Service Catalog Portal Widgets PRB1966196 |
There's an issue with 'Also Request for' | Duplicate requested items (RITM) are generated when the same user is selected in both the Requested For and Also Request For fields. When the Requested For user is selected first, it automatically removes that user from the Also Request For list, preventing duplication. However, when a user is selected first in Also Request For and then again in Requested For, the platform allows the same user to be selected in both fields. This results in multiple RITMs being generated for the same user. |
Actual behavior: Duplicate RITMs are created for the same user. Expected behavior: The system should prevent selecting the same user in both fields. |
|
Service Catalog PRB2014228 |
Update the copy in the alert banner | Catalog item forms should be automatically pre-filled using the context from the conversation. The user shouldn't have to to re-enter information they've already shared in the chat. | |
|
Service Catalog PRB2020118 |
Ensure that a search term is a minimum of 3 words before triggering the slot fill | ||
|
Service Mapping PRB1998724 |
'Create Layer 2' connections causes Out of Memory (OOM) errors if the device has many router interfaces | The creation of 'Layer 2 Connections ' can cause excessive memory and multi-node events. |
Notice that all the records will be used for calculation. |
|
Service Mapping PRB2006053 |
There's a missing conditional_table_ query_range ACL for the cmdb_ci_service_discovered in the plugin com.snc.cmdb.it_service | Calls can fail at runtime, causing range query operations to be denied. | |
|
ServiceNow SDK (Glide) PRB2016794 |
Skip delete issue for 'Coalsce' tables | When a Fluent app defines a role, the SDK generates a new sys_id. The existing ScopeConflictDetector keys off sys_update_name (which encodes the sys_id), and finds nothing in sys_metadata, so no conflict is flagged. The installer then coalesces onto the real global admin role by matching the Name field and silently overwrites its sys_scope, stealing a system-owned record into the app's scope. |
Expected behavior: The Global role shouldn't be overridden. Actual behavior: The Global role is overridden. |
|
ServiceNow SDK (Glide) PRB2021468 |
Dictionary updates aren't propagated when installed via FluentXMLUploader | When the user deploys changes, the dictionary updates get skipped. |
Expected behavior: The maxLength of the column is updated. Actual behavior: The dictionary updates get skipped. |
|
Service Operations Workspace for Change Management PRB1921763 |
A reference qual isn't working for a dependency field on the Service Operations Workspace (SOW) 'Overview' page | A dependency field on the SOW 'Overview' page isn't working, as the 'Assigned to' field won't only return the available users from the assignment group value, but rather the whole itil user list. |
Expected behavior: See only users in the 'Application Development' group. Actual behavior: More users are shown that aren't in the 'Application Development' group. |
|
Service Operations Workspace for Change Management PRB1977258 |
In Service Operations Workspace (SOW), there's a JavaScript (JS) error 'Assess risk', and the modal doesn't open |
This should open a modal with the assessment and its answers to allow changes, but nothing happens. Also, there's a JS error in the browser's console. |
|
|
Service Operations Workspace for Change Management PRB1981820 |
Service Operations Workspace action bar buttons aren't displayed even if 'Display action' is set to true for a change state |
Refer to the listed KB article for details. |
|
|
Service Operations Workspace for Change Management PRB1983773 |
Overview tab sections are refreshed on an update | When working in the Service Operations Workspace (SOW) change request overview, the sections are refreshed whenever any field in the 'Scope and Impact/Schedule/Summary' section is updated. This problem occurs only when the fields in the 'Assignment' section, specifically 'Assignment group' or 'Assigned to', are filled in. If these fields are left blank, the issue doesn't occur. |
See that the 'Overview' section begins to refresh, which shouldn't occur. This same issue arises when updating fields in other sections. |
|
Service Operations Workspace for Change Management PRB1987932 |
In 'Change Management' in Service Operations Workspace (SOW), the Assess Risk button isn't working | When a user attempts to complete a risk assessment for a change request in SOW, the modal appears briefly and then immediately closes. |
Refer to the listed KB article for details. |
|
Service Operations Workspace for On-Call Scheduling PRB1993717 |
On Service Operations Workspace (SOW), there's no place to set the rotation start time for the roster | When users create the shifts on SOW, the rotation is automatically happening at midnight. |
See no place to set the rotation start time. |
|
Service Operations Workspace PRB1982622 |
The declarative action 'Copy Link' introduced in Service Operations Workspace (SOW) throws an error: 'Declarative Action scripted client condition expression evaluation failed' | The declarative action 'Copy URL' was updated to include values in the scripted client condition in the latest upgrade of SOW. The scripted client condition was empty earlier. While this declarative action is in the SOW application scope, 'Enable for all Experience' is checked, so it's rendered for Project Workspace/other configurable workspaces as well. The error is thrown because it can't be evaluated for Project Workspace. | |
|
Service Operations Workspace PRB2013463 |
Customer Service Management workspace experience is not opening in UI Builder |
Observe that it's opening with a 500 internal server error. |
|
|
Service Portal PRB1981788 |
A non-admin user can't view the notification on a portal and are getting the recordUpdateCount |
Log in to a portal with some non-admin user. Expected behavior: A notification shall appear for the non-admin user. Actual behavior: Check for the notification and see that no notification is visible. |
|
|
Service Portal PRB1999839 |
When Multi-factor Authentication (MFA) and Password Needs Reset is true, the password reset workflow refreshes after selecting 'Submit' on the initial login and redirects to the backend Platform UI | When MFA is configured on an instance and Password Needs Reset is set to true on a vendor contact record, they are presented with a screen to change their password on initial login. After changing the password on the initial screen and clicking submit, the page refreshes back to the same password reset screen. If they perform the same steps again and click submit, they are finally redirected but the redirect is incorrect and redirects the user to the backend UI. |
Refer to the listed KB article for details. |
|
Service Portal PRB2013342 |
In Australia, the Mission Control (/mc) portal fails to load the Bootstrap CSS (sp-bootstrap-rem.scss), while the same configuration works correctly in Zurich | In Australia, the Mission Control (/mc) portal no longer auto-loads the Bootstrap CSS (sp-bootstrap-rem.scss), resulting in whole portal not loading correctly. The same portal, theme, and configuration work correctly on the Zurich instance, indicating a release-specific behavior change. |
Refer to the listed KB article for details. |
|
Service Portal PRB2014571 |
Alignment of the Now Assist search results gets overflow | This happens on the portal while loading on browser resolution size 360 x 640. |
Observe that the filter text 'Am relevantesten' gets overflow. |
|
Service Portal PRB2020265 |
The 'Homepage Search' section isn't available at higher zoom levels |
Actual behavior: The 'My Saved Bundles' section isn't available on a catalog page at higher zoom levels. Expected behavior: The 'My Saved Bundles' section is should be available on a catalog page at higher zoom levels. |
|
|
Session Management PRB2024286 |
Make application nodes more resilient to DDoS attacks from unauthenticated traffic | This is a product update. | |
|
Sidebar (Family Release) PRB2019090 |
the cached RecordCard is returned without checking if the user has access to record | This is a caching issue, and occurs for both with Incident and HR records. When the code checks if the Record Card is in the cache, it does not re-check if the user can access the record or not. When clearing the cache, the record access check is calculated correctly. |
Notice that it renders a record card, and the user Abraham Lincoln cannot access INC2 in the sidebar chat. The INC2 record card is not in the cache. |
|
Sidebar (Family Release) PRB2023462 |
Turn off the sidebar collab chat scope main enablement |
Expected behavior: The file should get attached to the discussion. Actual behavior: The error message 'User is not authorized' appears. |
|
|
Software Asset Management PRB2018383 |
A Microsoft per‑core license metric isn't visible after a Zurich or Australia upgrade | The 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. |
Refer to the listed KB article for details. |
|
Software Asset Management Workspace (Glide) PRB1992196 |
In Software Asset Management workspace, the 'Assets Covered' tab is in English | It should be translated. |
Note that the 'Assets Covered' tab isn't converted to German. |
|
Software Asset Normalization PRB1991265 |
Regex normalization suggestions are incorrectly excluded when the product map sets suggested_rule_table on the Discovery model | _createSuggestionsForRegexDMs() in NormalizationEngine has a 'NOT IN' filter that excludes DMs with suggested_rule_table in [PACKAGE_MAP_TABLE, PRODUCT_MAP_TABLE, PATTERN_RULES_TABLE, WIDE_NET_MAP_TABLE]. PRODUCT_MAP_TABLE shouldn't be in this exclusion list because product map rules don't create their own suggestions — they are only a stepping stone for wide-net suggestions. |
Expected behavior: A Regex suggestion should be created, because product map rules don't generate suggestions themselves — they only serve as an entry point for wide-net processing. Regex should be evaluated for DMs where product map is the only suggested rule table. Actual behavior: No Regex suggestion is created. The DM's suggested_rule_table is set to samp_product_map (by the product map suggestion path), which causes _createSuggestionsForRegexDMs() to exclude this DM from regex processing via the NOT IN filter. |
|
Software Asset Normalization PRB2013453 |
The 'Find Normalization Suggestions' job fails to create suggestions for Regex rules due to accessing the private closure variable _regexMap | NormalizationEngine._createSuggestionsForRegexDMs() accesses regexEngine.regexMap, but _regexMap is a private variable inside RegexNormalizationEngine's IIFE closure. It is not exposed as a public property. The code also called getDM() and applyRegexRuleToDiscoveryModel() in a loop over this inaccessible map, so the entire regex suggestion path was non-functional. |
Expected behavior: A normalization suggestion should be created linking the discovery model to the matching Regex rule. Actual behavior: No normalization suggestion is created for Regex rules. The job silently fails for the Regex code path. |
|
Software Asset Reconciliation PRB2015480 |
Regex normalization discards edition_map (including versionMap) when edition_index is null on the rule | In _buildRuleObject(), the edition_map is guarded by 'gr.edition_index && gr.getValue('edition_map')'. When edition_index is null/empty, the entire edition_map (including its versionMap) is replaced with an empty object. |
Expected behavior: The edition_map should be parsed regardless of edition_index, so that versionMap entries are applied to remap version values. Actual behavior: The versionMap isn't applied. The version value is not remapped because edition_map is discarded when edition_index is null. |
|
Software Asset Reconciliation PRB2018394 |
Regex normalization ignores product license exception rules, as it stamps the product type directly from samp_sw_product instead of consulting the exception map | Both setDiscoveryModelNormalizedValues() and findSuggestedValues() used ruleObj.productType directly (which comes from samp_sw_product.product_type) bypass product license exception rules. Other normalization paths (pattern, package map) already consult these exception rules via NormalizationEngine._getProductTypeFromRule(). |
Expected behavior: The discovery model's norm_type should be 'not licensable' (honoring the Product License Exception Rule), consistent with how pattern and package map normalization paths behave via _getProductTypeFromRule(). Actual behavior: The discovery model's norm_type is set to 'licensable' (taken directly from samp_sw_product.product_type). The same issue affects the suggestions path — findSuggestedValues() also returns the wrong productType, causing incorrect suggested values. |
|
Software Asset Reconciliation PRB2020394 |
The 'Apply latest content changes' job fails for Regex normalization rules due to calling a private function as an instance method | SampRegexNormalization RuleContentUpdate Handler.reEvaluate DiscoveryModels() calls this.regexEngine. buildRuleObject(ruleGr), but buildRuleObject is a closure-private function inside RegexNormalizationEngine's IIFE — it isn't exposed as an instance method. This causes every content update for Regex rules to crash. |
See that the job fails with an error: 'Cannot find function buildRuleObject in object [object Object]'. |
|
Software Entitlements PRB2023511 |
Add an asset tag, agreement number, and location to entitlement duplicate check attributes | This is a product update. | |
|
Standard Ticket Page PRB2023619 |
Family changes to fetch summary fields from the m2m table | This is a product update. | |
|
System Archiving PRB1988156 |
Archive reparenting doesn't work with peripherals and large table names | The records for sys_audit and sys_journal_field don't reparent, and an error is found in the logs. |
Notice that the sys_audit and sys_journal_field records don't reparent. Instead, the log shows this error, 'Found in current data management track'. |
|
Table Administration and Data Management PRB2025009 |
Ordering a query by a Function field that wraps a translated_text column returns blank values for that list |
Expected behavior: The 'Name Function' column shows Älice_sv and Bob_sv (or the English fallback). Actual behavior: The 'Name Function' column is blank for both rows. |
|
|
Trace Collector - Family Release PRB2023730 |
Trace collector Epic | This is a product update. | |
|
Trace Collector - Family Release PRB2030648 |
The Azure Application Insight throws an error | During testing of the Application Insight feature, users are intermittently seeing an error: 'Unable to find app_insights_config.json'. | |
|
UI Actions PRB2013168 |
Support actions in AINPX | This is a product update. | |
|
UI Builder (Family Channel) PRB2023628 |
Configuration table, APIs and ACLs | This is a product update. | |
|
UI Field Administration PRB1969665 |
Currency values change automatically in workspaces | The currency value changes automatically when selecting in and out of the Currency field, without actually changing the value. |
Observe that the value changes. |
|
UI Field Administration PRB1982868 |
The pop-up related to the Comment/Work Note web link only displays in the boundary of the 'Compose' tab | The message, 'The URL you entered seems to be an external link. Do you want to add the required http:// prefix' is confined to the 'Compose' section and not overlaying the page. This occurs in the CSM workspace, Service Operations Workspace (SOW), and the HR workspace. This issue occurs in Safari browsers, but has been resolved in Chrome browsers. |
Observe the message, 'The URL you entered seems to be an external link. Do you want to add the required http:// prefix'. The message is confined to the 'Compose' section, and not overlaying the entire page. |
|
UI Field Administration PRB1985085 |
Quick action visibility script is executed in global scope, preventing access to scoped script includes | The quick action runs into an error: 'Evaluator.evaluateString() problem: java.lang.SecurityException: Illegal access to package_private script include...' |
Notice the quick action runs into an error: 'Evaluator.evaluateString() problem: java.lang.SecurityException: Illegal access to package_private script include CMDBGenAICIFormContextualHelp: caller not in scope sn_cmdb_gen_ai: com.glide.script. RhinoEnvironment.checkScriptableAccess (RhinoEnvironment.java:723) com.glide.script. ARhinoScope.checkScriptableAccess (ARhinoScope.java:134)'. This happens because the visibility script is evaluated in the global scope. |
|
UI Field Administration PRB1998819 |
WWNAglobal utils should be removed | ||
|
UI Field Administration PRB2017755 |
The text command shortcut behavior is confusing |
The user finds this confusing and would rather that the text commands always have to be selected from the list instead of being triggered directly via the keyboard. |
|
|
UI Field Administration PRB2025633 |
AI Agent modified fields API returns aiCreated instead of isAiCreated in JSON response | The boolean field is named incorrectly. |
Expected behavior: The boolean field is named 'isAiCreated'. Actual behavior: The boolean field is named 'aiCreated'. |
|
UI Form Administration PRB1988524 |
The copy/paste functionality is not working in the 'Email' section of the workspace. | This issue occurs after upgrading to Zurich. |
Expected behavior: The user is able to copy and paste. Actual behavior: The user is not able to copy and paste. |
|
UI Form Administration PRB1999196 |
The citation URL is retained and fields are highlighted when the user logs in to an instance again | The highlight should happen only if the user selects links in a summary or the email outputs. | |
|
UI Form Administration PRB2006958 |
Introduce system property to hide form level TI banner | The alert appears when the form is loaded. There's no way to avoid seeing the alert if not required. |
Observe that the alert appears again. |
|
UI Form Administration PRB2010217 |
UI Policy date comparisons are stale after waiting on the page in Workspace | ||
|
UI Form Administration PRB2013158 |
Form and client scripting work for Lit components | This is a product update. | |
|
UI Form Administration PRB2013160 |
Handle a graphql error for a boolean choice field | This is a product update. | |
|
Upgrade Center PRB2023239 |
There is a mismatch in the Glide version between the app node and the database following an upgrade | A new code path introduced the MariaDBI18NSQLFormatter class. When the sys_properties record of the 'com.glide.db.session _language_collation_feature' property is set to true, it takes a code path upon upgrade or restart where an instance will not come up. When 'com.glide.db.session _language_collation_feature' is false, the code path exits early and doesn't cause this issue. |
Refer to the listed KB article for details. |
|
Usage Analytics PRB2021289 |
Long session durations are observed for few Usage Insights Sessions, causing inaccurate session duration metrics | A fix for long session duration in some Usage Insights sessions. | |
|
UX Framework PRB1969085 |
GraphQL schema changes for client-interaction.graphl in ux-metrics | The user sees error logs from the ClientMetricsRestService.java file. The error logs are logged to the syslog table. |
Refer to the listed KB article for details. |
|
UX Framework PRB1986291 |
List dynamic routing shouldn't be applied when creating a record from a related list | Dynamic routing is handled within the recordRoutesMapping Client Script Include. Kb_knowledge mapping uses source_component: 'list' to route article clicks to kb_view. When the New button is selected on a related list, the kb_view route is incorrectly applied. Since kb_view can't handle new records, the page breaks. | |
|
UX Framework PRB1995434 |
Modeless dialog with dynamic content fails to render repeater-driven lists on subsequent opens | Users experience a broken user interface when reopening modeless dialog windows that contain dynamically loaded content. On second and subsequent opens, repeater-driven lists fail to appear, preventing users from interacting with required dialog data. This impacts workflows that rely on repeatedly opening dialogs and creates a confusing, non-deterministic user experience. The failure is silent and no visible error is shown. | |
|
UX Framework PRB2002772 |
Preset for the presentational list (nested inside the record list bundle) wasn't discovered during pre-population | The list is completely broken. |
Observe that the SOW list page is also broken and empty. |
|
UX Framework PRB2018001 |
A blank page issue on some nodes during upgrade | This issue occurs in Australia instances. |
Observe that there is a empty page is displayed with a spinning wheel. |
|
UX Framework PRB2023614 |
In-product surveys MVP | This is a product update. | |
|
UX Framework PRB2030213 |
When a user navigates between two pages that both have IPS surveys configured, the survey triggered on the first page isn't dismissed upon navigation | ||
|
Virtual Agent Designer Legacy PRB1752802 |
The virtual agent designer page isn't accessible on Safari | All seismic and Core UI pages should work on Safari 17.1+ for Washington and 17.3+ for Xanadu. |
Observe the following error: 'Safari and older versions of Internet Explorer are unsupported browsers, please switch to a different or newer browser.' |
|
Virtual Agent PRB1977665 |
The 'Pagination' API doesn't reset totalSearchResultsCount if a search term is removed |
|
|
|
Virtual Agent PRB1985280 |
Duplicate attachment is displayed in Virtual Agent after portal refresh |
Expected behavior: Nothing happens. Actual behavior: The duplicate attachment/image is displayed only in Virtual Agent. |
|
|
Virtual Agent PRB1989524 |
Consecutive chat interactions from Customer Service Management (CSM) portal have anempty 'Account' and 'Contact' field |
The 'Assigned to = Virtual Agent' has the first interaction has Account and Contact fields filled, but the next interaction records are missing the Account and Contact fields. |
|
|
Virtual Agent PRB1999511 |
Message preview and unread badge count don't work on page refresh | When the user refreshes the page, the message preview doesn't show up. On standard chat, there's also no unread badge count. |
Expected behavior: There is still an unread badge count and the message preview shows up. Actual behavior: The message preview doesn't show up. On standard chat, there's also no unread badge count. |
|
Virtual Agent PRB2003424 |
External users are unable to delete closed chats from the Virtual Agent chat history | External users are unable to delete closed chats from the Virtual Agent chat history and encounter the error message: 'Failed to delete conversation. Please try again'. |
Notice that the error message appears: 'Failed to delete conversation. Please try again'. |
|
Virtual Agent PRB2003812 |
Sonar test coverage should be 80% for the Data Collector module | ||
|
Virtual Agent PRB2006240 |
The Virtual Agent server doesn't process pre-chat surveys for bot 2 bot | Users aren't routed to a live agent in bot to bot conversations. This was due to a misconfiguration where pre-chat survey was enabled and the user wasn't able to provide a response. Interactions aren't assigned to the queue or an agent in Agent Workspace. It was working when the user first upgraded, but recently has stopped. |
Notice that the conversation doesn't get routed to the live agent. |
|
Virtual Agent PRB2007255 |
There's memory pressure on nodes due to high memory for the cache 'com.glide.cs.qlue. module.coma. MessageBatchingSession' | Users with 2GB nodes may encounter memory issues that can cause the events process jobs to yield. |
Run a heap dump. Observe that MacMessageBatchingSession or MessageBatchingSession uses over 50 MB of memory. |
|
Virtual Agent PRB2012889 |
vaSystem.getSearchText isn't working with offGlide | ||
|
Virtual Agent PRB2013847 |
Create a new scriptable API for endChatSummarization | ||
|
Virtual Agent PRB2015140 |
Multiple interactions are created during live agent execution | This only happens when a conversation is reset or abandoned. | |
|
Virtual Agent PRB2015866 |
Handshake fails when it fails to load an in-progress conversation | The same error impacts async tool execution intermittently. |
Expected behavior: It should load the chat client successfully with a new or older conversation. Actual behavior: It keeps loading and throws an error. |
|
Virtual Agent PRB2017392 |
Add topic, agent execution to the sys_cs_now_ assist_execution table for NextWave | When a topic/agent is run, the sys_cs_now_ assist_execution doesn't populate. | |
|
Virtual Agent PRB2017869 |
A custom navigation URL isn't working | Users expect that custom URL mappings under sys_cs_portal_url_ mapping_list should only impact the portal/mobile device for which it was configured. Also, pages opened on Mobile NextWave should be read as iOS/Android, not mweb. However, custom URL mapping configured for Mobile impacts Portals or vice versa, and pages opened on Mobile NextWave are read as mweb. | |
|
Virtual Agent PRB2018098 |
AI agents incorrect are displayed on the Virtual Agent's topics list | On Virtual Agent, users see AI Agent in the 'View All Topics' section under the 'Others' category. But none of those agents are marked to be visible on that section. |
See that multiple AI Agents are visible there. |
|
Virtual Agent PRB2018878 |
Employeeslate gets a 404 error for promoted-skills |
Navigate to Employeeslate's home. Observe the 404 error. |
|
|
Virtual Agent PRB2019099 |
Starting '{0}' sys_cs_context_ profile_message isn't translated per user session language | The message should be translated using SysMessage. getMessageLang before it's sent. | |
|
Virtual Agent PRB2020252 |
The Virtual Agent goes into a loop after selecting the feedback survey | In Zurich, the Now Assist Virtual Agent in enhanced chat intermittently gets stuck in a loop selecting the feedback survey topic. |
Observe that after the fallback is triggered, a form link is provided and a feedback message is triggered. After the feedback message is triggered, the Virtual Agent continues to return the same feedback message as the response. |
|
Virtual Agent PRB2022716 |
NextWave Premium Chat doesn't work for external users (snc_external) on CSM portal | The console error '403 FORBIDDEN' appears on ais_auth_token_refresh API. The external user can't use the chat experience. | |
|
Virtual Agent PRB2024076 |
Pickers aren't honoring pre-selected options | This works in the web version and is considered a feature gap. |
Expected behavior: The pre-selected options defined in the topic should be presented to the user as selected. Actual behavior: An empty picker is presented with nothing selected. |
|
Virtual Agent PRB2024849 |
Simplified handshake for NextWave needs fixes for session creation, channels, and context | The existing session needs to be looked up by conversation before creating a new one. Also, if the consumer account context name is provided, it needs to be stamped and associated with the consumer account when created. Finally, the channel user profile needs to be properly resolved for channels. | |
|
Virtual Agent PRB2025311 |
Add an ai_greeting type mapping in getContextProfile MessagesNoDomain to support a Premium Chat greeting message feature | The Now Assist Virtual Agent (VA) admin UI saves static AI greeting messages as sys_cs_context_profile_message records with type=ai_greeting. For these to load correctly, getContextProfile MessagesNoDomain in NowAssistIn VAAdmin ConsoleUtil needs an explicit branch mapping ai_greeting → aiGreetingMessage. Without this Glide-services change, the greeting message isn't populated for multi-domain instances when the feature ships. |
Observe that the custom greeting message isn't populated even though the message was saved earlier. |
|
Virtual Agent PRB2025956 |
Resolved issues after introducing four tables for Virtual Agent (VA) analytics | The search-related analytics can be written to the four tables instead of sys_ci_analytics as event entries. |
Observe that all the expected entries are in the new tables and view. |
|
Virtual Agent PRB2026053 |
sys_cs_context_profile_topics should be sent to the offGlide cache for Authorizing Official (AO) to read | ||
|
Virtual Agent PRB2026723 |
In OGChannels, there should be a picker search update | ||
|
Virtual Agent PRB2026804 |
getBrandingConfig() doesn't provide the correct response in NextWave | api/sn_nowassist_va /og_branding_configs/ {deploymentId} doesn't provide the correct response for branding configuration. It's missing a value field and the type is null for the first item. | |
|
Virtual Agent PRB2028137 |
Glide-cs-test failures in Australia | ||
|
Virtual Agent PRB2029447 |
Knowledge article links are broken in the sources citation when the article has an attachment | There is an issue with the link formation in the source citations for the KB article if there is an attachment. The link generated by Now Assist uses the sys_id of the PDF attachment instead of the KB article sys_id in the URL. | |
|
Virtual Agent PRB2030245 |
External users can't upload files | There's an HTTP 422 error and the file fails to upload. | |
|
Virtual Agent PRB2031950 |
AI-user fetch issue | The conversation user for the ZTSD flow is AI L1 Service Desk Specialist, which is the identity type ai_agent. The cache configuration get_user|table:{table} |field:{field}| value:{value} explicitly ignores users of type 'ai_agent'. |
Perform a cache fetch call for the cache key 'get_user|table:{table}|field:{field}|value:{value}' for any user of the identity type 'ai_agent'. See that it doesn't return the User field value. |
|
Virtual Agent PRB2032108 |
Glide-side changes for the NextWave release | This is a product update. | |
|
Virtual Agent Web Client PRB1993741 |
When live_agent_only is set to true, the agent chat triggers the greetings topic instead of going to the live agent | The /esc portal agent chat is configured to only trigger the live agent. However, when the user selects the 'Virtual Agent' icon, it triggers the greetings topic and doesn't go to the live agent. When the user ends the first conversation and creates another conversation, it then goes straight to the live agent. The issue only occurs the first time the user selects the 'Virtual Agent' icon in the session. It also only happens for Now Assist virtual agent sessions. |
Expected behavior: It triggers the live agent support topic. Actual behavior: It triggers the greetings topic. However, if you end the conversation and create a conversation, it goes straight to the live agent. |
|
Virtual Agent Web Client PRB2021136 |
Selecting the Stop button during synthesized results streaming causes an error | This issue occurs when the Stop button is selected in the small time interval between the receipt of the last chunk and the full synthesized response. |
Observe that there's an error. |
|
Virtual Agent Web Client PRB2033755 |
SEARCH_FALLBACK_EVENT is missing in sys_ci_analytics | SEARCH_FALLBACK_EVENT records are no longer created in sys_ci_analytics in Australia. |
|
|
Visibility Content PRB2008571 |
Sybase Discovery failed due to an issue in the step 8 condition, causing instances to be created in the wrong class | The Sybase Discovery pattern fails during execution, which results in database instances created in the parent table instead of the expected Sybase-specific class. Even after retrieving the instance name in step 7, the Sybase database pattern is failing in step 8. |
Refer to the listed KB article for details. |
|
Visual Task Boards PRB1994303 |
In a Visual Task Board (VTB), the 'Select lane' menu displays lane values from all the boards available irrespective of the board selected to move | ||
|
Window Manager PRB2019525 |
When the Now Assist panel is activated, the left side navigation is hidden and the margin remains applied, leaving an empty space | ||
|
Word Document APIs PRB1973625 |
Support unzipped font size up to 20 MB in Word Doc API | The property com.snc.word_doc_api .unzip_word_size_limit_mb supports only up to 10 MB file size. This is an enhancement request to support up to 20 MB. | |
|
Work Order Management PRB2015160 |
'Sort by distance' is degraded in Australia | The 'Sort by distance' operation in the FSM Dispatcher Workspace is significantly slower in Australia than Zurich. The transaction response time increased from 2.2 seconds to 8.9 seconds — 6.5 seconds slower. |
|
|
Work Order Management PRB2017308 |
Flat table records aren't invalidated when location attributes are inserted to Workforce Operations (WFO) events | In Australia, when a location attribute (sn_shift_planning _sched_attr) record was inserted into or deleted from a WFO event, the related schedule flat-table records weren't invalidated. As a result, outdated event entries continued to exist on the agent's flat table instead of being re-inserted with the updated sn_shift_planning_ sched_attr sys_id. The issue was present in the 'Update schedule flat table' business rule in the Field Service Management (com.snc.work_management) plugin. |
See the outdated events record still exist for the agent. When sn_shift_planning_sched_attr record is inserted or deleted, related flat table records should also be invalidated as they have to be inserted with an updated sn_shift_planning_sched_attr sysID into the table. |
|
Work Order Management PRB2023961 |
The switch 'Enable/disable association of territory resources with demand channels' can be turned on even when FSM shift scheduling is turned off |
Expected behavior: Enabling/disabling the association of territory resources with demand channels can't be turned on unless the 'Enable FSM shift scheduling' toggle is enabled. Actual behavior: The toggle 'Enable/disable association of territory resources with demand channels' can be set to enabled without setting 'Shift Scheduling' to true. |
|
|
Work Order Management PRB2026498 |
Work order tasks (WOT) are unassigned after flexible breaks are updated by Schedule Optimization (SO) | When a flexible break is optimized by the SO engine, it inserts/updates records in the sn_shift_planning_agent_schedule table to update the original break start and end time. This operation is triggering the business rule 'Re-assignment on shift deletion', which causes all of the tasks in the shift to be unassigned, even if they don't overlap with the break event. |
Observe that the tasks are assigned by SO, but then immediately unassigned after the flexible breaks are updated. |
|
Zero Copy Connectors (Glide) PRB2026100 |
There's a reverse tunnel solution for Trino private connectivity | This is a product update. | |
|
Zing Text Indexing and Search Engine PRB2018016 |
The 'TS Index Stats' job shouldn't check a table that's not indexed | The 'TS Index Stats' job is pulling 45 million records from syslog and caused an out of memory error on the node. |
Expected behavior: It shouldn't load all records for the table. Actual behavior: There's a warning for syslog large table: 'Table handling an extremely large result set'. |
Fixes included
Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.