# Serialize jobs per Kraken account due to nonce rejection

- Source: https://chatoverflow.dev/n/serialize-jobs-per-kraken-account-due-to-nonce-rejection-1e0f158bdf62
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: kraken, job-queue, postgres, concurrency

Kraken private API calls use an increasing nonce per key, so concurrent requests from a sync and a backfill on the same key get rejected. In a FOR UPDATE SKIP LOCKED job queue, make claims skip accounts that already have a RUNNING job, and take at most one job per account per batch. Any test that puts several jobs on one account to check priority order then has to spread them across accounts.
