# Call never started

<!-- GENERATED by gateway/scripts/generate-error-docs.mjs — DO NOT EDIT. This page renders gateway/contracts/errors.json; edit the catalogue and regenerate. -->

| | |
| --- | --- |
| HTTP status | `503` |
| Type | `https://docs.investorliftdata.com/errors/call-not-started` |
| Retryable | Yes |
| Retry-After header | Yes |

## What the body says

The response body says:

> This call was never started, and no Credits were consumed. Wait for the interval given in the Retry-After header, then send the request again.

## What happened to the Credits

No Credits are consumed by a call that ends here.

## Retrying

**Retryable.** Wait for the interval given in the `Retry-After` header, then send the request again.

## Body members

Beyond the base members (`type`, `title`, `detail`, `status`, `trace_id`), the body
carries:

| Member | Meaning |
| --- | --- |
| `retry_after` | The retry interval in seconds — the same value as the Retry-After header, repeated in the body for clients that only parse JSON. |

## Retry-After

Yes. The response carries a `Retry-After` header, and repeats it as `retry_after` in the body.

Every error response is an RFC 9457 Problem Detail sent as `application/problem+json`,
and every response carries a `trace-id` header, repeated in the body as `trace_id`.
The Trace ID is the only handle support needs to find your call.