Script Only check is not triggering if i click on Scan Update set.

[Mahesh Pydisett]

Hi Everyone,

I’m currently testing the out-of-the-box Script Only Check "GlideRecord usage on Client Scripts" in Instance Scan, and I’m facing an issue where the check doesn’t seem to trigger as expected.

Here’s what I did:

• I created a Client Script that uses GlideRecord, specifically to test this Script Only Check.
• I captured the script in a local update set, marked it as Completed, and then clicked on the "Scan Update Set" related link.
• However, the scan results did not include the Script Only Check "GlideRecord usage on Client Scripts" in the findings.

Interestingly, when I implemented the same logic as a Table Check and ran the scan again, the findings did include the expected result.

Could anyone help me understand why the Script Only Check isn’t triggering in the update set scan? Is there a limitation or configuration I might be missing?

Thanks in advance!

[GlideFather]

Hi @Mahesh Pydisett,

please share some of your configurations to get an idea 

[Ankur Bawiskar]

@Mahesh Pydisett 

you will have to check the configuration for the Update set scan.

If my response helped please mark it correct and close the thread so that it benefits future readers.