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

# Troubleshoot a pending number or Sender ID

> Diagnose a number stuck at pending_compliance or a Sender ID stuck at pending, read the rejection reason, and re-submit with the right documents.

# Troubleshoot a pending number or Sender ID

Two surfaces gate on regulatory approval before they carry traffic: a
phone number waiting on a compliance profile, and an alphanumeric
Sender ID waiting on a country registration. Until the gate clears,
sends to that surface stay blocked. This page walks each status to its
cause and to the fix you can run yourself.

<Note>
  Compliance posture is yours to configure — Orbit gives you the
  controls and defaults them open. Final approval of a number or
  Sender ID always comes from the carrier or regulator, not from the
  platform, so lead time in this page is an expectation, not a
  guarantee.
</Note>

***

## Map the status to its meaning

**Phone numbers** — a number at `pending_compliance` is blocked from
sending or receiving until an approved compliance profile is attached
to it. Orbit re-submits the profile to the carrier and a carrier
webhook flips the number to `active`. See the full flow in
[Number Lifecycle](/numbers/lifecycle).

**Sender IDs** — a country entry at `pending` means the registration
was submitted and is awaiting review by the regulator or carriers in
that country. `approved` means traffic may flow; `rejected` or
`expired` block traffic until you re-submit. The four states are
documented on [Sender-ID Registration](/compliance/sender-id-registration).

***

## Fix a pending number

Attach an approved compliance profile to the number:

```bash theme={null}
curl -X POST https://api.orbit.devotel.io/api/v1/numbers/num_abc123/attach-compliance-profile \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{ "compliance_profile_id": "cprof_abc123" }'
```

The number flips to `active` when the carrier accepts the profile. If
you do not yet hold an approved profile, create one from your KYC
documents first, then attach it.

## Fix a pending or rejected Sender ID

Re-submit the registration packet with the documents the destination
country requires — the per-country sender types, registration flag,
and required documents are in
[Country Compliance Requirements](/compliance/country-requirements).
Re-submitting the same Sender ID is an idempotent upsert: countries
you already hold `approved` keep their approval, and countries that
were `rejected` or `expired` return to `pending` for a fresh review.
See
[Sender-ID Registration](/compliance/sender-id-registration#register-or-update-a-sender-id).

***

## Read the rejection reason

For numbers, check the **Numbers** page in the dashboard — the row
for a `pending_compliance` number shows what the carrier flagged.

For Sender IDs, open **Settings → Compliance → Sender IDs** in the
dashboard. Each country entry carries its status and the notes the
reviewer left; a `rejected` entry names what to fix before you
re-submit. Team members with access to the admin review queue can
also see the packet notes there.

***

## Country outliers that surface explicit error codes

Some markets block unregistered alphanumeric senders at send time
with a specific error code:

| Country      | Error code                           | Fix                                                                                          |
| ------------ | ------------------------------------ | -------------------------------------------------------------------------------------------- |
| Brazil       | `MESSAGING_BR_SENDER_NOT_REGISTERED` | Register the Sender ID with Anatel and wait for `approved` in Brazil.                        |
| Singapore    | `MESSAGING_SG_SENDER_NOT_REGISTERED` | Register the Sender ID on the SGNIC Sender ID Registry and wait for `approved` in Singapore. |
| Saudi Arabia | `MESSAGING_SA_SENDER_NOT_REGISTERED` | Register the sender name with CITC.                                                          |
| UAE          | `MESSAGING_AE_SENDER_NOT_REGISTERED` | Register the sender name with TDRA.                                                          |

**India is a separate regime.** Sender IDs there are DLT "Headers"
paired with DLT content templates — sends without an approved DLT
template return `MESSAGING_IN_DLT_TEMPLATE_REQUIRED`, and a body or
header that does not match the registered template returns
`MESSAGING_IN_DLT_CONTENT_MISMATCH`. Register your Principal Entity,
Headers, and templates on a DLT portal, then record them in Orbit.
See [DLT-India Onboarding](/compliance/dlt-india).

***

## Lead time and when to escalate

Approval lead time is set by the regulator or carrier, not by Orbit. A
few examples from the registry:

* Many EU markets clear within days; some take a couple of weeks.
* Brazil and Singapore routinely take days to weeks.
* India DLT artifacts clear on the registrar's timeline, then mirror
  into Orbit as the registrar updates their status.

Escalate to support when:

* A number has stayed `pending_compliance` for more than two weeks
  after the profile was attached.
* A Sender-ID entry has stayed `pending` beyond the lead time the
  country registry publishes.
* A `rejected` entry gives a reason you cannot resolve with the
  documents you hold.

Include the number ID or Sender-ID value, the country, and the
current status so the reviewer can pull the packet directly.

***

## Related references

* [Sender-ID Registration](/compliance/sender-id-registration) — the registration endpoints and status lifecycle.
* [Country Compliance Requirements](/compliance/country-requirements) — per-country sender rules and required documents.
* [DLT-India Onboarding](/compliance/dlt-india) — India's separate DLT regime.
* [Number Lifecycle](/numbers/lifecycle) — the `pending_compliance` flow and the attach-profile endpoint.
* [Error Codes](/reference/error-codes) — the full sender-registration error-code table.
* [Compliance Posture FAQ](/compliance/posture-faq) — the mental model for "pending until an external approval lands."