The job that ran twice: leases, idempotency keys and the duplicate your schedule will eventually produce - DEV Community
At-least-once is the default at every layer. Exactly-once effect is buildable: a lease claimed in one statement, a fencing token on every write, keys derived from the fact rather than the run, and one extra state in the ledger.