As many of you will know, Roblox is moving to per-Experience limits for Data Stores starting 2026.
The question I have concerns the behavior of these limits when an experience is abruptly shut down. In theses cases, it is standard that we use BindToClose to save any unsaved data just before the server closes. This will yield the server closure by up to 30 seconds.
Say that, in some extreme case, the server is still working through the data cache 15 seconds after BindToClose was originally fired. At this point, presumably all the players are considered disconnected and (maybe?) the data store budget is adjusted accordingly.
In regards to the budgeting, this was previously never a concern to me. As currently, the server itself has a generous 60 read & writes to finish up the last data store requests - regardless of how the concurrent player count budget changes.
However, we will now completely be losing the per-server limit. So in the case that an experience has all servers abruptly shut down - at what point is the CCU budget adjusted? If it is immediate - then we would just be left with 250 read & writes for the entire experience to save any cached data. This would completely fail at scale.
So I am wondering if anyone has information on when, exactly, Roblox adjusts the CCU budget? I cannot seem to find this documented anywhere. Is there a grace period of at least 30 seconds (to match BindToClose) after a user disconnects?