#withapain

1 messages · Page 1 of 1 (latest)

ripe hatchBOT
fleet gulch
#

Hi there!

vivid jay
#

you do report timestamp, however

#

where does it end up? What I mean is this part:

        "end": null,
        "start": null
      },
fleet gulch
#

Can you share the object ID where you see this?

vivid jay
#

It is in the code above

#
      "id": "sis_1N6sKuHzzIMXxbBCy3oL5hbm",
      "invoice": null,
      "livemode": false,
      "object": "usage_record_summary",
      "period": {
        "end": null,
        "start": null
      },
fleet gulch
#

Thanks! Give me a few minutes to look into this.

dry robin
#

hi! it's a bit confusing but you get these null periods whenever we're trying to surface a period summary for the current period, before it's been invoiced

#

in the API ref it mentions

Since new usage records can still be added, the returned summary information for the subscription item’s ID should be seen as unstable until the subscription billing period ends.
and this is what it's referring to

ripe hatchBOT
vivid jay
#

In my case we have a billing_threshold. Let's assume it is met and customer needs to pay.

I assume at this point end will get filled.

What about start though? Does it get filled at that time as well?

chilly mountain