Stale CMS data appears in Collection List after publish – unresolved cache invalidation

Objective

Determine whether updating CMS items during a Webflow publish operation can be done without exposing visitors to stale data in the Collection List component.

Constraints: Webflow publishing is atomic; there is no built‑in blue‑green deployment for CMS data; CDN‑side cache invalidation occurs after the publish completes, introducing an indeterminate window where the live site may serve pre‑publish content.

Uncertainty: The length of the stale‑data window varies with geographic CDN nodes and is not documented, making it unclear if a Collection List that renders a large number of items will consistently show outdated entries.

Questions:

• What is the maximum observable stale‑data window for a Collection List after a publish completes?
• Can a manual CDN cache purge be triggered for specific Collection List endpoints to reduce this window?
• Is there a supported method to defer CMS updates until after the publish propagation finishes without manual intervention?