Hello!
We using Java v13 API to make cross-client reports. Logic to plan report is
such:
1. Check if there is room for report (15 queue limit)
2. If ok - validate it
3. If ok - plan it, store Job ID.
4. For each not downloaded reports, check their statuses; if status OK -
download it.
It works fine for hundreds of accounts (partially there is cross-client
reports, while partially not).
But sometimes, Report Service just don't believe our credential information.
Example:
<ns1:code>5</ns1:code>
<ns1:message>Either this object does not exist, or this user does not
have permission to access it.</ns1:message>
<ns1:trigger>Job ID: 1856723944</ns1:trigger>
It happens not rarely, and it's have global effect, if we have such
problems, then it happened not with one account, but with many.
If we plan, plan, plan new feports, eventually some report is done and we
can download it.
Do you need any additional info?
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords 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
