Closing a server through the Server Management dashboard returns RobloxMaintenance instead of DeveloperShutdown as CloseReason

Bug Reports Engine Bugs
,
1

Fairly self explanatory bug. When we close our servers with the Shutdown Server button within a server under the Server Management dashboard, it passes Enum.CloseReason.RobloxMaintenance to BindToClose instead of Enum.CloseReason.DeveloperShutdown.

We verified this by creating a webhook that logs the reason when we shut a server down, of which yielded RobloxMaintenance.

Looking at the server management dashboard itself, Roblox lists these servers’ statuses as “Restarted,” so I wonder if this might be an issue with closing subplace servers specifically (as when you close a subplace server it automatically sends you to a server in the main place.)

Expected behavior

We would expect the server to instead close with DeveloperShutdown as the CloseReason.

2 Likes
2

i can confirm i noticed same exact issue in my experience

we have an option for moderators to remotely shutdown individual servers thru our discord bot in case everything goes wrong and it uses roblox shutdown api the one a developer sees while being able to shutdown individual servers

anyways straight to the point after using same exact API to shutdown servers it just does “RobloxMaintenence” instead of “DeveloperShutdown” and we can see that because we also have a join logs webhook (not a problem for us because our game is small so it doesn’t get spammed at all)