Preventing Duplicate Delivery Across Automation Threads
How a destination-and-content idempotency key, unknown-result handling, and repeated sibling-task checks can stop resumed automation from repeating an external side effect.
10 articles
How a destination-and-content idempotency key, unknown-result handling, and repeated sibling-task checks can stop resumed automation from repeating an external side effect.
A remote-aware display guardian uses connection events, local input, cancellable deadlines, and fail-closed evidence to keep an unattended Windows workstation dark without interrupting active remote work.
A safe automation handoff separates live authority, recovery evidence, retired execution paths, and disposable local state before anything is removed.
How an explicit revision lifecycle can reopen a completed external-delivery job without duplicating remote objects or trusting stale review evidence.
How versioned policy snapshots keep active jobs and retries reproducible while new rules roll out prospectively.
How to keep required repository checks meaningful when an automation branch frequently commits heartbeats, checkpoints, and other run state.
How request-based health checks, bounded local control, and explicit ownership turned a stale automatic proxy group into a recoverable connection path.
How reviewed fictional actors, actions driven by visible causes, pre-generation frame review, model routing by shot importance, and file hashes make realism checks repeatable and version-specific.
How a stable allocation key and a process lock let a recurring paid pipeline create several jobs per period without duplicating work when a scheduled run retries.
How I diagnosed interrupted RF label batches and added per-label delivery with a retry boundary that avoids duplicate prints.