Hi Julian,

Thank you for raising your concern.

Please see my response below to the questions you've mentioned on this concern:
Does the changes take too much time to be reflected and available to be query 
from "change_status" resource?
-When the changes is already available in the Change History, then it can also 
be retrieved using change_status.

Is there something that is not working properly at Google Ads API or maybe am I 
doing something wrong? Please Let me know if you need more details about how I 
am implementing this.
-You can inspect this document to check the configuration of your API request 
for change_status. However, so that I can further investigate the issue, could 
you provide the following details?

Complete request and response logs with request ID generated on your end where 
data is being returned before the changes that you've made
Complete request and response logs with request ID generated on your end 
without data
Screenshot of logs in the Change History that you are expecting in the API 
response of change_status


If you haven't enabled the logging of the API transactions for the specific 
client library that you are using, then please refer to this guide.

2) Sometimes while I am trying to debug it (for the only case I mentioned that 
it worked for me, I mean, I got only some changes that I made) it got an 
outOfMemory error:

Exception in thread "http-nio-8080-exec-1" java.lang.OutOfMemoryError: Metaspace
-You can try the workaround provided on this document. You may just note of 
this part of the document "The timeout currently cannot be increased beyond a 
maximum value of 1 hour. If this becomes an issue, it is usually best to split 
the query up and execute the chunks in parallel; this avoids the situation 
where a long running request fails and the only way to recover is to trigger 
the request again from the start.".

You can provide the details that I am requesting via Reply privately to author.

Regards,

Ernie John Blanca Tacata
Google Ads API Team
ref:_00D1U1174p._5004Q2JByw4:ref

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/alYWb000000000000000000000000000000000000000000000QWMMD900CeRdU1E2R3GLbgDWCLwKfg%40sfdc.net.

Reply via email to