# Overlapping Subscriptions Issue

**URL:** <https://meta.discourse.org/t/overlapping-subscriptions-issue/245559>\
**Category:** Product Support\
**Tags:** subscriptions\
**Created:** [November 14, 2022, 7:20pm UTC](https://meta.discourse.org/t/overlapping-subscriptions-issue/245559 "2022-11-14T19:20:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [November 14, 2022, 7:52pm UTC](https://meta.discourse.org/t/overlapping-subscriptions-issue/245559/2 "2022-11-14T19:52:03Z")

</div>

Maybe you can change the group associated with the old subscription with a bogus group. Then when that expired, they’d get removed from the bogus group. They’d stay members of the group even after their old subscription expired, so you’d periodically need to go and manually remove those people from the group.

Another idea that I had was to do something like the below, but I’d have to look at the source to figure out how todo it, and I think the above solution should work and not require knowing the internals.

```plaintext
   old_subscriptions=SubscriptionOrSomethingLikeThat.where(somefield: 'sub_xyz')
   old_subscriptions.destroy_all

```

I think that the “right” way to do it would have been to create a new group for the new subscription and add it to the associated categories. That too would have been a bother.

---

_[View the full topic](https://meta.discourse.org/t/overlapping-subscriptions-issue/245559)._