Remote Terminal States Should Stop Re-Publishing Logic
If the provider already reports scheduled, publishing or published, the reconciler should observe rather than repeat the side effect.
idempotency
Publisher Retries Need Idempotency or They Create Duplicate Posts
When a network response is lost, retrying a create request can duplicate the side effect even if the first request succeeded remotely.
Redis 8.6 Streams Finally Address the Producer Retry Ambiguity Directly
A producer can time out after XADD without knowing whether Redis accepted the entry. Redis 8.6 adds stream idempotency so retries can be recognized without creating duplicate entries.
Find Existing Before Create Is a Practical Reconciliation Pattern
When the remote API lacks your preferred idempotency primitive, deterministic discovery can recover an uncertain previous attempt.
Queue Retry Policy Is Part of Data Integrity
Retry counts and backoff are not just performance settings when the job performs external side effects.
If the Same Button Is Pressed Twice, Should the Work Run Twice?
When a network response disappears, a user may retry even though the first operation already succeeded on the server. Whether the second request creates new work or returns the result of the first operation is part of the application's contract.