Skip to main content
Committed ⭐️⭐️
September 24, 2024
Parked

DatapointsSubscription: Expired cursor

  • September 24, 2024
  • 12 replies
  • 174 views

I understand that updates older than 7 days may be discarded from the endpoint, which is perfectly fine. However, I’m wondering if it’s possible to determine when a cursor is older than the given limit, since updates older than 7 days are discarded. Based on my understanding of your Subscription API, it would simply continue iterating over the oldest available updates on the endpoint, which could result in missing important updates that occurred between the time of my cursor and the current oldest update.

 

For the Subscription API to be fully functional, I believe it's essential to either receive a notification or an exception when using an expired cursor, be able to determine the age of a cursor, or somehow be assured that iterating from a cursor won't lead to lost data. Knowing the age of the cursor would be preferable, as it would allow us to gauge how much margin we have, but it should also be possible to receive a notification if an expired cursor is being used.

 

Is this currently possible, or are there any plans to implement such a feature?

12 replies

Active ⭐️⭐️⭐️
October 3, 2024

Thanks.

Also, as always, don’t trust the cursor format, we change it whenever we see a need for it.

We’re very well aware of the problems with poking at internal state/implementation details, but in the absence of a proper way to do this we would like to see if this can work as a heuristic.

Also, detecting that you’ve done a change should be fairly trivial: We assume your new (if this happens) format will not be anywhere close to decoding to a sane value on our side.

Thanks for your swift response, we hope to see a proper way to check this soon!

Lead Product Manager
July 13, 2025

As we’re evaluating the roadmap for Time Series during Q3, 2025, I’m parking this request until I’ve had a chance to assess.