Client Script onChange is not triggering at all

[colin-lucwe]

Hi everyone,

I’m currently facing an issue with a Client Script onChange script that is not being executed at all.

The strange thing is that it is not a logic issue inside the script — the script does not seem to trigger in the first place. I already added logging statements at the very beginning of the Client Script, but nothing appears in the console/logs when I change the field value.

Has anyone experienced a similar issue or has an idea what could prevent an onChange Client Script from firing?

Things I already checked:

The Client Script is active
The field name is correct
The script type is set to onChange
I tested with simple log statements at the first line
The field value is definitely changing
Are there any less obvious reasons why an onChange Client Script would not trigger at all? For example, any configuration settings, UI policies, field types, client conditions, or other dependencies that could block it?

Any hints or troubleshooting tips would be highly appreciated. Thanks!

[colin-lucwe]

[Juhi Poddar]

Hi @colin-lucwe 

Could you please share a screenshot of the Client Script configuration along with the script itself? That would help us review the setup and better investigate why the onChange Client Script isn't being triggered.

Thank You!

Juhi Poddar

[colin-lucwe]

It does only trigger the console log while loading

[Tanushree Maiti]

Hi @colin-lucwe 

Share the screen shot of your client script. Specifically with Trigger condition and script.

[yashkamde]

did you check for any config, ui policy or client policy blocking the same field to set ??

check in audit history if the field value is being changed..

If my response helped mark as helpful and accept the solution.