Hello,
I made a copy of your script and tested it on my end using both new script experience and legacy version. Upon executing the said script using the new script experience version, I was able to reproduce the same issue or error on my end. While upon trying to execute the said script using the legacy version(by toggling off the new script experience button) I wasn't able to encounter the said error and it works perfectly fine on my end.
I took a closer look at your script then I observed that you haven’t migrated your script to the new script experience set up which is the main reason why you encounter that specific error upon running your script in the new script experience version.
Having said that, you may opt to continue executing your script using the legacy version but please be reminded that as per our blog post, all new scripts will default to the new scripts experience, although you can still disable it on a script by script basis if necessary. Existing scripts won't be affected until September of 2022. After that, we will migrate all scripts to the new experience. You should manually move your scripts over to the new experience before then to ensure continued functionality.
Given that you’re using a third party script which is being created and maintained by brainlabsdigital.com, I would suggest that you raise this to their support team through this link as they are more knowledgeable on the implementation of their own script. Take note that third party scripts are already outside of our expertise. Moreover, you may also provide our migration document to them in order for them to make adjustments to their script to work properly in the new script experience environment in the future.
Regards,
 |
| James Howell |
| Google Ads Scripts Team |
|
|
| |

ref:_00D1U1174p._5004Q2bmVv0:ref