Twitter Ad Stats Jobs Timeout

analytics
api

#1

Hi,
We have been using the async Ads API to get stats for a while now.
Occassionally, our calls to GET /1/stats/jobs/accounts/:account_id endpoint to get the status of the job_id(s) we obtained by a call to POST /1/stats/jobs/accounts/:account_id immediately before.

The response obtained was having job status data as null even after retrying many times.

Could you please explain why this happens and what can be done to resolve this.


#2

Hi @vijayarjit,

Can you give us an example request and response when this actually happened? Preferably using twurl (if you’re going to create a fresh example) with the -t flag to give us more information to debug. Can you also put the steps to reproduce, including creating the job?


#3

Hi @goforbrent @vijayarjit
I get same error.
I created one job. And affter an hour with 86 times request to checking job status, but it returned ‘PROCESSING’.
Maybe server has overload?


#4

Hi @goforbrent,

Following is request and its response we are getting:

Executing GET request for GetStatsJobRequest using https://ads-api.twitter.com/1/stats/jobs/accounts/18ce53upd9x?job_ids=899516291601629186%2C899516293803458560%2C8995162831
96239872%2C899516270625869824%2C899516289491894272%2C899516302049644544%2C899516297985249280%2C899516300090761216%2C899516268897861632%2C899516287382155264%2C899516274899693568%2C89
9516304159379456%2C899516279027052544%2C899516295829434369%2C899516285284995073%2C899516277152206848%2C899516264342835200%2C899516281631645696%2C899516266553131008%2C899516272718864
385 {} null {}

and for all these request we are getting:

“status”:“PROCESSING”

event after trying for more than 200 seconds.

Thanks
Arjit


#5

Hi @vijayarjit,

Due to increased latency with the async analytics endpoint POST stats/jobs/accounts/:account_id, there has been a drop in success rate starting at 2017-08-19 05:45 UTC, we are currently actively investigating the root cause of the issue.

In case of any issues with async jobs stuck in PROCESSING state, the recommended path is to use the DELETE stats/jobs/accounts/:account_id/:job_id endpoint and re-try once the issue is resolved.

Thank you


#6

Hi @goforbrent,
Any update on this issue.

Thanks
Arjit


#7

Hi @vijayarjit,

Yes these issues are resolved. If they reoccur or we have future updates, please reference the announcement here.

Thanks!


#8

@goforbrent Hi,I now receive Error 503 Connection timed out when I get stats