Forum Discussion

atodd's avatar
atodd
New Contributor
1 month ago
Solved

Zephyr Scale: Too Many Requests error after adhering to Retry-After: 60

In V15, all the post requests going to Zephyr Scale are returning a 429 Too Many Requests error. The Retry-After states 60, which interprets as 60 seconds. After putting in a 60 second pause when this error is triggered and retrying the post, the error still occurs. This issue wasn't happening prior to  V15 with the same post requests at the same interval. The post is in reference to creating a test execution onto Zephyr Scale.

HTTP/1.1 429 Too Many Requests [Date: Wed, 27 May 2026 17:23:14 GMT, Content-Type: application/json, Content-Length: 81, Connection: keep-alive, Server: awselb/2.0, Retry-After: 60, Via: HTTP/1.1 m_proxy_prod_aws_us-east-1_1_1n, X-Amz-Cf-Pop: IAD55-P2, X-Amz-Cf-Id: gVutaZyFhexaGL8SX4IDUTMJXrX_Lq84grI9QfLNx897Aa5vr1q2-A==] org.apache.http.conn.BasicManagedEntity@712594f4

  • maksym_lytvyn's avatar
    maksym_lytvyn
    27 days ago

    Hey folks,

    Good news -- the fix has been deployed. The rate limiting regression on POST /testexecutions has been resolved and things should be back to normal.

    Please give it a try and let us know in this thread if you’re still seeing any issues. If problems persist, please open a support ticket and we’ll look into it directly. 

    Thank you all for your patience and for the detailed reports -- they were genuinely helpful in tracking this down.

5 Replies

  • dariia's avatar
    dariia
    Regular Visitor
    1 month ago

    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.

  • janeislzr's avatar
    janeislzr
    New Member
    1 month ago

    im having the same problem it only ocurres with the test execution onto Zephyr Scale.

    The service is receiving too many requests from you [item 1]

    {'code': '429', 'error': 'Rate limit reached. Please try again after 1 minutes.'}

  • maksym_lytvyn's avatar
    maksym_lytvyn
    Icon for Staff rankStaff
    27 days ago

    Hey folks,

    Good news -- the fix has been deployed. The rate limiting regression on POST /testexecutions has been resolved and things should be back to normal.

    Please give it a try and let us know in this thread if you’re still seeing any issues. If problems persist, please open a support ticket and we’ll look into it directly. 

    Thank you all for your patience and for the detailed reports -- they were genuinely helpful in tracking this down.

  • lbanawa's avatar
    lbanawa
    Occasional Visitor
    30 days ago

    We have been encountering this same issue with POST /v2/testexecutions but never on PUT /v2/testexecutions even with almost similar request volume.

    maksym_lytvyn​ has there been any updates and/or resolution on this?