ServiceNow Cache will not update

[Marc_007]

Hello all,

     I made a change in my script for a word misspelled eligable and corrected the spelling to eligible. We already had clone down which I thought would have fix this with out using cache.do Will I need to invoke the cache.do in all instances? Please see attachments below.

[Robbie · Accepted solution]

Hi @Marc_007,

This has me thinking - "alert()" is a method of the window object in the underlying JavaScript. Typically an alert message defined in a client script would not require a cache.do to reflect a change. Is this the only place this message and string is defined?

I have not seen this require clearing the cache.

For a little further understanding of cache.do and it's affects, I recall a good article written on the community from @Shahed Shah1 - check it out. (See below).

To confirm my though process, can you change the alert message to something completly different to see if the change is immediately reflected. This will tell you straight away if it is cache related (which I don't think it is) vs being defined and called somewhere else.

https://www.servicenow.com/community/now-platform-blog/you-don-t-always-need-to-clear-the-cache/ba-p...

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

[Marc_007]

Thanks for clearing up about the cache.do. I looked further and there was one more location that had the miss spelling. Tested and you was correct. Thanks for the help. You all have a great day!!

[Robbie]

Hi @Marc_007,

No worries. We've all been there. It's amazing what a 4-eye or sense check can do.

Glad we found the solution. Happy coding ; )

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

[Kieran Anson]

Hi,

Just to clarify. You've moved your updated code from a dev environment up to a higher environment (prod?) and still seeing the issue? Have you looked at the script in prod to check the script record has the new spelling?

As an FYI - If this is a client/catalog client script, you should be using getMessage("message_key") and storing your message in sys_ui_message table