Files
remnawave-bedolaga-telegram…/app/services
Fringg cea7260a85 fix: apply same create-vs-update fix to renewal and purchase flows
Same bug as the tariff purchase fix: in multi-tariff mode, new
subscriptions without remnawave_uuid incorrectly fell back to
user.remnawave_uuid and called update instead of create.

Fixed in subscription_renewal_service.py and purchase.py to use
the same _should_create pattern based on mode.
2026-04-15 13:17:35 +03:00
..
2026-03-26 10:34:14 +03:00
2026-03-26 10:34:14 +03:00
2026-03-26 10:34:14 +03:00