ServiceNow Cleanup/cache clear

[Vaibhav Ramteke]

Hello,

I just found that via cache.do we do the cleanup is it possible.
what is the advantage and disadvantage.

Thank you

[Tanushree Maiti]

Hi @Vaibhav Ramteke 

Best Practice for using cache.do are

1. In Prod, you run it after taking proper approval and  in maintenance hour.

2. Before running it , Please test your stuff after clearing your browser cache. You can open the browser in Incognito/InPrivate Window.

Advantages:

1. Immediately reflects background updates such as UI layout modifications, form updates, Service Portal widget changes, or updated system properties.
2. Helps eliminate corrupted cached data and resolve unusual UI behavior during critical P1 incidents.
3. Clears stale server-side memory that may be causing inconsistent system behavior or data discrepancies.

Disadvantages:

1. Clearing the full system cache forces the ServiceNow instance to retrieve data directly from the database instead of using cached memory. As the cache rebuilds, users may experience slower page loads and delayed transactions.
   Note: Running /cache.do in Production without proper approval is generally not recommended.
2. Executing /cache.do on a Production instance during peak business hours can negatively impact the user experience. It is best performed during scheduled maintenance windows.

[Vaibhav Ramteke]

what the best solution to do this cleanup activity as per your suggestion

[Tanushree Maiti]

First clean browser cache, if you are getting no difference in result, use cache.do (In non- prod)

In prod , make sure you are taking approval else it can create an escalation ( We did face once long back) and run in in business off hour /in maintenance time.

[Vaibhav Ramteke]

how to know the cache complete or not where it is check