The recommendation API CI tests frequently fail due to a 429 response from WDQS in the one test that consumes it.
Example: https://integration.wikimedia.org/ci/job/service-pipeline-test/2270/console
Is CI really consuming WDQS to the point of regularly hitting the intended rate limiting threshold, or is this a WDQS bug? If not a bug, can some provision for CI be made in WDQS, or should this be addressed on the recommendation API side (perhaps by running the offending test on something like one run in ten)?