---
title: "Fix it on Launch"
url: "https://developers.contentstack.com/paths/fix-it-on-launch"
type: "path"
level: "intermediate"
outcome: "You can diagnose a broken Launch build, decode a Launch error code and get a custom domain live."
steps:
  - "https://developers.contentstack.com/guides/published-but-my-site-still-shows-old-content"
  - "https://developers.contentstack.com/guides/fix-failing-launch-builds"
  - "https://developers.contentstack.com/guides/launch-error-codes-decoded"
  - "https://developers.contentstack.com/guides/custom-domain-stuck-on-pending-validation"
  - "https://developers.contentstack.com/guides/debug-a-failing-launch-deploy-with-an-agent"
updated: "2026-11-15T11:47:31.585Z"
---

# Fix it on Launch

- **Level:** Intermediate
- **Steps:** 5
- **Full path in one document:** https://developers.contentstack.com/paths/fix-it-on-launch/full.md

---

The problems developers hit most on Contentstack Launch, from stale content and failing builds to error codes and custom domains, and how to fix each one.

**You'll end up with:** You can diagnose a broken Launch build, decode a Launch error code and get a custom domain live.

## Steps

1. [I published, but my site still shows old content](https://developers.contentstack.com/guides/published-but-my-site-still-shows-old-content) (Guide, Beginner)
   - You'll end up with: You can find the layer that holds an old copy of your content, from the publish itself to the browser, and apply the fix that matches it.
   - Checkpoint: You can tell which cache layer is serving stale content.
2. [Fix failing Launch builds](https://developers.contentstack.com/guides/fix-failing-launch-builds) (Guide, Intermediate)
   - You'll end up with: You can match a failing Launch deployment to its cause from the log line or symptom and apply the fix that belongs to it.
   - Checkpoint: Your build passes with the right env vars, Node version and output directory.
3. [Launch error codes decoded: CF005, CF1001, CF1004, CF003 and more](https://developers.contentstack.com/guides/launch-error-codes-decoded) (Guide, Intermediate)
   - You'll end up with: You can map a Launch error code to the limit or failure behind it, find the evidence in the logs and apply the fix.
   - Checkpoint: You can map a CF error code to its cause and fix.
4. [Custom domain stuck on Pending validation in Launch](https://developers.contentstack.com/guides/custom-domain-stuck-on-pending-validation) (Guide, Intermediate)
   - You'll end up with: Your custom domain and its certificate both show Active in Launch, traffic reaches the right environment, and redirects behave the way you expect.
   - Checkpoint: Your custom domain and certificate are live.
5. [Debug a failing Launch deploy with an agent](https://developers.contentstack.com/guides/debug-a-failing-launch-deploy-with-an-agent) (Guide, Intermediate)
   - You'll end up with: You can have an agent find a failed Launch deployment, read its logs, name the likely cause, and redeploy only after you approve it.
   - Checkpoint: An agent can pull logs and diagnose a failed deploy for you.

