No data stores found after deleting over 2k datastores (6 remaining)

Bug Reports Creator Hub (create.roblox.com) Bugs
1

My guess is that it still try to fetch the delete ones, despite not showing them… making the list paginated

image
image982×524 18.4 KB

Page URL: https://create.roblox.com/dashboard/creations/experiences/508099649/data-stores-manager?filter_Text=DataStoreService

2

Hi there Symlat,

Thanks for raising this issue.

First, I’d like to explain the root cause of the issue.

The underlying cause is that the Data Stores Manager relies on the ListDataStores Open Cloud endpoint to populate the list.

When the query parameter showDeleted is set to true, the operation will only check up to 512 data stores. If all checked data stores are deleted then it will return an empty list with a page token to continue iteration. This causes the behavior you noted in the bug report.

Now, I’d like to explain a resolution.

While it’s not possible to remove the 512 limit (since it protects our backend servers), I do believe two action items are warranted:

  1. The 512 data stores limit should be documented on the ListDataStores Open Cloud API documentation.
  2. The Data Stores Manager frontend should show a descriptive error message when an empty list is returned with a cursor to continue pagination.

I’ll work on adding both of these and post a resolution here when done. Otherwise, can you please let us know if you have any feedback on these action items?

Thanks!

2 Likes
3

Hello!

Thanks for the explanation.

Since it’s using OpenCloud’s endpoint, when we have the “Show Deleted?” toggle on the list toggled off, the argument &showDelete=false on the open cloud query should be set to false.

This should then only return the non-deleted datastores. Saving bandwidth for both the users and Roblox wihle fixing this issue

EDIT: So I ran a quick script to confirm what I said above about fetching with showDeleted=false, this was the result, which is what I would expect to see in the list:
image

Basically this means that right now the fetch call is done using showDelete=true (or absent) whether or not you have it enabled, then the filtering is done directly on the frontend part

4

Hi there Symlat,

Apologies, let me revise my original statement.

When listing Data Stores with showDeleted=true the operation will always return the number of Data Stores requested as long as they exist, up to the maxPageSize indicated on the request, which defaults to 10 and is capped at 100.

When listing Data Stores with showDeleted=false (or omitted) the operation will only check up to 512 data stores. If all checked data stores are deleted then it will return an empty list with a page token to continue iteration.

That said, I expect your script should have returned an empty list for the first call to ListDataStores on your game. Can you confirm that is true? If so, that is the intended behavior.

1 Like
5

Hello!

You’re right, it shows that it makes 3 calls (original + 2 next_token call) to get all of them
image

In that case, for the second point you made earlier

Would there be a way to avoid the changing page entirely? I just feel like it’d be cleaner

Also I know with 2k datastores its a pretty extreme and rare case, so if it’s not worth the effort it’s 100% understandable

6

Hey Symlat,

Sounds great! :slight_smile:

To your point, this issue is fairly rare, so we won’t be able to prioritize this at the moment.

1 Like
7

Hey there Symlat, we’ve gone ahead and completed the two items.

  1. When pages remain (but the current page is empty) there is now an additional hint displayed on the Data Stores Manager: “No data stores found. Use the next button to continue pagination.”
  2. We’ve updated the ListDataStores documentation with details on the 512 limit.

I’ll close out this ticket for now. Let us know if you have any more issues!

2 Likes
8

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