Troubleshooting

# Part 16 — Troubleshooting & FAQ

## "I never got the verification email"

1. Check your spam folder.
2. Visit **`/check-email`** and click **Resend confirmation email**.
3. If still nothing arrives after a few minutes, contact the team — there may be an SMTP issue.

## "My verification link says expired"

Links expire after a short window. Click **Request a new confirmation email** on the expired‑link page and try again.

## "I can't see the Activate Package button"

## "I lost my dashboard work mid‑wizard"

The wizard writes drafts at every step. Visit **`/dashboard/projects/new`** again — your last completed step is remembered. If your draft is truly missing, contact the team with your account email and we can recover the server‑side log.

## "I edited a chapter but my collaborator can't see the change"

1. Check that you clicked **Save** (the button turns into a green "Saved" badge briefly).
2. Confirm you weren't in **✦ Suggest mode** (suggestions need acceptance).
3. Refresh the page on the collaborator's side.

## "An EN approval should also approve FR"

By design, **EN and FR approvals are independent**. This is to let the English version ship while the French is still being polished (or vice versa). If you want to approve both, click both **✓ Approve EN** and **✓ Approve FR**.

## "The publishing bundle build skipped some items"

The status badge tells you why. If it's **🟡 Partial**, the missing items are optional (b‑roll, portraits) and you can still distribute. If it's **🔴 Incomplete**, click **🔍 View missing items** to see exactly which deliverable is missing — usually a media asset that hasn't been generated yet.

## "An heir says their access is locked"

Open **`/continuity/[clientId]/successors`** and confirm:

1. Their **role** (Child = always unlocked; Grandchild = gated)
2. Their **unlock condition** has fired
3. Their **acceptance** is recorded (if you have *Require acceptance* on)

If everything looks right, the lock will lift the next time they refresh.

## "The chat in the historian is too slow"

Each reply uses a simulated typewriter effect (~12ms per chunk) so the bubble feels responsive without flooding. If you'd rather see the whole reply at once, your team admin can adjust the stream rate.

---