#dineshkumar_docs

1 messages · Page 1 of 1 (latest)

spiral bluffBOT
#

👋 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/1336974619348828212

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tidal stag
#

meter id is : mtr_test_61QdPBXZqM51mjVfy41BUmBAZBIgtD4S

bitter sigil
#

Meter and Meter Events are two different things. Meters specify how to aggregate Meter Events over a billing period.

Your question is about updating the Meter Event value whereas the example object ID is Meter.

Which one do you want to update - Meter or Meter Events?

#

Which specific field would you like to update?

tidal stag
#

i want sent to aggregate value monthly once from nodejs background process like below code

#

const meterEvent = stripe.billing.meterEvents.create({
event_name: eventName,
payload: {
value: payValue,
stripe_customer_id: stripeCustomerId
}
});

#

by mistake payload value not sent monthly once or sent twice, thrice and etc, how will manage this?

#

We want to update meter event.

#

specific customer aggregate payload value is sent only once per month, this is requirement, please help to achieve this..

bitter sigil
tidal stag
#

no i got below error

bitter sigil
tidal stag
#

Events can only be canceled for up to 24 hours. Event with identifier f4cc9f42-2c23-48d3-b2e0-f0f2d5f0c6be was received at timestamp 1738573322 so it had to have been canceled before 1738659722 but it is currently 1738756216.

#

request id is - req_fzjD9TZXRn6r42

spiral bluffBOT
bitter sigil
#

Thanks for sharing the request ID. Unfortunately, this is the limitation of the meter event adjustment that only meter event submitted in the past 24 hours can be canceled/adjusted. Adjusting the meter events that past 24 hours is on the roadmap, but we don't have any timeline to share.

I'd recommend ensuring that the meter event is submitted before submitting again in your own database

tidal stag
#

sorry, please explain with more details

#

i understood this "I'd recommend ensuring that the meter event is submitted before submitting again in your own database"

lusty galleon
#

The event you want to update is too old to be updated – we limit that to events created within 24 hours

tidal stag
#

by mistake this will sent multiple time, we can't correct?

lusty galleon
#

As the error describes:

Events can only be canceled for up to 24 hours. Event with identifier f4cc9f42-2c23-48d3-b2e0-f0f2d5f0c6be was received at timestamp 1738573322 so it had to have been canceled before 1738659722 but it is currently 1738756216.

#

You maybe create a new event with a negative value to make the necessary adjustment. Can you try that?

tidal stag
#

ok i will check my code and if any doubt i will rech here...