> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livingsecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# service_unavailable

> Public API error service_unavailable — the service could not return a successful response (HTTP 503).

| | |
| - | - |
| **Code** | `service_unavailable` |
| **HTTP status** | `503 Service Unavailable` |
| **Retryable** | Yes |

## What it means

The service could not return a successful response for this operation. Follow
the recovery steps below. For writes, the error does not establish whether the
operation took effect.

## What to do

* For reads, retry with a finite attempt and time budget using exponential backoff and jitter. Honor `Retry-After` when present.
* For writes, a `503` does not prove that nothing happened. Follow the operation's documented recovery procedure. Only retry automatically when the operation explicitly supports it; preserve the original `Idempotency-Key`, request body, resource path and API version.
* Do not switch to a new key to retry an uncertain write. Retrieve the resource when you know its ID, or investigate before submitting another operation.
* If the error persists, contact [Living Security Support](mailto:support@livingsecurity.com) with the `request_id` from the response.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.