another thing here. Do you remember the place you are editing in studio where you see the second screenshot? Since you only do “Publish As”, I suppose you had the staging place open. But somehow studio confusingly say “Published changes in Oaklands”, which is the production place. Is this correct?
2 Likes
Thanks for the follow up. Since I made that post, that specific error has subsided, but I’ve actually been seeing a whole new one pop up whenever I press “Publish to Roblox” or Studio attempts to auto-save my work.
I can’t reproduce right now, but I believe the error is something along the lines of “HTTP 503 - attempted to publish to Team Create but Team Create is not enabled for this place”.
2 Likes
Yo wait this is actually real, i’ve had this happen to me once or twice but then it just lets me publish after 1-2 fails. Such a weird little issue.
1 Like
Hi. We believe we have identified the cause of this issue and are working on a fix. Based on our analysis, you would get “Attempted to upload to a Team Create place, but Team Create is not enabled” 409 error when you do a manual save/publish after “save/publish as”. The error would go away if you retry again. Sorry for the inconvenience. Let us know if you encounter cases different from the one described above.
2 Likes
Update: we made some changes to correct the misleading message, so it should now show “[place name] save failed” if you run into the same issue again. let us know if you are still seeing “Attempted to upload to a Team Create place, but Team Create is not enabled”
2 Likes
Still experiencing this issue on a different sub-place under the same game. It still seems to consistently fail after we publish once successfully.
1 Like
Hey. We are working on a fix that would hopefully help with the issue. Will update you on it!
1 Like
Hi. Thanks for the patience. We just rolledout a fix and believe have fixed the behavior where after publishing finish, studio goes to the new place. Let us know if you are still seeing any issue.