Memory stores do not support 31-day month use cases

As a Roblox developer, it is currently too hard to take advantage of memory store for time-based features where we need data to remain for a 31-day month. The maximum timeout is currently 30 days and there are 7 months with 31 days - that’s more than half the number of months in a year.

If Roblox is able to address this issue, it would improve my development experience because for features that require data to last only for the current month (e.g. monthly leaderboards), I would be able to have the data persist for the whole month and then expire right after. It would prevent me from needing to use data stores and consume budget unnecessarily as a feature like leaderboards needs low latency and high throughput and I need that data store budget for other critical persistent features. Additionally, it would save me the engineering headache of needing to determine how to extend the expiry time on my memory data for a single day.

47 Likes

Thanks for the feedback! We’re looking into this and will circle back when there’s an update.

3 Likes

Appreciate your feedback! We have updated the max expiration time from 30 days to 45 days. The change is also reflected in the memory store article: Memory Store. Please do note the GDPR warning on that page. Let us know if you have any questions!

13 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.