Skip to content

[Bug]: Claude gateway cooldown is dropped when the SDK rejection has no timestamp #39691

Description

@Brechard

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

Run a Claude turn through a gateway that publishes its cooldown in a 429 response. This run produced the following SDK frames, in order:

  1. A rate_limit_event with rate_limit_info: {"status":"rejected","isUsingOverage":false}. The frame supplies neither a limit type nor a reset timestamp.

  2. A synthetic assistant error with error: "rate_limit".

  3. A terminal result with is_error: true, terminal_reason: "api_error", and api_error_status: 429. Its text reads:

    API Error: Server is temporarily limiting requests (not your usage limit) · All credentials for model claude-opus-5-5 are cooling down (last error: rate_limit_error: This request would exceed your account's rate limit. Please try again later.) (reset after 2h26m17s)
    

Expected behavior

Use the gateway countdown to recover the reset timestamp when the SDK rejection supplies no limit type or timestamp. A separately identified limit with an unknown reset should still prevent scheduling an automatic retry.

Actual behavior

The saved failure has code: "api_error_429" and resetAt: null. The thread shows Reset time unavailable; retry manually and cannot resume automatically. This happened on three captured turns, each with a countdown in the terminal result.

The Claude adapter reads the countdown and then drops it when the timestamp-free rejection is included in the list of reset times. Adapter source

Impact

Major degradation or frequent failure. Repeated cooldowns require manual retries.

Version or commit

Observed on a T3 server reporting 0.1.10. The same adapter logic is present on upstream main at 7fcec368cb1.

Environment

Linux x64, Claude Code SDK, Claude Opus 5.5 through a gateway.

Related work

The earlier change for the countdown's placement in the error message addresses parsing. The failure here occurs when the adapter combines the parsed countdown with the SDK rejection. #37692

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    vouch:trustedAuthor is trusted by repo permissions or the VOUCHED list.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions