Troubleshooting¶
Common operational problems and where to start. For end-user-facing problems (login, downloads), see Common errors too.
Quick reference¶
| Symptom | Likely cause | What to check |
|---|---|---|
| Item approved but no DOI yet | The 10-minute mint cron hasn't run, or the item is out of scope. | Wait for the next run; confirm the item is archived, has an ARK, and is in target scope. Check the preflight report. |
| DOI doesn't resolve at doi.org | Deposit not yet processed, or a deposit error. | Check the nightly verify output; re-run the deposit if needed. |
| Edited item not updated at Crossref | Panel saves don't notify Crossref. | Trigger/await the nightly resync. |
| ARK doesn't resolve | Resolver or N2T mapping issue. | Confirm the ARK is populated; check the ARK resolver and its mapping. |
| User can't submit (no New submission) | Not in a submit group. | Add them to the right group — see Users & groups. |
| Registration email not arriving | Mail delivery or spam. | Check the SMTP (Mailjet) status; ask the user to check spam. |
| Site unreachable | DNS/TLS, network, or a service outage. | Confirm DNS resolves and the certificate is valid; check container health and nginx; escalate to ICT if it's an upstream/network issue. |
| Bulk import items missing ARKs | ARK back-fill not run. | Run the ARK mint/finalisation step; re-verify — see Bulk import (SAF). |
Before you change anything¶
Admin actions are public-facing
Test on a single item first when you can, and never approve/import a test item while the Crossref cron is live — see the identifier-safety rules in Identifiers (DOI & ARK).
Where the runbooks live¶
The authoritative operational records (the long-form "how it's built and run") are in the
config repo's docs/ — IMPLEMENTATION_GUIDE.md, SONNET_HANDOFF.md, HANDOFF.md,
PROGRESS.md, and crossref-deposit-pipeline.md. Keep them close for anything beyond the
table above.