Massive Failed api responses

[singular_noai]

Hello,

We are experiencing massive fails across customers with response such as:

{  
   'status':'FAILED',
   'created_at':'2018-01-11T12:14:03Z',
   'placement':'PUBLISHER_NETWORK',
   'account_id':'18ce53up0w7',
   'metric_groups':[  
      'ENGAGEMENT',
      'BILLING',
      'MOBILE_CONVERSION'
   ],
   'url':None,
   'country':None,
   'start_time':'2018-01-04T00:00:00Z',
   'updated_at':'2018-01-11T13:25:07Z',
   'expires_at':None,
   'entity':'PROMOTED_TWEET',
   'platform':None,
   'id_str':'951426979659628544',
   'granularity':'DAY',
   'entity_ids':[  
      '4cn8y',
      '257bm',
      '257bl',
      '257bi',
      '257bh',
      '257bk',
      '257bj',
      '257c4',
      '257c5',
      '257c2',
      '257c3',
      '2qh1b',
      '2qg6c',
      '2qg6b',
      '2qg6w',
      '2qg70',
      '2qh1c',
      '2qg6y',
      '2qg6x',
      '2qg6z'
   ],
   'segmentation_type':'PLATFORMS',
   'id':951426979659628544,
   'end_time':'2018-01-11T00:00:00Z'
}

We have experienced this issue for the last couple of days.
The fails are not consistent over time, we are querying reports for many accounts and this happens across all of them.
Can you please take a look?

Thanks,
Noa Iarchy
SIngular

[goforbrent]

Hi @singular_noai,

Can you provide your client app ID alongside the full twurl request/response for the example above?

Example:

twurl -H ads-api.twitter.com "/2/stats/jobs/accounts/18ce54d4x5t" -X POST -d "entity=LINE_ITEM&entity_ids=8u94t&start_time=2017-05-19&end_time=2017-05-26&granularity=DAY&placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT" | jq

[singular_noai]

Hi @goforbrent,

Thanks for your response.

Per your request:
(I took a different example in order to get all details)

client id: 17337554
request:

twurl -H ads-api.twitter.com "/2/stats/jobs/accounts/18ce54lat2m" POST -d "entity=CAMPAIGN&entity_ids=9za9k,9za9l,9za9m,9za9n,9za9o,9vera,9z9n9,9verc,9verb,9vere,9verd,a75s3,a75s2,9za9x,9za9y,9za9z,9za9p,9za9q,9za9r,9za9s&start_time=2018-01-07&end_time=2018-01-13&granularity=DAY&placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT,BILLING,MOBILE_CONVERSION" | jq

response:

