# BRD-254 — Appeal only a vet that has finished

> An appeal may be filed only against a vet in a final state — never against one still pending.

- **Rule ID:** BRD-254
- **Layer:** Brand (`BRAND`)
- **Checks:** `the vet state`
- **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:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-254/

## Why this rule exists

A pending vet has not decided anything, so an appeal against it is refused on entry and the attempt is wasted. The reason people file early is that a vet in progress is indistinguishable from one that is stuck, and the appeal form is available the whole time.

## How to fix it

Wait for the vet to reach ACTIVE, COMPLETE, FAILED or EXPIRED before filing. If it looks stuck, the cause is usually an unanswered 2FA rather than a queue — chase that instead. Done when the appeal is filed against a vet that has actually concluded.

## Example of a compliant value

```text
appeal filed against a vet in FAILED state — not against one still PENDING
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| TCR | `592` | yes |