# Spend outcome indeterminate

<!-- 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/spend-indeterminate` |
| Retryable | Yes |
| Retry-After header | Yes |

## What the body says

The response body says:

> This Metered Call did not complete, and the outcome of its Spend is not known. Any Credit recorded for it will be returned to the Account as a Refund. Wait for the interval given in the Retry-After header, then send the request again.

## What happened to the Credits

No claim is made about what was consumed, because the outcome is not known. Any Credit recorded for the call is returned to the Account as a Refund.

## 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.