Cloudflare Pages Runbook

Service: Cloudflare Pages (site-base, proposals) Trigger: Deployment failure, DNS propagation delay, or site unavailable Severity: P1 high

Steps

Build failure

1. Open GitHub Actions tab for the relevant repo (github.com/Curious-Owl11)
2. Find the failing workflow run and check the build log for the error
3. Fix the build error in the repo and push — this triggers a new deployment automatically
4. If the fix is not immediately obvious, re-trigger the deployment from the Cloudflare Pages dashboard

DNS propagation delay

1. Log in to the Cloudflare dashboard
2. Navigate to the domain's DNS settings and verify the CNAME/A record is correct
3. Check propagation status at https://dnschecker.org
4. DNS propagation can take up to 48 hours — no action required unless records are wrong

Rollback to previous deployment

1. Log in to the Cloudflare Pages dashboard
2. Select the project (site-base or proposals)
3. Go to Deployments tab
4. Find the last known-good deployment and click "Rollback to this deployment"

Rollback

Cloudflare Pages supports instant rollback via the dashboard — see steps above. No data loss risk as Pages is stateless.

Contacts

• On-call: hello@liflode.com
• Cloudflare dashboard: https://dash.cloudflare.com
• GitHub Actions: https://github.com/Curious-Owl11

Related ADRs