createdTime response field completely missing from Datastore Set Entry opencloud api(?)

Bug Reports Cloud Services Bugs
,
#1

Out of nowhere, earlier today both of my bots that use the rblx-open-cloud library for Python stopped working. After some investigation, it looks like the createdTime field is missing from the Datastore Set Entry endpoint response, causing an error in the library.

image
image1674×544 122 KB

The docs still mention this as part of the response, so I’m assuming this is a bug?

image
image1510×919 78.8 KB

This started happening approximately 24 hours ago, but thought it was a temporary Datastore outage or something until I looked closer.

EDIT: Just noticed that there’s a field called creationTimeInTicks in place of the createdTime field. Assuming maybe some code got pushed that didn’t mean to get pushed?

4 Likes
Rblx-open-cloud - Roblox Open Cloud Wrapper for Python!
#2

I can confirm this issue, for extra clarification the library (and therefore Maui) is using version 1 of the data store API. I should probably migrate to version 2; however we assume it is a bug because it is expected that existing APIs do not have breaking changes.

The library uses this endpoint:

https://apis.roblox.com/datastores/v1/universes/{universeId}/standard-datastores/datastore/entries/entry

Expected Response:

{
    "version": "08DB3CB11454A4D0.000000000C.08DD3471D6594F22.01",
    "deleted": false,
    "contentLength": 14,
    "createdTime": 1736842224,
    "objectCreatedTime": 1736842224
}

Actual Response:

{
    "version": "08DB3CB11454A4D0.000000000C.08DD3471D6594F22.01",
    "deleted": false,
    "contentLength": 14,
    "creationTimeInTicks": 638724385688604450,
    "objectCreationTimeInTicks": 638170503451026640
}

Frequency: Consistent (seems to always happen)
Reproduction steps:

  1. Send a request to https://apis.roblox.com/datastores/v1/universes/:universe/standard-datastores/datastore/entries/entry with valid arguments and api key provided.
  2. Observe that createdTime is not returned.

I have confirmed this is not an issue of the library and is replicable without use of an api wrapper.

#3

Hello, this should be resolved. Please let me know if you still see the same issues. Sorry about that.

3 Likes