Troubleshooting checklist
Start with durable state
Check the certificate, batch, delivery, or endpoint page before retrying. A browser timeout does not prove that the database transaction failed.
Keep identifiers safe
Share the request ID, workspace-visible certificate ID, and approximate UTC time with support. Never send passwords, API keys, signing secrets, encryption keys, card data, or SMTP credentials.
Rendering problems
Confirm the template is published, required fields are present, and all assets were uploaded to CertKit. External URLs and scripts are intentionally blocked.
Email problems
Run the SMTP connection test, verify the From address is permitted by the provider, and use an app password where required. Review the delivery log before retrying.
API problems
Read authentication and idempotency and find the exact code in the API error reference. Preserve the request ID and retry only according to that entry.
Still blocked
Use the support form and describe the expected outcome, actual outcome, and safe reproduction steps.