When disabling Team Create in the main place, subplace instances do not refresh, leaving developers in a conflicted environment. This issue becomes prominent in larger studio settings where multiple developers work simultaneously.
Developers who aren’t monitoring the output log may unknowingly continue working on a conflicted branch, leading to progress loss upon attempting to publish. Developers will also lose progress if they exit their studio instance because the auto save feature also gives the same Conflict error. The only way to ensure progress is not lost is:
- Know you are in a conflicted branch, and exit / rejoin immediately.
- Download a copy
The error “Server Publish Failure: HTTP (409): Conflict” appears without clear explanation, causing confusion and potential progress loss if no backups are created.
System Information: 12th Gen Intel(R) Core™ i5-12400F, 32GB, NVIDIA GeForce RTX 3070 Ti
Beta Features:
Material Generator, Updated Roblox Controls, Video Uploads
Steps to Reproduce:
- Enable Team Create for a game.
- Create a subplace under the same game and enter it.
- Return to the main place (keeping the subplace instance open) and disable Team Create.
- Observe that the main place refreshes itself into a new studio instance without Team Create.
- Return to the subplace instance that remained open. Attempt to publish from this instance.
- You will encounter the error “Server Publish Failure: HTTP (409): Conflict”.
Expected behavior
You should not ever be put in a conflicted environment. There are a few possible ways to take on this:
-
When Team Create is disabled in the main place, all open subplace instances should refresh accordingly to prevent developers from unknowingly working in a conflicted environment.
-
A warning should pop up, or developers should be immediately kicked out of the affected studio instance with a message like “Team Create has been disabled! Please rejoin.” to ensure they no longer work on a conflicted environment.
-
Do not allow team create to be disabled if it detects any other developers still has an instance running. I would imagine something along the behaviors that you cannot ‘Publish to’ a game that has team-create enabled with a developer inside it (it doesn’t allow you and lets you know they have to exit before you’re able to publish).