- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2023 11:45 PM
Hi, all.
We're labeled modifications were made in the UAT environment and in the production environment after the version upgrade.
In the UAT environment, the label was reflected normally, but in the production environment, the label was left as it was before the change.
When the cache.do command was executed, the label was reflected normally in the production environment.
Based on this, I would like to know the following.
1. when to use cache.do (when is it desirable to use cache.do?)
2. What are the negative effects of using cache.do?
3. is there any other way to reflect labels properly?
Please advise.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2023 01:33 AM
Hi @RyoyaFukuda ,
The "cache.do" command in ServiceNow is used to refresh the cache of a specific record in the system. This can be useful in situations where the information displayed on a record form is not up-to-date and needs to be refreshed. It is recommended to use "cache.do" when a record has been updated, but the changes are not being reflected on the form.
The negative effects of using "cache.do" can occur when it is used excessively or inappropriately. This can lead to increased server load, decreased system performance, and potential data integrity issues. For example, if multiple users are constantly refreshing the cache for the same record simultaneously, it could cause system instability or even data corruption. Therefore, it is important to use "cache.do" judiciously and only when necessary.
Not aware about others way. But you can try to clear browser cache. Or else Cache.do is another option
- No, running the "cache.do" command in ServiceNow while a user is logged in will not log them out.
Kindly mark correct and helpful if applicable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2023 01:06 AM
There was one more thing.
If you run cache.do while a user is logged in, will they be logged out?
Please advise.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-14-2024 05:15 AM
No, session will not logged-out
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2023 01:33 AM
Hi @RyoyaFukuda ,
The "cache.do" command in ServiceNow is used to refresh the cache of a specific record in the system. This can be useful in situations where the information displayed on a record form is not up-to-date and needs to be refreshed. It is recommended to use "cache.do" when a record has been updated, but the changes are not being reflected on the form.
The negative effects of using "cache.do" can occur when it is used excessively or inappropriately. This can lead to increased server load, decreased system performance, and potential data integrity issues. For example, if multiple users are constantly refreshing the cache for the same record simultaneously, it could cause system instability or even data corruption. Therefore, it is important to use "cache.do" judiciously and only when necessary.
Not aware about others way. But you can try to clear browser cache. Or else Cache.do is another option
- No, running the "cache.do" command in ServiceNow while a user is logged in will not log them out.
Kindly mark correct and helpful if applicable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2025 01:14 PM
If multiple UI policies are written with run order of 100 and execute in a certain way in Non-Prod but run in a different way in Production after a cache.do. That seems to be the fault of not ordering priority and leaving it up to random not the cache.do correct? Because the cache.do can sometimes find flaws or inconsistency in the system or code does not mean that is to blame?
