Errors and retries

Errors

A 4xx or 5xx response raises an error that carries the status code and the response body. Each documented status has its own class, so you can catch only what you expect.

import { EvcloudSDK, EvcloudSDKError, EvcloudSDKTypes } from "evcloud-sdk";
try {
    await client.emsp.commands.get({ tracking_id: "trk-123" });
} catch (error) {
    if (error instanceof EvcloudSDKTypes.NotFoundError) {
        // Unknown tracking id for this organization.
    } else if (error instanceof EvcloudSDKError) {
        console.error(error.statusCode, error.body);
    } else {
        throw error;
    }
}

All of them extend EvcloudSDKError (TypeScript) or ApiError (Python), and so does any other status. A request that runs out of time raises EvcloudSDKTimeoutError in TypeScript and httpx.TimeoutException in Python.

Retries

The SDKs retry a failed request up to 2 times, with exponential backoff, when the response is 408, 429 or 5xx. Change it per client (maxRetries) or per request (max_retries in Python’s request_options).

What is never resent

A POST that could act twice is sent once, even after a 503. If the response was lost, the first attempt may already have created the location or sent the command, so a retry would do it again. This covers creates, commands and other actions.

Before you retry one of these yourself, check whether the first attempt went through, for example with emsp.commands.list or energy.controlRequests.list.

Operations that require an Idempotency-Key header, such as emsp.tokens.provision and the eMSP token and network actions, keep their retries: the API returns the first result for a repeated key.