The job that ran twice: leases, idempotency keys and the duplicate your schedule will eventually produce
The duplicate never announces itself. It arrives as a second confirmation email that looks like a courtesy, or a second charge that looks like a pricing bug, or a message to a stranger that the log says was sent exactly once. I run a scheduled assistant: a few dozen actions that wake themselves at…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-11-14 21:17 · DEV Community — AI
The job that ran twice: leases, idempotency keys and the duplicate your schedule will eventually produce