#bbqcokefan

1 messages · Page 1 of 1 (latest)

quiet apexBOT
trail atlas
#

Can you share a request id where this happened?

obsidian urchin
#

Sorry, where can I get the request ID?

#

I found it: "req_mJMFQwefmm0bCY"

trail atlas
#

That's not what happened there

#

You set quantity for that subscription item to "1"

#

And now it's 1

#

You can see for yourself in the dashboard there

obsidian urchin
#

But my dashboard shows the "QTY" for the upcoming invoice to be at 229, not at 1.

trail atlas
#

You shared the wrong request id then

#

Oh wait

#

This might just be an issue with the dashboard

obsidian urchin
#

Okay, that would explain things. How would I know though if a created invoice will contain the right amount? I am not sure what to trust right now.

trail atlas
#

Still looking

#

I see what you're talking about now

#

I'll need to get a colleague to look at this with me. Bear with me. Unless I'm missing something, this looks worrisome

obsidian urchin
#

Yeah, I hope this is a problem on my end. Is there any way I can correct the amount quickly? The invoice willl be generated in a couple of hours in the right amount should be 37, not 229.

trail atlas
#

We're looking right now

obsidian urchin
#

Okay, thank you!

quiet apexBOT
trail atlas
#

Because of that, usage is always summed

#

When you pass "Set" on a usage record with aggregate_usage=sum, then you just set usage at that specific timestamp

#

You'd need aggregate_usage set to last_ever for you to be able to override usage for the entire period by creating a usage record with set with a more recent timestamp to override everything

obsidian urchin
#

So can I update my price to behave this way? Or would I need to create a new one?

trail atlas
#

You'd need a new one

obsidian urchin
#

Okay that worked, thank you very much!

#

I am still a bit confused though and I believe this could be clarified more in the docs. In my opinion "set" should not work if "sum" is used.

trail atlas
#

So it's designed that way so that you can use "Set" to override individual usage records in the past at a certain timestamp

#

(if you have aggregate_usage = sum)

#

But agree it could be clarified a bit better