# campaign_pause_not_confirmed

- HTTP status: 409
- Retry: Yes, with backoff
- Execution: may have started
- Admin needed: no

**Pause not confirmed.** The campaign is recorded as `paused` only once the telephony network confirms it. It did not, so the campaign status is unchanged and dialling may continue.

## What it means

The API returns HTTP 409 with `error.code` set to `campaign_pause_not_confirmed`. The default message is: "The pause was requested but not confirmed. The campaign may still be dialling."

## Common causes

- The pause did not take effect in time.

## How to identify it

Check the response status (`409`) and `error.code` (`campaign_pause_not_confirmed`). Branch on `error.code`, not on the message text: messages can be reworded, codes do not change within v1. Log `error.request_id` (also sent as the `X-Request-Id` header) so support can find the request.

## How to fix it

- Retry the pause (with the same Idempotency-Key if you sent one; a repeated pause is harmless), then retrieve the campaign. If it is still running, use stop.

## Retry guidance

Use exponential backoff (for example 1 s, 2 s, 4 s, up to about a minute). For a write, read the resource first to find out whether the change was applied before you send anything again.

## Did anything happen?

The work may have started before this error was returned. Do not assume nothing happened: read the resource (for a call, list calls filtered by `to` and `created_after`; for a campaign, retrieve it) before you send anything again. A charge may have been recorded for work that started; check the call or campaign before you act.

## Idempotency

Retry with the SAME key if you sent one; without a key a retry is simply another pause, which is harmless.

## Who can fix it

The developer who sends the request can fix it; no administrator action is normally needed.

## When to contact support

If repeated pauses are not confirmed, stop the campaign and write to [support@relationsai.com](mailto:support@relationsai.com). See [Support](/resources/support) for what to include (the `request_id`, the time in UTC, the operation, and whether you used a test or live key) and what never to send (API keys, Authorization headers, webhook signing secrets, recording links, transcripts or customer data).

## Example error response

```json
{
  "error": {
    "code": "campaign_pause_not_confirmed",
    "message": "The pause was requested but not confirmed. The campaign may still be dialling.",
    "details": {},
    "request_id": "req_vswznd7bcxaukatwznrlp2z7",
    "retry": "yes",
    "doc_url": "https://docs.relationsai.com/errors/campaign_pause_not_confirmed"
  }
}
```

## Operations that can return this error

- [`POST /campaigns/{campaign_id}/pause`](/api/campaigns#pause-a-campaign): Pause a campaign

See all codes in the [error-code reference](/fundamentals/error-codes).