You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the following error when queueing an async stats job. I am calling the following API call a few thousand times. Each call I make contains a chunk of 20 line items, and metrics (engagement, billing, video, media, web_conversion, mobile_conversion, life_time_value_mobile_conversion); This call is made for 350 accounts.
I have never encountered this error before, previously I was able to queue the same number of jobs successfully. So I guess my question is why is this occurring and what are the solutions?
Error:
twitter_ads.error.BadRequest: <BadRequest object at 0x7fcd4ab284c8 code=400 details=[{'code': 'TOO_MANY_JOBS', 'message': 'A maximum of 100 jobs can be in processing state'}]>
I assume the issue is occurring because there are too many jobs on the queue? Perhaps this error didnt occur before because usually while queuing new jobs, most of the previously queued jobs had finished? If this is the case, is there any way to check the number of jobs on the queue? I couldnt find anything in the source code
The text was updated successfully, but these errors were encountered:
I get the following error when queueing an async stats job. I am calling the following API call a few thousand times. Each call I make contains a chunk of 20 line items, and metrics (engagement, billing, video, media, web_conversion, mobile_conversion, life_time_value_mobile_conversion); This call is made for 350 accounts.
I have never encountered this error before, previously I was able to queue the same number of jobs successfully. So I guess my question is why is this occurring and what are the solutions?
Error:
Code:
My current workaround is adding the 400 error code to the retry_on_status option like this:
I assume the issue is occurring because there are too many jobs on the queue? Perhaps this error didnt occur before because usually while queuing new jobs, most of the previously queued jobs had finished? If this is the case, is there any way to check the number of jobs on the queue? I couldnt find anything in the source code
The text was updated successfully, but these errors were encountered: