Problem
As mentioned in the title, the issue with getting an Internal Server Error when saving a place to the Roblox cloud has returned. The place does not update in the cloud as the version number does not change. I haven’t tried it with publishing, but I suspect that the issue is there as well. This is an intermittent issue and retrying the operation for a second time usually works. When saving an unpublished place to the local computer, the error never happens.
At this point, since the error has just started to reappear, I do not know if there’s a pattern associated with this return of this issue or if there was some kind of network issue. Considering the fact that the error message is specific, I’m leaning to it being a server issue. This appears to be related to a previous bug report that I had on this matter.
HTTP 500 = Internal Server Error
Additional Information
Parameter | Value |
---|---|
Problem Area | Studio |
Problem Component | Saving and Publishing |
First Noticed | 8 Jun 2024 |
Priority | Critical |
Impact | High |
Annoyance Level | Moderate |
Game ID | 5207881632 |
Place ID | 15112688736 |
I have included both the published game and place Ids that I am experiencing the issue with.
The beta features that I have enabled are as follows:
- Assistant Preview
- Material Generator
- Material Picker
- Notched Screen Support
- Texture Generator
- Updated Docking System
As for plugins, I have a bunch that are installed, but very few are enabled. The ones that are enabled are listed below with links to their details page on the Roblox store website:
Expectations
What I expect to happen is that there are no errors when saving a place to the Roblox cloud.
Visuals
Reproduction
To reproduce the issue, perform the following steps:
- Open a published place in Studio.
- Make some changes.
- Save the place to the Roblox cloud.
- Observe the results.
The problem happens intermittently, and only when saving a place to the Roblox cloud. I haven’t tried publishing, but I suspect there’s an issue with that as well.
Files
Log files attached in private message.
A private message is associated with this bug report