Subscription editing bug or inconsistency

Not sure if this is the proper place to report (perceived) bugs, but here we go.

When I create a new Subscription in HS Commerce, with start date today, it receives the status “Active”.

Now, when I want to edit the subscription right after, a message appears saying “This subscription has expired. You can only edit active subscriptions.”.

Strange, considering that “Active” and “Expired” are two valid but obviously different subscription statuses.

Despite the error message, you can actually continue and edit the subscription, but you can’t save any changes.

Not sure what the intended functional behaviour is supposed to be, but it doesn’t seem to make much sense you can’t edit an active subscription. Even if there’s some logic reasoning behind it, the UI is very confusing to say the least.

It also seems something that didn’t occur last week (but not 100% of that).

An additional finding:

Once the initial invoice for the new subscription is marked as “Paid”, there’s no longer the option to edit the subscription.

Why should I not be allowed to update an active (and paid) subscription? Is it because I try to do this on the same day as the start date of the subscription perhaps?

Hey, @Pinne :waving_hand: For bug reports and other product issues, opening a support ticket is likely your first best step. — Jaycee

Thanks @Jaycee_Lewis

The chatbot’s instructions for reporting issues seem outdated though. Just click the tiny question mark in the top navigation bar.

This discussion lead me towards the root of the issue: https://community.hubspot.com/t5/CRM/How-do-you-should-we-use-quot-term-quot-in-line-items/m-p/607508

The Product’s ‘term’ property was misinterpreted. Setting it to ‘12 months’ automatically ends a subscription 12 months after the start date, and is unrelated to the billing frequency. So if you have a subscription service that automatically renews year after year, just leave the Product Term empty.

Having said that, the situational warnings/messages shown in the UI are highly confusing.