#alexg_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1245847888899342428
đ Have more to share? Add details, code, screenshots, videos, etc. below.
Hi there!
hello
I see what you mean
so as you see here this one customer has two subscriptions "Cloud Seats" which are tied to the same price/meter
but pertain to two different instances of the software
you send usage and it records to both subscriptions
Since a Subscription is tied to a Price, and a Price is tied to a Meter, then all Meter Events will propogate down to the customer's Subscriptions that use that Price
Other than creating a separate Meter + Price, no
would that be considered bad practice? I assume so
Not every customer but every customer who has more than one usage-based Subscription where you want to track usage independently across subscriptions
ok i might have to use the legacy usage then
as every customer will have this
i also considered just having one metered subscription per customer, but that causes an issue with tier-based pricing
ie, the first seat is free, any seat after that you pay for
but if they have two projects, tied to one metered subsription then the first seat for each project will automatically put them over the threshold
A not-so-feasible workaround could be to create multiple Customer objects, each with a single usage-based Subscription
This will cause issues with our existing set up
Another option in this instance is to only report usage over the threshold
it's going to have to be either that or legacy usage
I'll share this feedback with our team