How to Flush Cache in ServiceNow for Optimal Performance
- ericpark68
- Mar 20
- 2 min read
Updated: Mar 29
Cache management in ServiceNow is vital for maintaining optimal system performance and ensuring that recent configuration changes take effect immediately. This article will clearly explain the process of flushing cache, highlight common scenarios requiring cache flushing, and provide safe practices to avoid performance impacts.
Understanding Cache Flushing in ServiceNow
ServiceNow uses caching to enhance system speed by temporarily storing data such as UI layouts, scripts, and system properties. However, outdated cached information can lead to issues like UI inconsistencies, delayed updates, or unexpected behaviors.
Why Do You Need to Flush Cache?
Flushing cache removes outdated information, ensuring the latest configurations and updates take immediate effect. Here are key reasons why flushing the cache is important:
Reflecting Configuration Changes: Changes in form layouts, UI scripts, or system properties might not appear immediately if cached information isn't cleared.
Troubleshooting Issues: Flushing the cache is helpful when troubleshooting strange behaviors or discrepancies, confirming whether the issue stems from cached data.
When Should You Flush Cache?
Consider flushing the cache in the following situations:
After installing update sets or significant system changes.
After modifying UI layouts or properties that don’t seem to be updating correctly.
If ServiceNow behaves unexpectedly even after correct configurations.
Important: Avoid frequent cache flushing in production environments during peak hours, as it can temporarily degrade system performance due to the rebuilding of cached data.
How to Flush Cache in ServiceNow (Step-by-Step)
Follow these easy steps to flush the cache in your ServiceNow instance:
Navigate to Cache Flush:
Type cache.do in the Application Navigator search bar and hit Enter.
Alternatively, append /cache.do directly to your instance URL (e.g., https://your-instance.service-now.com/cache.do).
Flush Cache:
Once accessed, ServiceNow immediately clears the cache across all nodes, ensuring system-wide consistency.
Completion:
The cache flushing process typically completes in a few moments. There's no explicit completion notification, but once the page reloads, the cache flush is finished.
Practical Example:
Imagine you've updated a UI policy or a form layout, but users still see the old configuration. Flushing cache via cache.do ensures these UI changes become immediately visible to all users.
Alternative Solutions and Tips:
Property Changes: Changing a property in sys_properties automatically flushes the cache unless the "Ignore Cache" checkbox is enabled. Check this option carefully to manage cache behaviors.
Creating Quick Access to Properties: If you regularly manage properties, consider creating a custom module linked to sys_properties for quicker navigation.
Conclusion
Cache flushing in ServiceNow is a straightforward yet crucial maintenance activity. By knowing when and how to clear cache effectively, you can avoid unnecessary troubleshooting efforts and enhance overall system performance.
Actionable Next Steps:
Familiarize yourself with cache flushing by practicing on a non-production instance.
Plan cache flushing activities during off-peak hours to minimize disruption.
Regularly inform your team about the implications and best practices for cache management to maintain smooth operational performance.
