#tidymince_docs
onyx turretBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- tidymince_usage-based-sub, 4 minutes ago, 7 messages
rigid siloBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1243497410827780157
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
azure surge
Subscription id is sub_1PJbn2IPsU8bKnjXcAsvmqh1
quartz egret
So you're querying if/why usage is reset if an associated item is removed?
azure surge
Yes
And also which usage metric events are considered when creating a new subscription
quartz egret
And also which usage metric events are considered when creating a new subscripti...
I don't understand the question. You'd report usage after the start of the sub/period – we'd only bill for usage reported in the period
azure surge
What if I have metric events before creating the sub or before the start of the sub period? I'm wondering if its either:
- considering all events after creation of the sub and after the start of the sub period
- considering all events after the start of the sub period
In the second case it's possible to create a sub covering usage in the past, in the first it isn't
*meter events
The reason I'm asking is that I built the integration to push meter events and we'd like to migrate customers to automated billing and this might involve billing them for usage in the past for which we have pushed meter events already and I'm wondering if it's possible or we'd need a different approach
quartz egret
Sorry, what are 'metric events'?
Ah, you corrected
I don't see why you can't retrospectively report the usage?
azure surge
We have a pipeline that is pushing meter events when the service is actually used and it would be convenient to setup the integration to do this and then create subscription as a separate step both for testing but also to make it easier to switch from manual invoice (what we have now) to automated
Apologies for the late answer (for some reason I'm not getting notifications from discord)
I just want to know the limitations in setting up a subscription for a meter with existing meter events
And decide on the approach we will take based on that
quartz egret
It doesnt work that way is my understanding. We'd only bill for usage on the metered reported after the subscription was created/started