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.

Источник