Short answer: Treat a browser download link as the last state in an export workflow, not as proof that the export worker finished. Persist one canonical object key, verify that exact key after the upload, and issue the expiring link only after the job reaches a separately named downloadable state. That sequence catches the two failures that look alike in a property-management system: a race between job completion and storage visibility, and a wrong key prefix assembled by another service.
This is a small state machine with three different clocks: the export job, the object store, and the browser's link expiry. The 404 is useful evidence, but it does not identify which clock was read incorrectly.
The incident lesson: “exported” did not mean “downloadable”
The bounded failure I care about is a batch of private inspection reports generated for property managers.…