Certificate already exists error after rapid custom domain re-add in Webflow

Webflow provisions SSL for custom domains exclusively via Let's Encrypt and surfaces status as Pending, Failed, or Secure in Project Settings > Publishing > Custom domains.

A documented behavior notes that removing a custom domain and re-adding it quickly can cause Webflow to reuse a cached validation state that conflicts with Let's Encrypt's view, resulting in a 'certificate already exists' error that clears only after an undocumented cooldown period.

Because Webflow does not expose ACME challenge tokens or validation logs, the interaction between cached state, Let's Encrypt duplicate certificate limits, and DNS requirements for apex and www records is not observable from the UI.

What triggers reuse of cached validation state on rapid re-add? Is the cooldown period tied to Let's Encrypt's duplicate certificate window or to an internal Webflow cache? Can the cached state be invalidated without waiting for the undocumented period?