Thanks heaps for chasing that up for me Eric
On Dec 12, 5:40 am, AdWords API Advisor
wrote:
> Hi Fred,
>
> Currently all UNEXPECTED_INTERNAL_API_ERRORs are classified as server
> side errors, even if the root cause was bad user input.
>
> Best,
> - Eric
>
> On Dec 2, 12:14 pm, AdWords API Advisor
Hi Fred,
Currently all UNEXPECTED_INTERNAL_API_ERRORs are classified as server
side errors, even if the root cause was bad user input.
Best,
- Eric
On Dec 2, 12:14 pm, AdWords API Advisor
wrote:
> Hi Fred,
>
> The inconsistent reporting of API units and operations for this error
> is another im
Hi Fred,
The inconsistent reporting of API units and operations for this error
is another important issue, and I've brought it to the attention of
the core engineering team. I will take a deeper look into how units
are charge for UNEXPECTED_INTERNAL_API_ERRORs and get back to you.
Best,
- Eric
Thanks for following this up Eric. I will make sure we account for
quota on faults to.
When you say "where the error was due to a problem on Google's
servers" does that mean whenever the error is internal error?
In the example I posted (reported as 787 quota) it was reported as an
INTERNAL_API_ERR
Hi Fred,
Thank you for the follow up information. The API units reported in
the SOAP header are billed to your account, even if the request
resulted in an error. In cases where the error was due to a problem
on Google's servers and not user input the units will not be charged
to your account.
B
I assume you want the SOAP from the delete call which had the dodgy
operations header. Unfortunately I did not save the XML last week, but
was getting that behaviour consistently on Friday (Thursday evening in
the US)
This week I am unable to reproduce this issue. When deleting keywords
with an inv
Hi Fred,
Do you have the SOAP XML request and response that shows this
behavior? The request ID would also suffice.
Best,
- Eric Koleda, AdWords API Team
On Nov 27, 12:45 am, fred wrote:
> Hello,
> While developing our client for the v2009 API I have been doing some
> error condition tests.
>