{u'status': u'FAILED', u'created_at': u'2018-01-14T10:42:13Z', u'placement': u'ALL_ON_TWITTER', u'account_id': u'18ce54lat2m', u'metric_groups': [u'ENGAGEMENT', u'BILLING', u'MOBILE_CONVERSION'], u'url': None, u'country': None, u'start_time': u'2018-01-06T22:00:00Z', u'updated_at': u'2018-01-14T11:47:32Z', u'expires_at': None, u'entity': u'CAMPAIGN', u'platform': None, u'id_str': u'952491033446641664', u'granularity': u'TOTAL', u'entity_ids': [u'9za9k', u'9za9l', u'9za9m', u'9za9n', u'9za9o', u'9vera', u'9z9n9', u'9verc', u'9verb', u'9vere', u'9verd', u'a75s3', u'a75s2', u'9za9x', u'9za9y', u'9za9z', u'9za9p', u'9za9q', u'9za9r', u'9za9s'], u'segmentation_type': None, u'id': 952491033446641664, u'end_time': u'2018-01-13T22:00:00Z'}```

Thanks!
Noa

[JBabichJapan]

Hi @singular_noai ,

Is the issue still persisting on your end? I took a look at the service stability and it appears to have had some elevated errors around 11th to 13th but has been very stable after that. We will take a closer look this week if it’s still a continuing problem.

Thanks,

John

[singular_noai]

Hi @JBabichJapan,

Thanks for your reply.
We are sorry to inform you we are still experiencing massive fails every day (today as well).

Adding a recent example:
client id: 2755476668
request:

twurl -H ads-api.twitter.com "/2/stats/jobs/accounts/18ce53ure0m" POST -d "entity=CAMPAIGN&entity_ids=2wxk4,2t0vy,2g8hn,2wxjo,2jhdr,1ntek,1ntem,1nqgw,1nteo,1ntes,19630,1ntet,1ntew,1ntey,2o76w,299hd,3w8ks&start_time=2018-01-08&end_time=2018-01-14&granularity=DAY&placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT,BILLING,MOBILE_CONVERSION" | jq

response:

{u'status': u'FAILED', u'created_at': u'2018-01-16T08:52:52Z', u'placement': u'PUBLISHER_NETWORK', u'account_id': u'18ce53ure0m', u'metric_groups': [u'ENGAGEMENT', u'BILLING', u'MOBILE_CONVERSION'], u'url': None, u'country': None, u'start_time': u'2018-01-08T08:00:00Z', u'updated_at': u'2018-01-16T09:53:38Z', u'expires_at': None, u'entity': u'CAMPAIGN', u'platform': None, u'id_str': u'953188292152868864', u'granularity': u'TOTAL', u'entity_ids': [u'2wxk4', u'2t0vy', u'2g8hn', u'2wxjo', u'2jhdr', u'1ntek', u'1ntem', u'1nqgw', u'1nteo', u'1ntes', u'19630', u'1ntet', u'1ntew', u'1ntey', u'2o76w', u'299hd', u'3w8ks'], u'segmentation_type': None, u'id': 953188292152868864, u'end_time': u'2018-01-15T08:00:00Z'}

Today’s effected client ID’s are:
1209608880, 1251697254, 1531669496, 17195943, 17337554, 19013415, 1929530274, 2216182879, 2227519429, 224423919, 22461067, 2273543695, 2302382365, 2382719060, 2551259005, 2561418950, 2650268413, 2713163052, 2730846469, 2735237864, 2755476668, 276254736, 2775022633, 305506258, 3087653766, 3110419942, 3121926687, 3142933058, 338395294, 3567023112, 3907244774, 4049118919, 4128631932, 4135775354, 4227914207, 4375185981, 439145234, 4831380050, 485416525, 541519782, 569569550, 581819199

Thanks,
Noa

[goforbrent]

wurl -H ads-api.twitter.com “/2/stats/jobs/accounts/18ce53ure0m” POST -d “entity=CAMPAIGN&entity_ids=2wxk4,2t0vy,2g8hn,2wxjo,2jhdr,1ntek,1ntem,1nqgw,1nteo,1ntes,19630,1ntet,1ntew,1ntey,2o76w,299hd,3w8ks&start_time=2018-01-08&end_time=2018-01-14&granularity=DAY&placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT,BILLING,MOBILE_CONVERSION” | jq

Please note that metric_groups=MOBILE_CONVERSION data should be requested separately. This worked for me and we have not noticed any large failures in our system over the past day.

[singular_noai]

Hi @goforbrent

Thank you for your reply.
We’re sorry to inform that we are still experiencing the same issue.
Yesterday we didn’t run into failures, but today we already have failures with 2 clients.

client id: '2735237864’
Fail:

 {u'status': u'FAILED', u'created_at': u'2018-01-18T08:06:22Z', u'placement': u'ALL_ON_TWITTER', u'account_id': u'18ce53wzyxh', u'metric_groups': [u'ENGAGEMENT', u'BILLING', u'MOBILE_CONVERSION'], u'url': None, u'country': None, u'start_time': u'2018-01-11T08:00:00Z', u'updated_at': u'2018-01-18T09:09:57Z', u'expires_at': None, u'entity': u'CAMPAIGN', u'platform': None, u'id_str': u'953901363657715714', u'granularity': u'TOTAL', u'entity_ids': [u'2ybiq', u'2y9an', u'2ybfe', u'35q30', u'35q39', u'35q38', u'2yax1', u'2ycbb', u'39089', u'2yaqr', u'2ya58', u'2y9s8', u'2yaql', u'2y9s1', u'2yaqd', u'390mm', u'399u9', u'2y9tz', u'2yaxj', u'2y9si'], u'segmentation_type': None, u'id': 953901363657715714, u'end_time': u'2018-01-18T08:00:00Z'}

client id: 17337554
fail:

{u'status': u'FAILED', u'created_at': u'2018-01-18T10:31:47Z', u'placement': u'ALL_ON_TWITTER', u'account_id': u'18ce54lat2m', u'metric_groups': [u'ENGAGEMENT', u'BILLING', u'MOBILE_CONVERSION'], u'url': None, u'country': None, u'start_time': u'2018-01-10T22:00:00Z', u'updated_at': u'2018-01-18T11:02:27Z', u'expires_at': None, u'entity': u'PROMOTED_TWEET', u'platform': None, u'id_str': u'953937960583413760', u'granularity': u'DAY', u'entity_ids': [u'1mwutg', u'1mwuth', u'1mwuti', u'1mwutj', u'1mwutk', u'1mwutl', u'1mwutm', u'1mwutn', u'1mwuto', u'1mwutp', u'1mwutq', u'1mwutr', u'1mwuts', u'1mwutt', u'1mwutu', u'1mwutv', u'1mwutw', u'1mwutx', u'1mwuty', u'1mwutz'], u'segmentation_type': u'PLATFORMS', u'id': 953937960583413760, u'end_time': u'2018-01-17T22:00:00Z'}

You’ve mentioned that metric_groups=MOBILE_CONVERSION data should be requested separately - Does this mean our request is invalid? Can it explain the issue we are experiencing?
Is this a valid request for aggregation?

Thanks for the help!
Noa Iarchy - Singular

[goforbrent]

Hi @singular_noai,

Technically the request isn’t invalid, but due to way in which these metrics are calculated. We stated as best practices to request “MOBILE_CONVERSION” data separately. If you’re still running into failures after you’ve separated the data requests, we will look into the issue.

Thanks!