effect-missing-idempotency-key

warning

A call whose SDK supports an idempotency key is made without one.

Why it goes wrong

Guards can still let a repeat through (record rolled back with the transaction, lease expired, non-atomic check). Without a key the provider performs the effect again.

Safe pattern

Pass the SDK's idempotency key option, derived from the event or job id.

See it in the playground →

An example handler that triggers this rule.

Safe patterns guide →

Keys, transactions, leases, and status codes.

Configure

// retrysafe.config.ts
export default defineConfig({
  rules: { "effect-missing-idempotency-key": "warning" }, // or "off"
});

// or, for one line (a reason is required):
// retrysafe-ignore effect-missing-idempotency-key -- <why this is safe>