+1 on this issue. Trying to capture SOAP logs, but like the UNKNOWN_ERROR
issue last week, it is intermittent and hard to reproduce.
On Monday, September 26, 2016 at 1:33:07 PM UTC-5, AdWordsApiUser wrote:
>
> It appears that reporting calls are getting stuck for some adwords
> accounts, while
Done.
Here's the tricky part: the log files aren't generated when this failure
occurs. I have attached the log files of a successful request/response,
which occured immediately after one of the exceptions was thrown. Again, it
seemed totally random, but I only had to try the request about 5
Nadine - thank you so much for your efforts in resolving this issue. My
team and my clients thank you!
On Monday, September 19, 2016 at 8:26:53 PM UTC-5, Nadine Sundquist
(AdWords API Team) wrote:
>
> Greetings AdWordsians,
>
> We found the root cause. You should no longer be seeing this issue.
We are also seeing the CustomerError.UNKNOWN problem, which is beginning to
occur very frequently on our reporting software. In almost every case
re-sending the exact same request results in a successful response.
On Friday, September 16, 2016 at 10:37:06 AM UTC-5, Anthony Madrigal wrote:
> Hi
Sent. Can you confirm you received?
Also I have noticed there is a similar issue in the interface. When I go to
the campaign level I can see all extensions, but they all disappear from
the view when I add AdGroup or Campaign columns, even if there are
extensions associated with AdGroups in the
While I am successfully able to query any other AdWords service for
existing entities, I seem to have hit a wall retrieving entities from the
AdGroupExtensionSettingService (v201607). Here is my function.
public function _getAdGroupExtensionSettings(\AdGroupExtensionSettingService
I am looking for some guidance on how to handle a somewhat complicated
problem on our end which hinges on the design of our application as well as
the token limits enforced by Google API: namely the limit of 25 (50?)
tokens "per user, per client".
We basically have a multi-tenant application
