Found in clubfinder-backend/migrations/archive/108_user_subscriptions_one_active_per_user.sql:4
production runs TWO clubfinder-backend instances (clubfinder-backend + clubfinder-backend-2, blue/green). Both run the every-minute NestJS @Cron schedulers independently. ensureAlwaysPremium() (always-premium test avatars) does check-then-insert: read status, INSERT a fresh subscription if the user has no active one. After a data wipe, both instances see "no active sub" in the same tick and both INSERT -> duplicate active rows (observed 2026-07-02:
Link this decision to the modules and files it governs.
All linkage saved.
Deprecate marks this decision as no longer current — existing references remain, but it stops being treated as the standard. It doesn't change any code.