# campaign_recipients_suppressed

- HTTP status: 422
- Retry: No
- Execution: not started
- Admin needed: no

**Every recipient is suppressed.** At start, recipients on the do-not-call list, without required consent or at their daily limit are left out. When that leaves nobody, the start is refused.

## What it means

The API returns HTTP 422 with `error.code` set to `campaign_recipients_suppressed`. The default message is: "Every recipient of this campaign is blocked by your compliance settings. Nothing was dialled."

## Common causes

- All recipients are on the do-not-call list, lack consent, or reached their daily limit.

## How to identify it

Check the response status (`422`) and `error.code` (`campaign_recipients_suppressed`). 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

- This is a compliance outcome: do not retry; an unchanged start is refused again.
- Add recipients who can be called. Record consent or remove a do-not-call entry only when the person really asked, and keep a record of it.

## Retry guidance

Sending the request unchanged fails the same way. Fix the cause first (see How to fix it), then send it again.

## Did anything happen?

This request was refused before any call was placed and before anything was charged.

## Idempotency

Refused for compliance; nothing was dialled and the refusal is not stored under the Idempotency-Key. Do not retry: resending the same call (with any key) is refused again until the cause has legitimately changed.

## Who can fix it

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

## When to contact support

If the error persists after the steps above, contact [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_recipients_suppressed",
    "message": "Every recipient of this campaign is blocked by your compliance settings. Nothing was dialled.",
    "details": {},
    "request_id": "req_vaip2hi2rkfqn2eguaai5ycy",
    "retry": "no",
    "doc_url": "https://docs.relationsai.com/errors/campaign_recipients_suppressed"
  }
}
```

## Operations that can return this error

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

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