Server side script fails with error "String object would exceed maximum permitted size of 33554432" | TroubleshootingIssue Encountering server-side scripting failures with the error String object would exceed maximum permitted size of 33554432? Find information and fixes below. Steps to reproduce in /sys.scripts.dopaste the following code: var abc = "a"; try { for (i=1;i<30;i++) { gs.print("current length: " + abc.length); gs.print("current size: " + (abc.length)*2);gs.print("Attempting to increase string size to: " + (abc.length)*4);abc = abc + abc; } } catch (e) { gs.print("error: " + e); } gs.print(abc.length); CauseThe platform has a hardcoded value of 32 MB for the String object and it is not customizable via any system property.This issue has been mostly seen to happen when script includes are instantiated in a while loop. Note that the limit may be breached when other scripts invoke a ScriptableObject, for example instantiating a script include, in a while/for loop where a GlideRecord object is passed into the script include inside the while loop. The object size grows with each loop iteration because we are adding up the GlideRecord object with each loop. One way to cause this is to loop with each GlideRecord result, and then call a script include.This error will also occur if you assigned a lot of data to a new glide record object.ResolutionTo resolve this issue, make sure that what every string object defined doesn't grow beyond 32 MBs (33,554,432 Bytes) in any of the server side scripting. NOTE: Javascript uses 2 bytes per character and there is a String object limit of 33554432 bytes.