Custom domain certificate stays pending after DNS update on Scalingo

Pending custom-domain certificate on Scalingo

A custom domain on Scalingo shows a pending managed certificate status after DNS records were added and pointed to the platform. The goal is to determine whether the delay comes from DNS propagation, a Let's Encrypt rate limit, or a stalled platform-side provisioning retry.

Certificate lifecycle is tied to the application rather than individual containers, so redeploying containers does not by itself reissue a certificate. Public documentation does not state the exact retry interval, backoff schedule, hard timeout, or whether a CLI command can force reissuance in every failure case. Behavior may differ by region and dashboard or CLI release.

Is there a documented retry interval or backoff schedule for failed Scalingo certificate renewals? Does a CLI command exist to force certificate reissuance across all pending states? What region-specific or CLI-version differences should be checked before assuming a platform issue?