After today’s maintenance (?), API access to artifacts are failing with 429, with no RateLimit related headers in the responses to https://circleci.com/api/v2/project/<project-slug>/<job>/artifacts.
Other APIs work as expected (and I see RateLimit related headers).
What are we doing wrong???
Been seeing the same thing for the past 3 hours at least. In our case even just a basic https://circleci.com/api/v2/project/{project-slug}/job/{job-number} sometimes fails. Tried polling the API with 5 second intervals and it’s just failing randomly. Some requests pass, others return 429, no RateLimit header either.
This is affecting many pipelines for us, as well as some external integrations.
This should be resolved by now, sorry for the issues (tracked in the June 30 section of https://status.circleci.com/). let us know if youre still seeing issues