arch 9, 2017 at 12:37:27 AM UTC-5, Stefan Kleine Stegemann
> wrote:
>>
>>
>> Hi,
>>
>> the problem remains and "increases" as far as we can see. This morning
>> (german time), we have 22 jobs stuck in ACTIVE for around two to three
>> hours
his thread, it makes no sense
to re-submit a job if it does not get through in the early morning.
Regards,
Stefan
Am Mittwoch, 8. März 2017 20:18:19 UTC+1 schrieb Stefan Kleine Stegemann:
>
> Hi Nadine,
>
> over the past weeks, batch jobs have been stable and also much faster than
> befo
Hi Nadine,
over the past weeks, batch jobs have been stable and also much faster than
before. However, starting yesterday, we have some
stuck batch jobs again. This is annoying, to be honest. It creates a lot of
effort on our side. Do we have to expect that to
happen on a regular base?
Here
Has this anything to do with this?
https://twitter.com/search?q=google%20oauth=typd
Am Freitag, 24. Februar 2017 08:20:00 UTC+1 schrieb Stefan Kleine Stegemann:
>
>
> As additional information, it seems that the tokens are working
> "sometimes". For a few accounts, I crea
ieb Stefan Kleine Stegemann:
>
>
> Hi,
>
> we're also experiencing this issue for some hours now. For around 50
> adwords accounts connected to our system, the refresh tokens suddenly
> stopped working. We're also getting the "invalid_grant" error message. It
&g
Hi,
we're also experiencing this issue for some hours now. For around 50
adwords accounts connected to our system, the refresh tokens suddenly
stopped working. We're also getting the "invalid_grant" error message. It
will be a lot of work to re-authorize all of the affected customers, any
n't optimal, but I do want you to know that is of higher
>> priority to us. It's just really tricky trying to find a solution for what
>> you're seeing. I'll get back to you as we make more progress. Thanks again
>> for providing so much helpful information!
>>
&
schrieb Nadine Sundquist
>> (AdWords API Team):
>>>
>>> Hi Stefan,
>>>
>>> The good news is that we found where the hanging is happening, but the
>>> bad news is that we still don't have a complete fix. If the cancel
>>> continues to hang, plea
, it looks like you're doing the
> right thing by cancelling and retrying.
>
> Best,
> Nadine, AdWords API Team
>
> On Thursday, February 16, 2017 at 1:54:41 AM UTC-5, Stefan Kleine
> Stegemann wrote:
>>
>>
>> Hi Nadine,
>>
>> To update you
g into what caused this
> last spike in execution time.
>
> Cheers,
> Nadine, AdWords API Team
>
> On Wednesday, February 15, 2017 at 5:04:20 AM UTC-5, Stefan Kleine
> Stegemann wrote:
>>
>> Hi,
>>
>> sorry for hijacking this thread but since yesterday mornin
Hi,
sorry for hijacking this thread but since yesterday morning, we also
started to have significant troubles with batch job service. Jobs remained
active for a very long time. The following jobs have been started yesterday
morning, german time (see start time is noted for each job) and were
Hi,
the problem has been solved. In fact, it turned out to be a problem on our
side. Thanks very much for your support and your help, AdWords API Team!
Best,
Stefan
Am Montag, 14. November 2016 18:10:40 UTC+1 schrieb Shwetha Vastrad
(AdWords API Team):
>
> Hi Stefan,
>
> Could you provide
When downloading a product partition report, we sometimes receive duplicate
rows for a single criterion. The reports are segmented by Date and Device
and we're getting two rows for the same combination of CampaignId,
AdGroupId, CriterionId and Device. When this happens, one row usually
Hi,
just wanted to update this thread saying that the problem does not longer
exist. Thanks for solving it.
Best,
Stefan
Am Dienstag, 25. Oktober 2016 12:19:30 UTC+2 schrieb Stefan Kleine
Stegemann:
>
> Hi,
>
>
> we are experiencing problems when downloading product pa
Hi Shwetha,
thanks for the fast reply. I sent you the campaign ids via private reply.
I cannot tell whether it's related to the campaign or account, because each
campaign belongs to a separate account and our system does not "manage" any
other campaigns from these accounts.
Best,
Stefan
Am
Hi,
we are experiencing problems when downloading product partition reports for
some campaigns. We're loading these reports for large number of campaigns
without problems but three campaigns started to fail consistently this
morning (german time). We've successfully downloaded reports for
September 14, 2016 at 12:27:16 AM UTC+9, Christian wrote:
>>
>> Hi,
>>
>> we are in AWS Frankfurt as well. Could be relevant: we are use AWS'
>> managed NAT service.
>>
>> Best,
>> Christian
>>
>> On Tuesday, September 13, 2016
s,
> Josh, AdWords API Team
>
> On Tuesday, September 13, 2016 at 7:12:06 AM UTC-4, Stefan Kleine
> Stegemann wrote:
>>
>>
>> Hi Josh,
>>
>> as an additional information, our main problem seems to be the AdWords
>> management API, not the reporting
, or if region is not a factor. If you'd prefer to share that
> information only with me, you can click *Reply privately to author* on
> this message.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, September 13, 2016 at 7:12:06 AM UTC-4, Stefan Kleine
> Ste
se requests and didn't
> see any errors in terms of AdWords API handling, which suggests this may be
> an issue at a different layer on our side. I'll keep digging and let you
> know what I find.
>
> Cheers,
> Josh, AdWords API Team
>
> On Friday, September 9, 2016 at 10:31
AdWords API Team
>
> On Friday, September 9, 2016 at 10:31:58 AM UTC-4, Stefan Kleine Stegemann
> wrote:
>>
>>
>> Hi Josh,
>>
>> I sent you a private mail with some information.
>>
>> I hope that helps.
>>
>> Thanks,
>> Stefa
with that
> particular request.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, September 9, 2016 at 7:27:56 AM UTC-4, Stefan Kleine Stegemann
> wrote:
>>
>>
>> Hi Josh,
>>
>> i'm sorry but I wasn't able to find a request with a request-id in o
Hi Josh,
i'm sorry but I wasn't able to find a request with a request-id in our
logs. I inspected the soap dumps from failed requests and found none with a
request id. I found some other failed requests where the id was displayed
but these requests failed because of "normal" errors (such as
Hi Josh,
thanks for your reply. First, the situation got much worse this morning
with the number of timeouts increasing significantly. About setting the
read timeout, is there a away of doing that in pure Java without
ads.properties because we have our own "setup code" and configuration
Hi,
over the past days, we experienced an increasing number of read-timeouts
when making API calls.
The timeouts are not restricted to a specific service but we have observed
them for CampaignService,
TrafficEstimatorService, Reporting and some others . I seems that our
network is not the
Hi,
thanks for your Update, Umesh. However, so far, we did not notice any
improvement. In fact, today we get more rate limit errors than yesterday.
Best regards,
Stefan
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
Hi,
starting this morning, we're experiencing similar issues. The throughput
rates we've got from the TrafficEstimatorService were pretty stable over
the past months but today, we get a lot of RateExceededErrors (the same as
illustrated by Alexander). Waiting for 30 seconds sometimes helps
sorry, i meant that we get some rows with zero impressions when we
set includeZeroImpressions to *false*, of course.
Stefan
Am Montag, 24. August 2015 13:59:18 UTC+2 schrieb Stefan Kleine Stegemann:
Hi Josh,
today, we noticed the same behavior for keyword performance reports.
Despite
-4, Stefan Kleine Stegemann
wrote:
Hi Josh,
are there any updates on this issue so far?
Cheers,
Stefan
Am Donnerstag, 4. Juni 2015 22:13:27 UTC+2 schrieb Josh Radcliff (AdWords
API Team):
Hi Stefan,
Thanks for pointing that out -- I hadn't tried setting it to *true* so
didn't
Hi Josh,
are there any updates on this issue so far?
Cheers,
Stefan
Am Donnerstag, 4. Juni 2015 22:13:27 UTC+2 schrieb Josh Radcliff (AdWords
API Team):
Hi Stefan,
Thanks for pointing that out -- I hadn't tried setting it to *true* so
didn't notice the difference in behavior. I'll pass
*Reply privately to author *the report definition with Date
and includeZeroImpressions=false along with the campaign ID that produced
zero impression rows?
Thanks,
Anthony, AdWords API Team
--
Adference GmbH
Stefan Kleine Stegemann
Munstermannskamp 1
21335 Lüneburg
Fon 04131.677-2305
E-Mail
31 matches
Mail list logo
