@Lea CC Thanks for responding. I assume it is an issue with a client script that we just put in place.