Unable to publish an update from our testing game to the main game

We’re trying to push the halloween update for Super Golf and we keep getting the errors “Save Failed” & “Publish Failed”. We cant publish from our testing game file to the main game file no matter what.

We tried to publish from the testing game file to a brand new place, which worked, and then attempted to publish from that new game to the main game and that still failed. There seems to be something wrong with the Super Golf universe/sub places.

Steps for repro:

  1. File > Publish to Roblox As…
  2. Select Super Golf, then select the Map Builder subplace (we start with this one first but it seems like all places are affected)
  3. We then get the “Save Failed” error
  4. Clicking the Retry button keeps giving us the same errors

Read private content notes for the link to the games & a gif showcasing the issue

Expected behavior

Once published, there should be no errors and the update should be live.

A private message is associated with this bug report

1 Like

Thank you for bringing this issue to our attention. We understand the inconvenience and are actively working on a solution. In the meantime, here’s a workaround that should allow you to publish your update successfully:

  • Download a copy of the game.
  • Close all open Studio windows.
  • Open the downloaded copy directly from your downloads folder.
  • Publish this version to the target game.

This should serve as a temporary solution for impacted creators. We’re prioritizing a full fix during business hours, as the necessary changes are complex and high-risk to implement over the weekend. We appreciate your patience and will update you as soon as we have more information.

5 Likes

We have had the same issue on our game for the past few weeks. We’ve used the “download copy” workaround as well.

We publish from our “staging” game to live, similar to OP. @KnightGaladeld, I’ve sent a message with the links to our staging and live game here

Hoping having another example of the issue makes debugging for you guys a bit easier.

2 Likes

Quick update, our engineering team has resolved this issue. Thank you all for patiently waiting for a solution.

3 Likes

Could this fix have possibly caused this issue?

1 Like