The deployment pipeline clears the CDN correctly, but users still receive broken bundles because the invalidation precedes the final asset upload and manifest sync.
CloudFront invalidation runs before the new asset manifest is fully published
The deployment pipeline clears the CDN correctly, but users still receive broken bundles because the invalidation precedes the final asset upload and manifest sync.
Scenario
What to check first
- Identify the primary failure signal in the Static Asset Release Order scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.
Questions worth viewing together
Users can receive a new HTML or manifest view before every referenced asset is actually present on origin.
Similar cases seen in the field