A developer found 4 of 9 deployed pages were 404 despite a 'success' message

A developer discovered that four of nine newly deployed pages returned 404 errors shortly after a deployment tool reported a successful upload. Checking the live URLs directly revealed the issue was edge propagation, and all pages resolved to 200 within seconds — but only because the developer verified manually. The incident highlighted a broader pattern: tools like deploy CLIs, task schedulers, and shell pipelines truthfully answer a narrow question, but that answer is often misread as confirmation of a wider outcome. The author also found that a shell pipeline was silently masking a non-zero exit code from a guarded script, because the pipe reports the last command's status rather than the whole chain. The core lesson is that a success report only testifies within its own jurisdiction — not whether the intended end result was actually achieved.