Aman Kumar S
Kilo Patron

Hi @kedar_sirshikar 

Did you try putting in alerts explicitly to validate if onload is working on not.

If still it fails, validate the order has been put correctly, its active or not.

Best Regards
Aman Kumar

vermaamit16
Kilo Patron

Hi @kedar_sirshikar 

 

Any specific reason to have 3 On-Load client scripts ? Mostly, a single On-Load script serves the purpose.

 

Thanks & Regards

Amit Verma

Thanks and Regards
Amit Verma

Not applicable

Hi @kedar_sirshikar ,

 

Put the alert or addInfoMessage to see which is not executed. 

Do your scripts run on cmdb_ci table, if yes then please tick Inherited checkbox to apply to extended tables.

Maddysunil
Kilo Sage

@kedar_sirshikar 

Few things to check:

 

1. Confirm the execution order of your client scripts. In some cases, the order in which client scripts are executed might impact their behavior. Ensure that the desired script is not being overridden or skipped due to the execution order.

 

2. Review the logic in the client script that is not consistently executing. Ensure there are no conditions or errors that might cause it to skip execution.

 

3. Clear the browser cache and try again. Cached scripts might not be updated, leading to inconsistent behavior.

 

4. If your client script relies on script includes, ensure that the script includes are being loaded correctly and are available at the time of execution.

 

5. Review the ServiceNow instance logs for any errors or warnings related to client script execution. This can be found in the "System Logs" module.

 

Kindly mark helpful/accepted if it helps you.

Clear the browser cache is helping most of the times.