Same issue here since late May 2026.
We run multiple parallel E2E test areas in a nightly CI pipeline, each publishing results to Zephyr Scale via POST /testexecutions. Starting around the same time as your V15 report, we began seeing persistent 429s - not just on the first hit, but on every retry attempt even after honoring Retry-After: 60. Our logs show jobs retrying multiple times over several minutes, all still returning 429.
maksym_lytvyn It would be very helpful to understand:
1. What changed in V15 with respect to rate limiting for POST /testexecutions?
2. Is the rate limit now enforced per-token globally (across concurrent requests) rather than per-request?
3. Is there a documented requests-per-minute limit we should stay within?
We'll be submitting a support ticket as well, but adding this here since the issue clearly affects multiple teams.
