Exceptions

Every exception lives in RoundlyConsulting\HttpClientRateLimits\Exceptions and extends RateLimitException:

Catching everything

use RoundlyConsulting\HttpClientRateLimits\Exceptions\RateLimitException;

try {
    Http::rateLimit('github')->get('https://api.github.com/user');
} catch (RateLimitException $e) {
    // Any package error: unknown profile, max wait exceeded, invalid store/deferrer, …
    report($e);
}

In a queued job using the ReleaseDeferrer, a catch-all also swallows JobReleasedException — and the job is already back on the queue, so the attempt carries on as if the request had run while the re-queued copy runs again later. Catch narrower, or rethrow the release first and let HandlesRateLimitRelease end the attempt:

use RoundlyConsulting\HttpClientRateLimits\Exceptions\JobReleasedException;
use RoundlyConsulting\HttpClientRateLimits\Exceptions\RateLimitException;

try {
    Http::withMiddleware(RateLimits::releasingJob($this)->perMinute(60)->by('github'))->get($url);
} catch (JobReleasedException $released) {
    throw $released; // HandlesRateLimitRelease ends the attempt
} catch (RateLimitException $e) {
    // a real limit or setup failure
}

Some errors from the same calls are not RateLimitExceptions: package-toolkit’s InvalidConfigurationException for a malformed config value (see Configuration), Laravel’s LockTimeoutException when the CacheStore can’t take a window lock in time, a RequestException rethrown from a handle() callback that calls ->throw(), and a store backend’s own failures — Redis connection errors, database QueryExceptions — which pass through unwrapped.