Troubleshooting & Reference · Article 7.11
"Database / migration error" — operator runbook pointer
This article is a placeholder for operator-facing issues (failed migrations, schema mismatches, stuck Celery queues). End users don't hit these directly; if the symptom is described here, escalate to operations.
If you're a freelancer reading this article, you're probably in the wrong place. Database and migration issues surface as 500 errors or unexplained "something went wrong" messages; the fix is on the operations side. Contact support — they have the runbooks and access.
Step by step
Refresh once.
Some 500s are transient — server restart in progress, brief deploy window.
Retry the action after 60 seconds.
If still failing, contact support
with the proposal number and a screenshot of the error.
Why this works this way
This page exists because the help wiki indexes by symptom, and "internal server error" is a symptom users do encounter. The information here is intentionally sparse — the actual recovery procedures live in operator-only documentation.
Troubleshooting
Keep reading
Troubleshooting & Reference
"My client says they didn't get the email"
The most common support question Clozo gets. Five checks resolve nearly all cases — most of the time, the email landed in spam.
Troubleshooting & Reference
"The invoice link is broken or the PDF is missing"
PDFs occasionally fail to render (Gotenberg flake) or fail to upload to R2. Symptom: the document shows as "issued" but clicking the link returns 404 or the PDF is blank. Recovery: regenerate from the Documents dropdown.