Data Stores Versioning Changes are Going Live

[CoffeeBurg3r]

Hi Creators!

This is a follow-up to the Upcoming Changes to Data Stores Versioning announcement. These changes to Data Stores versioning are now being released globally. Here’s what that means for you:

1. Fewer, Optimized Versions: Now, only the first write to each key in each hour creates a versioned backup of the previous data. All successive writes to a key within the same hour permanently overwrite the previous data.

2. Versions Available Longer: Non-current versions now expire 30 days after they are made non-current. This is always longer than the current behavior.

These two changes are in the process of being rolled out to all experiences. You may notice some of your experiences receive these changes before others. We expect to have all universes fully enrolled in the coming weeks.

3. Data Stores Snapshots: CreateUniverseSnapshot is now available on Open Cloud. You can view the new endpoint here.

After a snapshot, the next write to every key in the experience will create a versioned backup of the previous data, regardless of the time of the last write. As a reminder, we encourage you to use this method before publishing any experience update which changes your data storage logic.

Please let us know if you have any questions or encounter any issues. We look forward to continuing making Data Stores versioning a better, easier to use tool for data recovery!

The Data Stores team

[TomPlays63 (Tom)]

This is honestly amazing, thank you roblox!

[lostresosostedyIII (Server)]

Love it, now we have improvements which I really needed!

[JunisL0L (clown_junis)]

Sweet! Loving the new updates

[VideoBlogsPro5 (FBI)]

Great! We need more updates like this.

[KultDeeri (Kult)]

Thank you so much Roblox! I very much appreciate it.

[Bulldo344 (LawMixer)]

Hey, has this already been pushed to Open Cloud endpoints or are we still waiting on that? I know CreateUniverseSnapshot has, but anything else? Amazing update, thank you guys!

[CoffeeBurg3r]

Once your experience is enrolled in changes (1) and (2), you’ll see the changes on both Open Cloud and Engine endpoints at the same time.

[Raki3dd (Raki)]

@CoffeeBurg3r

After a snapshot, the next write to every key in the experience will create a versioned backup of the previous data, regardless of the time of the last write. As a reminder, we encourage you to use this method before publishing any experience update which changes your data storage logic.

The truth is that creating a backup copy with the previous version of the data is quite good from my point of view so as not to lose anything by modifying the data storage logic.

¡Thanks, as always!

[MightyPart (Mighty)]

Openblox (my OpenCloud wrapper written in typescript) now supports the new CreateUniverseSnapshot endpoint.

Example

import "dotenv/config";
import { setConfig } from "openblox/config";
import { StandardDataStoresApi_V2 } from "openblox/cloud";

setConfig({ cloudKey: process.env.CLOUD_KEY })

;(async () => {

  const { data:snapshot } = await StandardDataStoresApi_V2.createStandardDataStoreSnapshot({ universeId: 5097539509 })
  console.log(snapshot)

})();

docs: createStandardDataStoreSnapshot – Nextra

[bg9]

Is there a way to lower the hour limitation for new versions to save? I prefer the old behavior where it updates on each save because it helps when pinpointing where data loss occurs.

[ivan866_z]

how do i start a new Universe? does it allow sharing DataStores between places?

[PrestigeToken (token)]

long overdue,
glad it’s finally here!

[CoffeeBurg3r]

This new behavior will apply to all experiences. We do acknowledge that you lose a level of granularity when debugging issues, but this change is necessary to continue improving the versioning system.

By using snapshots when you update your experience, you can ensure you have the most recent pre-update data available to revert to if the update leads to data loss. If the data loss occurs outside of an update/snapshot, you will still have previous versions at most one hour “stale”.

We’re investigating how we can give creators more control over this system. If you have any other ideas or insights, please open up a feature request!

[CoffeeBurg3r]

Yes! Data Stores share data across all places in an experience. Experiences are sometimes referred to as universes.

This article has more information on publishing multiple places to the same experience/universe.

[Usering]

Would it be possible to retain all versions for a key within 24-48 hours of a save? I imagine many of us could forget/may never know or understand the concept of making a data snapshot.

[xenstence]

When will automatic retry finally get implemented?

[CoffeeBurg3r]

@Usering

Would it be possible to retain all versions for a key within 24-48 hours of a save? I imagine many of us could forget/may never know or understand the concept of making a data snapshot.

For now, the one-version-per-hour rule will be applied. We’ll keep this feedback in mind for the future.

Even if you don’t use snapshots, you’ll still have access to one version each hour, including the most recent version.

[CoffeeBurg3r]

Hi! Which method are you referring to? We do make recommendations for which errors to retry on in our error code reference.