500 error (unique constraint failed) trying to add cards

[pjeby]

Running on docker with a db exported from the cloud version of fizzy, and it suddenly started getting Internal Server Error trying to add any cards. I'm assuming this is something to do with a sequence number getting out of sync and will investigate that angle next, but here are the logs in case that's helpful:

fizzy_1  | {"time":"2026-02-17T19:58:56.651510754Z","level":"INFO","msg":"Request","path":"/1/cards.json","status":500,"dur":43,"method":"POST","req_content_length":111,"req_content_type":"application/json","resp_content_length":46,"resp_content_type":"application/json; charset=UTF-8","remote_addr":"76.128.231.248","user_agent":"fizzy-cli/1.0","cache":"bypass","query":"","proto":"HTTP/1.1"}
fizzy_1  | I, [2026-02-17T20:00:00.009836 #94]  INFO -- : [ActiveJob] Enqueued SolidQueue::RecurringJob (Job ID: 1beba0d9-fb32-454f-8596-cc7d880017dd) to SolidQueue(solid_queue_recurring) with arguments: "Notification::Bundle.deliver_all_later"
fizzy_1  | I, [2026-02-17T20:00:00.018345 #94]  INFO -- : [ActiveJob] Enqueued SolidQueue::RecurringJob (Job ID: db8c6d80-5912-4aaf-adfe-27432c21ee43) to SolidQueue(solid_queue_recurring) with arguments: "MagicLink.cleanup"
fizzy_1  | I, [2026-02-17T20:00:00.099638 #72]  INFO -- : [ActiveJob] [SolidQueue::RecurringJob] [1beba0d9-fb32-454f-8596-cc7d880017dd] Performing SolidQueue::RecurringJob (Job ID: 1beba0d9-fb32-454f-8596-cc7d880017dd) from (solid_queue_recurring) enqueued at 2026-02-17T20:00:00.006221416Z with arguments: "Notification::Bundle.deliver_all_later"
fizzy_1  | I, [2026-02-17T20:00:00.116134 #72]  INFO -- : [ActiveJob] [SolidQueue::RecurringJob] [1beba0d9-fb32-454f-8596-cc7d880017dd] Enqueued Notification::Bundle::DeliverAllJob (Job ID: 7b26b344-bd18-45fd-a0ec-64d9de63e721) to SolidQueue(backend) with arguments: 
fizzy_1  | I, [2026-02-17T20:00:00.116325 #72]  INFO -- : [ActiveJob] [SolidQueue::RecurringJob] [1beba0d9-fb32-454f-8596-cc7d880017dd] Performed SolidQueue::RecurringJob (Job ID: 1beba0d9-fb32-454f-8596-cc7d880017dd) from SolidQueue(solid_queue_recurring) in 16.84ms
fizzy_1  | I, [2026-02-17T20:00:00.101658 #72]  INFO -- : [ActiveJob] [SolidQueue::RecurringJob] [db8c6d80-5912-4aaf-adfe-27432c21ee43] Performing SolidQueue::RecurringJob (Job ID: db8c6d80-5912-4aaf-adfe-27432c21ee43) from (solid_queue_recurring) enqueued at 2026-02-17T20:00:00.013964074Z with arguments: "MagicLink.cleanup"
fizzy_1  | I, [2026-02-17T20:00:00.123683 #72]  INFO -- : [ActiveJob] [SolidQueue::RecurringJob] [db8c6d80-5912-4aaf-adfe-27432c21ee43] Performed SolidQueue::RecurringJob (Job ID: db8c6d80-5912-4aaf-adfe-27432c21ee43) from SolidQueue(solid_queue_recurring) in 22.05ms
fizzy_1  | I, [2026-02-17T20:00:00.133384 #72]  INFO -- : [ActiveJob] [Notification::Bundle::DeliverAllJob] [7b26b344-bd18-45fd-a0ec-64d9de63e721] Performing Notification::Bundle::DeliverAllJob (Job ID: 7b26b344-bd18-45fd-a0ec-64d9de63e721) from (backend) enqueued at 2026-02-17T20:00:00.102292348Z with arguments: 
fizzy_1  | I, [2026-02-17T20:00:00.136563 #72]  INFO -- : [ActiveJob] [Notification::Bundle::DeliverAllJob] [7b26b344-bd18-45fd-a0ec-64d9de63e721] Performed Notification::Bundle::DeliverAllJob (Job ID: 7b26b344-bd18-45fd-a0ec-64d9de63e721) from SolidQueue(backend) in 3.19ms
fizzy_1  | I, [2026-02-17T20:00:51.855340 #35]  INFO -- : [c1c5876c-e013-4a18-b78c-6e24faf507bc] Started POST "/1/cards.json" for 76.128.231.248 at 2026-02-17 20:00:51 +0000
fizzy_1  | I, [2026-02-17T20:00:51.857468 #35]  INFO -- : [c1c5876c-e013-4a18-b78c-6e24faf507bc] Processing by CardsController#create as JSON
fizzy_1  | I, [2026-02-17T20:00:51.857575 #35]  INFO -- : [c1c5876c-e013-4a18-b78c-6e24faf507bc]   Parameters: {"board_id" => "03fkrkifnofsagbec2scsxyc6", "card" => {"description" => "Stuff and things\n", "title" => "Stuff and things"}}
fizzy_1  | I, [2026-02-17T20:00:51.872261 #35]  INFO -- : [c1c5876c-e013-4a18-b78c-6e24faf507bc] Completed 500 Internal Server Error in 14ms (ActiveRecord: 2.3ms (11 queries, 0 cached) | GC: 0.6ms)
fizzy_1  | E, [2026-02-17T20:00:51.875831 #35] ERROR -- : [c1c5876c-e013-4a18-b78c-6e24faf507bc]   
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] ActiveRecord::RecordNotUnique (SQLite3::ConstraintException: UNIQUE constraint failed: cards.account_id, cards.number)
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] Caused by: SQLite3::ConstraintException (UNIQUE constraint failed: cards.account_id, cards.number)
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] 
fizzy_1  | Information for: ActiveRecord::RecordNotUnique (SQLite3::ConstraintException: UNIQUE constraint failed: cards.account_id, cards.number):
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc]   
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] 
fizzy_1  | Information for cause: SQLite3::ConstraintException (UNIQUE constraint failed: cards.account_id, cards.number):
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc]   
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] app/controllers/cards_controller.rb:21:in 'block (2 levels) in CardsController#create'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] app/controllers/cards_controller.rb:14:in 'CardsController#create'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] app/controllers/concerns/current_timezone.rb:15:in 'CurrentTimezone#set_current_timezone'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] config/initializers/tenanting/account_slug.rb:31:in 'block in AccountSlug::Extractor#call'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] app/models/current.rb:22:in 'Current#with_account'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] config/initializers/tenanting/account_slug.rb:30:in 'AccountSlug::Extractor#call'
fizzy_1  | [c1c5876c-e013-4a18-b78c-6e24faf507bc] config/initializers/true_client_ip.rb:20:in 'TrackTrueClientIp#call'

[pjeby]

So, it looks like accounts.cards_count was 10, though my highest card number was 26. I had recently noticed it started counting cards from 1 again, though I wasn't sure exactly when. I just thought it reused deleted cards. So I don't know if this dates back to the time of importing the account data, or if it's due to something else.

I've bumped the cards_count to 26, if it goes back down again at some point we'll know it's not the import that did it.

[monorkin]

Hey @pjeby, there was a bug in the import process and we didn't migrate over the card count.
I just deployed a fix for that, so this shouldn't happen in the future.
Thank you for reporting this!