have a test game rated 18+ (questionnaire set to maximum for age restriction).
While testing “Migrate to Last Update”, I initially thought a script might be interfering. I deleted all scripts and code from the game. Despite this, using Migrate to Last Update still results in players being disconnected with Error Code 301.
The migration is supposed to complete and send all players to a new, updated server, but it fails, and automatically kick all players with the error
This indicates the issue comes from Roblox Cloud DataStore migration systems, not from any user code.
Expected behavior
The Migrate to Last Update feature should complete successfully.
All players should be moved to a new, updated server reflecting the latest version.
Hi, could you please give me some more context to help you debug this issue. Could you please give me a placeId and maybe a recent log of this happening?
I will try to see if I can reproduce this as well. Thanks!
I’m experiencing the same issue in my 18+ game. I deleted everything and tested again, but every time I restart the server, instead of migrating, it disconnects all players.
After finding this post, I reproduced the steps one by one, and it seems that once you submit a maturity label for age restriction, server migration stops working entirely.
Here’s what I tested:
I created a brand-new empty place and published it.
I joined the place, added something in Studio to trigger an update, then restarted it from the server management page. The server migrated with no issues.
After that, I changed the minimum age in Access Settings to 18+, submitted the maturity content, and enabled Strong Language.
I rejoined the game, made another small change, and published it again.
When I restarted the server after these age restriction settings were enabled, it disconnected the entire server instead of migrating it.
