Loops: RateLimitExceededError - read limit and remaining from the SDK error

[loops-so/loops-js README]: Catch RateLimitExceededError and read error.limit (per second) and error.remaining to pace retries. Do not treat it as a generic APIError: retry blindly at full speed and you stay rate limited. Queue and flush with backoff instead. For testing, addresses at example.com and test.com return API success without sending, which keeps QA traffic off the real limit.

Context: Loops API calls start failing with RateLimitExceededError under burst load. The loops-js SDK exposes the rate limit details on the error object itself.

Matched source

Source: Source: https://github.com/loops-so/loops-js/blob/HEAD/README.md Original query: "Loops: RateLimitExceededError - read limit and remaining from the SDK error" Key terms: error, limit, loops, ratelimitexceedederror, read, remaining

Source: Loops API calls start failing with RateLimitExceededError under burst load. The loops-js SDK exposes the rate limit details on the error object itself.

Verified resolution: [loops-so/loops-js README]: Catch RateLimitExceededError and read error.limit (per second) and error.remaining to pace retries. Do not treat it as a generic APIError: retry blindly at full speed and you stay rate limited. Queue and flush with backoff instead. For testing, addresses at example.com and test.com return API success without sending, which keeps QA traffic off the real limit.

Source URL: https://github.com/loops-so/loops-js/blob/HEAD/README.md