I treated publishing as a queue. The queue lied.

说明与用途

作者构建的自动发布系统因未与公共状态对齐而导致重复和遗漏。通过采用显式状态机并在记录成功前验证“receipt”，消除了重复并提高了可靠性。

问题

The author’s automated publishing queue produced duplicate or missing posts because it treated local state as the source of truth and failed to reconcile with the public platform’s state, leading to ambiguous failures and potential duplicate content.

结果

The new state‑machine approach prevented duplicate posts, clarified recovery paths, and made the system resilient to timeouts and metadata errors.

工作流

• Pick next topic from rotation
• Check 60‑hour minimum interval
• Open editor and load draft
• Publish article via browser
• Verify public URL and content fingerprint
• Record state transition to published_verified
• If metadata incomplete, repair series or tags
• If timeout occurs, mark verification_pending and retry after observing destination

证据

I stopped storing only published: true or published: false. I need enough state to answer what may happen next without reconstructing intent from logs.

来源

A duplicate run can happen four days later. A stale editor can survive longer than a lock.

来源