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

# CHANGE_UNCONFIRMED

> Change not confirmed

| HTTP status | Retryable |
| - | - |
| `503` | Yes |

## What happened

The phone number did not confirm the edit or unsend in time. It may or may not have applied.

## How to fix it

Retry with the same idempotency key. Blujay checks whether the change already applied before trying again.

> [!TIP]
>
> This error is safe to retry. Wait for the `Retry-After` header when it is present. If the endpoint takes an `Idempotency-Key`, reuse the same key so a retry never creates a duplicate.

## Example response

An illustrative example. The `message` wording and the contents of `details` vary; branch on `error.code`.

```json theme={null}
{
  "status": "error",
  "error": {
    "code": "CHANGE_UNCONFIRMED",
    "message": "Change not confirmed",
    "type": "phone_number",
    "http_status": 503,
    "retryable": true,
    "doc_url": "https://docs.blujay.io/errors/change-unconfirmed",
    "details": []
  },
  "trace_id": "trc_8f2a1c0e4b7d",
  "timestamp": "2026-10-14T17:30:48.000Z"
}
```

## Still stuck?

Email [support@blujay.io](mailto:support@blujay.io) with the `trace_id` from the error response. See [Errors](/errors.md) for the response format.


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