Operations Troubleshooting¶
Cross-cutting symptom → cause reference. For Cloudflare-specific symptoms (auth errors, CORS,
wrangler errors), see Cloudflare → Troubleshooting - this
page covers the broader operational picture.
| Symptom | Likely cause | Where to look | Safety of the check |
|---|---|---|---|
| A deploy succeeded but the site looks unchanged | Edge cache | Hard refresh; curl -I for cache headers |
[READ-ONLY] |
| Smoke test fails for exactly one app | That app's own deploy step | Verification, Logs | [READ-ONLY] |
| Smoke test fails for everything | Cloudflare-account-wide issue, not this repo | Cloudflare status page | [READ-ONLY] |
deploy-production stuck/queued |
Another deploy already running in the akshaya-production concurrency group |
GitHub Actions tab, wait for it to finish | [READ-ONLY] |
| A form submission 500s | API Worker exception | wrangler tail on the API Worker while reproducing |
[READ-ONLY] |
| A file download 404s unexpectedly | Key starts with private/ - refused by design |
R2 Operations | [READ-ONLY] |
| Data looks stale/missing after a "fix" | Migration applied to --local instead of --remote, or vice versa |
D1 Operations - always specify explicitly | [READ-ONLY] to check |
| Investors app not covered by an automatic deploy you expected | By design - excluded from ci.yml's deploy-production |
CI/CD → Deployment | N/A |
Admin/Embroidery not covered by a manual deploy-cloudflare.yml run |
By design - excluded from that workflow's matrix | CI/CD → Deployment | N/A |
| Suspected leaked secret in a commit | Never assume git revert fixes it |
Infrastructure → Security | Rotate immediately - [MUTATING] |