Washington DC Patch 10 Hotfix 4
Summarize
Summary of Washington DC Patch 10 Hotfix 4 Release Notes
The Washington DC Patch 10 Hotfix 4, released on April 24, 2025, addresses specific issues affecting the Washington DC release. It is essential for ServiceNow customers to stay informed about these fixes to enhance their platform performance and user experience.
Show less
Key Features
- Build Information:
- Build Date: April 20, 2025
- Build Tag: glide-washingtondc-12-20-2023patch10-hotfix4-04-15-2025
- Fixed Problems:
- API Performance Issues: Slow API calls due to Table Cleaner throttling, leading to replication lag.
- Platform Analytics Filters: Search keywords not trimmed, impacting multi-select filter results on dashboards.
Key Outcomes
Customers can safely upgrade to this release from specified prior versions, ensuring they benefit from all included PRB fixes. This upgrade is crucial for maintaining optimal platform performance and addressing known bugs that disrupt functionality.
The Washington DC Patch 10 Hotfix 4 release contains fixes to these problems.
- Build information:
- Build date: 04-20-2025_2148
For more information about the release cycle, see the ServiceNow Release Cycle.
Fixed problem
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Activity Stream PRB1858894 |
Application Programming Interface (API), ServiceNow AI Platform, and GraphQL are slow due to the Table Cleaner being throttled, causing heavy replication lag |
API, ServiceNow AI Platform, and GraphQL calls are slow specifically because of the Table Cleaner on sys_activity shards. ​Using Instant Alter added an index, and as a result, all records were replicated with the load causing replication lag. When replication lag is detected, Table Cleaners are throttled, which can exacerbate the amount of data that is being replicated and cause timeouts. Timeouts are caused by the Table Cleaner running synchronously in the Activity Stream load request. |
Refer to the listed KB article for details. |
|
Platform Analytics Filters PRB1732587 |
The search keyword is not trimmed | After applying values in a multi select filter, there are no results for the applied values, and the keyword that was searched is not trimmed. This problem was observed in Vancouver and Washington DC instances. |
Expected behavior: Both applied values should be displayed and keyword is trimmed. Actual behavior: Notice that there is no result for the applied values and keyword is not trimmed. |
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.
- Washington DC Patch 10 Hotfix 3
- Washington DC Patch 9
- Washington DC Patch 8
- Washington DC Patch 7
- Washington DC Patch 6
- Washington DC Patch 5
- Washington DC Patch 4
- Washington DC Patch 3
- Washington DC Patch 2
- Washington DC Patch 1
- Washington DC security and notable fixes
- All other Washington DC fixes