Deleting localization table can result in a massive amount of HTTP requests

Currently if you plan on deleting/purging your localization table via the creator dashboard it will rapidly create HTTP requests to delete each individual entry rather than a single HTTP request for roblox to process this on the backend.
While this would be fine for games with only a few hundred entries, larger games which have been around for many years would accumulate hundreds of thousands of entries from auto scraping and such to the point where this reaches comically absurd levels.
As shown in the screenshots below purging a table for one of our games has hit rate limits and ballooned my browsers CPU and memory usage to the point that my browser went unresponsive and had to be ended via task manager.

Steps:

  1. Go to a place which you have edit access to
  2. Click the dropdown and click “Configure Localization”
  3. Click “Table Management”
  4. Press the delete button.
    If you have developer tools open you will notice it will make a PATCH request for each individual entry.


Expected behavior

I expect a sane API interaction that doesn’t result in the equivalent of a DoS attack.

15 Likes

Hello! This is a great point, and thanks for bringing it to our attention.

We will be looking into request batching to resolve this issue for the larger tables, and follow up here once we have resolved the problem.

I can confirm this is still an issue.