Custom domain SSL validation lacks detailed error reporting

Custom domain SSL validation lacks detailed error reporting

The platform requires automatic SSL certificate issuance when a custom domain is linked via correct A or CNAME records, yet the failure mode that prevents the transition from pending to active remains opaque.

Current logs only indicate a generic validation error without specifying whether the cause is DNS propagation delay, an incorrect record target, or an API rate‑limit response, making troubleshooting inefficient.

What specific error details should Discloud expose to distinguish DNS mismatches from rate‑limit throttling, and does the platform provide a mechanism to retrieve the exact failure reason without manual restart?