# BRD-248 — One political import at a time

> A second Campaign Verify import must not be submitted while one is in progress.

- **Rule ID:** BRD-248
- **Layer:** Brand (`BRAND`)
- **Checks:** `the Campaign Verify import queue`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-248/

## Why this rule exists

The second request is refused rather than queued, and because a political import is slow it looks stalled long before it is — so resubmitting is the obvious thing to do and it makes the situation worse rather than better. On a dated campaign, the lost cycle is the actual cost.

## How to fix it

Let the in-flight import finish before submitting anything else against this brand. If it has genuinely stalled, ask the provider to check its state rather than resubmitting — a second request is refused and does not replace the first.

## Example of a compliant value

```text
One political import in flight — check its state rather than submitting a second
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `21723` | yes |

## Notes

Absorbs OPS-321, which states the same in-flight restriction and the request fields it applies to.