Error: no more values at Og.next (adsmanagerapp_compiled:2010:13)

[Luuk]

Hi,

I'm having trouble with a script and I have reported this issue before, but after some digging (please have a look in this ticket) it appears that the previous ticket for this issue has been deleted for some reason. The original link was this: https://groups.google.com/g/adwords-scripts/c/-0J83xoCkTo. For some reason all posts in that topic have been deleted.

The script I'm having issues with is a copy from a script that is currently running fine in the client manager account. I'm testing it in my own developer MCC, so please keep this in mind. The test script is a copy of the actual script, where in the copy I have commented out some functions to debug the issues that showed op. Besides that, everything is set up in the same way. If you are able to request a delay for the automatic transition to the new ads script environment, I'd like to ask you to request that delay for the actual script, which is in the MCC with id: 293-243-6676. The script is named "Auto update locaties + campagnes".

The script for testing and debugging is in my personal developer MCC, which has the ID 374-324-0135. The script in here is named "Testing for new script environment - No more values issue".

Basically the script reads a spreadsheet and checks if it needs to update campaign locations if the checkbox in the spreadsheet is check. It first removes all campaign locations and then adds back the ones which are checked in the spreadsheet. This works perfectly fine in the old script environment, but in the new environment a bug shows up. The error is:

Error: No more values 

at Og.next (adsmanagerapp_compiled:2010:13)

This bug looks like an internal Google Ads script bug, not related to my script but related to the way the scripts are parsed and executed on the server side.

Feel free to make changes in the developer MCC ( so the one with ID 374-324-0135), but please don't make changes to the live version in the other MCC.

Best,

Luuk

[Luuk]

I'm just writing another comment to make sure this post has been forwarded to the support query, since it seems that that issue is still going on :)

Op maandag 6 februari 2023 om 23:36:51 UTC+1 schreef Luuk:

[Google Ads Scripts Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-scripts/c/MVQ5WMj4hp4) from the forum as it wasn't routed to our support queue.

Regards,
Yasmin
Google Ads Scripts Team

[Google Ads Scripts Forum]

Hi Luuk,

This is Yasmin from the Google Ads Scripts Team. Please excuse us for only getting back now as your messages failed to be routed to our support queue.

Please do note that we are unable to make requests to issue delays on specific scripts as well as users with regard to the auto-migration in Google Ads Scripts.

Upon checking the script in the account, it appears that the it is trying to access account IDs which the MCC account the script is implemented in is not managed by. The MCC account 374-324-0135 is a Test account which does not have access to any sub or child accounts. With this, I would recommend to test this in Preview Mode in your live MCC account with child accounts being managed. When scripts are executed in preview mode, they make no changes to the actual campaign data. Instead, script execution shows the changes that would have been made had the script been executing.

Let us know how it goes.

Best regards,

Yasmin
Google Ads Scripts Team

[Luuk]

Hi Yasmin,

Thanks for getting back to me. The test account with ID 374-324-0135 does actually have access to multiple sub and child accounts, but they are all deactivated because of these being test accounts and not having any spend in them. The automatic procedure deactivates accounts when there is no spent in them for at least 15 months, so that's why all sub accounts are paused. However, running scripts and accessing these accounts via the scripts works just fine.

Here you can see the accounts the development MCC has access to: https://imgur.com/a/r89eeAo. The script named "Testing for new script environment - No more values issue" tries to access the accounts 244-742-0499 and 766-663-9445 which are both accessible via the MCC as you can see in the screenshot on imgur. The other account IDs on lines 9 to 13 are commented out. These are the account IDs of all accounts that are used in the live script. The 2 account IDs that aren't commented out are used in this testing script / environment.

Please let me know if you still have issues finding the accounts the script is trying to access.

Best,

Luuk

Op woensdag 15 februari 2023 om 12:07:21 UTC+1 schreef Google Ads Scripts Forum:

[Google Ads Scripts Forum Advisor]

Hi Luuk,

 

Thanks for providing more context to this as well as for confirming that those accounts are paused or deactivated. Kindly note that, by default, only ACTIVE accounts are retrieved by the selector in the new script experience unless you explicitly include the status of the account in the .withCondition method. With this, I would recommend testing the script with active child accounts.

 

Let us know how it goes on your end.

 

Best regards,

 

 

Yasmin Gabrielle Google Ads Scripts Team

ref:_00D1U1174p._5004Q2j0PIr:ref

[Luuk]

Hi,

In the ManagedAccountSelector I don't see an option to explicitly include the status with .withCondition. I'm looking at this page: https://developers.google.com/google-ads/scripts/docs/reference/adsmanagerapp/adsmanagerapp_managedaccountselector#withCondition_1. The the only columns available for filtering are currency_code, time_zone, applied_labels and descriptive_name. Is there an undocumented field that allows including accounts with a specific status (in this case deactivated accounts?)

Furthermore, trying to filter on the descriptive name throws an error as well.

    var account = AdsManagerApp.accounts().withCondition("customer_client.descriptive_name CONTAINS_IGNORE_CASE 'fiets' ").get().next();

Results in this error:

InputError: Invalid condition "customer_client.descriptive_name CONTAINS_IGNORE_CASE fi" (translated from "customer_client.descriptive_name CONTAINS_IGNORE_CASE fi "): unrecognized operator "CONTAINS_IGNORE_CASE" at Hh.withCondition (adsmanagerapp_compiled:2443:15) at main (Code:6:44) at Object.<anonymous> (adsapp_compiled:19004:54)

