@DATTA we were getting this error connected with the widespread defect that was breaking transaction forms. Strangely enough undeploying all SS1 client scripts on the form seems to be the thing that works (even though the error is on a SS2 script)