# BrandingNotRemoved

A Branding being deleted is still on the server; it is Ready=False in phase Deleting.

## Meaning

A Branding has no deletion policy: deleting it removes the document from the server, and
the server has not done so. It did not answer, serves an unsupported contract, refused the
call (often the `brandings` operation missing from the grant), or the operator's credential
is unusable. The message carries the cause. The finalizer `nauthera.io/branding` holds the
resource until the document is gone.

## Impact

The client's sign-in pages keep wearing the old document instead of falling back to the
organization's default. The application team's namespace may stay in Terminating.

## Diagnosis

1. `kubectl -n <ns> describe branding <name>` for the cause.
2. `nauthera_operator_server_calls_total{call="DeleteBranding"}` by `code`.
3. `kubectl -n <release-ns> logs deploy/<release>-operator` around the deletion.

## Mitigation

- Fix the cause (see Unreachable, Refused, Unsupported); the removal is retried every five
  minutes, or about once a minute while the server does not answer.
- Removing the finalizer by hand leaves the document; the hourly orphan sweep removes a
  branding whose manifest is gone once the server answers.

## Escalation

Rarely urgent, since the pages still render. Escalate to the platform team if it persists
past a server recovery, with the condition message and the call metrics.

---

[Operator failure reasons](https://www.nauthera.io/docs/v1/runbooks/operator) · Generated from [`operator/internal/runbook/conditions.yaml`](https://github.com/nauthera/nauthera-server/blob/main/operator/internal/runbook/conditions.yaml) in nauthera-server.