Best,

Luuk

Op donderdag 16 februari 2023 om 09:35:28 UTC+1 schreef Google Ads Scripts Forum Advisor:

[Google Ads Scripts Forum Advisor]

Hi Luuk,

 

Kindly note that the new Google Ads Scripts experience has a completely rewritten backend to take advantage of new features in the Google Ads API. It's infrastructure is based on the said API. With this, please refer to the Google Ads API resources documentation to check the filterable resource fields. You may navigate specifically to the customer_client report and try to use the field customer_client.status to filter the accounts.

 

As an aside, I'd also like to suggest you check this link for more information on how to query in the Google Ads API as it states these operators in the AdWords API WHERE clauses are not supported in the Google Ads API:

• CONTAINS
• CONTAINS_IGNORE_CASE
• DOES_NOT_CONTAIN
• DOES_NOT_CONTAIN_IGNORE_CASE

 

Let us know if you have any further clarifications.

[Luuk]

Hi Yasmin,

Thanks for pointing me in the right direction. The Ads script documentation itself doesn't mention the ability to filter on the customer_client.status (the ads API does, but ads scripts doesn't). That's quite confusing.

However, I modified the script to look for the account IDs in accounts with all possible statusses by using the following condition: 

        .withCondition("customer_client.status IN ('CANCELED','CLOSED','ENABLED','SUSPENDED','UNKNOWN')")

Now the script runs but it hangs after a few seconds and doesn't output any error information or log statements. The script name is "Testing for new script environment - No more values issue" and it is in the account 374-324-0135.

Would you be able to look into that?

Regards,

Luuk

Op vrijdag 17 februari 2023 om 10:56:48 UTC+1 schreef Google Ads Scripts Forum Advisor:

[Google Ads Scripts Forum Advisor]

Hi Luuk,

 

I'd like to reiterate that the new Google Ads Scripts experience has a completely rewritten backend to take advantage of new features in the Google Ads API. It's infrastructure is based on the said API. With this, I would suggest to refer to the Google Ads API resources documentation to check the filterable resource fields.

 

I checked the script you implemented and observed that you are not following the best practices as per our documentation. It appears that you are looping through two account IDs and then applying the condition to it which may have caused the issue. I would recommend to follow the sample implementation as per our documentation. You may follow this simple script I've created:

var accountSelector = AdsManagerApp 
    .accounts() 
    .withCondition("customer_client.status IN ('CANCELED','CLOSED','ENABLED','SUSPENDED','UNKNOWN')") 
    ;  

    var accountIterator = accountSelector.get(); 
    while (accountIterator.hasNext()) { 
        var account = accountIterator.next(); 
        console.log(account.getName()) 
    }

 

Let us know if you still encounter any issues on your end.

[Luuk]

Hi Yasmin,

I have implemented this way of iterating over the accounts, but it still hangs. I have only implemented it in the updateLocations functions, since that's the only real function being executed. The other ones are commented out so there was no need to change them yet. The script still hangs on running. It outputs a few log lines, but it doesn't finish.

Best

Luuk

Op vrijdag 17 februari 2023 om 14:17:13 UTC+1 schreef Google Ads Scripts Forum Advisor:

[Google Ads Scripts Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-scripts/c/MVQ5WMj4hp4) from the forum as it wasn't routed to our support queue.

Regards,
Yasmin
Google Ads Scripts Team

[Google Ads Scripts Forum Advisor]

Hi Luuk,

 

We were able to reproduce the issue on our end, and will be raising this to our wider team for further investigation. We'll be getting back with relevant information once we hear any from them soon.

 

Your patience is greatly appreciated.

 

Best regards,

 

Google Ads Scripts Team

ref:_00D1U1174p._5004Q2j0PIr:ref

[Luuk]

Hi,

I was wondering if you have any updates on this issue?

Best,

Luuk

Op dinsdag 7 maart 2023 om 13:17:20 UTC+1 schreef Google Ads Scripts Forum Advisor:

[Google Ads Scripts Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-scripts/c/MVQ5WMj4hp4) from the forum as it wasn't routed to our support queue.

Regards,

Google Ads Scripts Team

[Google Ads Scripts Forum Advisor]

Hello Luuk,

 

Your patience is greatly appreciated, however, I'm afraid we do not have any updates to share with you yet. I'll follow-up on the issue and we'll get back the soonest we do receive a response with relevant information.

[Luuk]

Hi there,

This ticket and the original ticket (which was deleted, but the original link is: https://groups.google.com/g/adwords-scripts/c/-0J83xoCkTo) have been open for about a year now. I'd appreciate to get an update on the status.

Op vrijdag 14 april 2023 om 14:20:13 UTC+2 schreef Google Ads Scripts Forum Advisor:

[Google Ads Scripts Forum]

Reposting the last inquiry (https://groups.google.com/g/adwords-scripts/c/MVQ5WMj4hp4) from the forum as it wasn't routed to our support queue.

Regards,
Google Ads Scripts Team

[Google Ads Scripts Forum Advisor]

Hi Luuk,

 

I'm afraid we do not have any updates to share yet. Allow me to follow up and our team will get back soon as we hear anything from our wider team.

 

This message is in relation to case "ref:_00D1U1174p._5004Q2j0PIr:ref"

Thanks,

 

Google Ads Scripts Team