Continuing the discussion from 503 error occurring seemingly connected with mobile_conversion_re_engages metric:
Thank you for your response on this. I have done some further investigation and agree that reducing the number of funding instruments in the request does stop the error. In the request I posted there are 18 funding instruments. I have found that the crossover point between getting the 503 error and not getting it is about 7 or 8, i.e. I can run the code successfully by batching this up to about 8 per request, but not thereafter.
However I’m not entirely convinced yet that this is only a matter of requesting too much information and therefore hitting rate limits. Specifically I’d like to raise the following points:
• Why is this showing up as a 503 error rather than 429, as we’d expect for rate limiting issues?
• Why does this only affect account d80pk and not any others?
• Why does the issue only appear on inclusion of one specific metric?
• Connected with the above two points, how is it that we have to reduce the number of funding instruments per request so significantly in this one very specific case before it works? This is the main point – the circumstances around the failure seem too specific to be explained only by requesting too much data.
I can certainly change our code to ensure we minimise the number of funding instruments we include in a single request, but I feel that there might be something else going on here which is not yet explained.
Apologies if I’ve misunderstood something about how this works, but please can you let me know if you have any further advice on this, many thanks.