My team uses Open Cloud endpoints to publish our game, and yesterday (7/16/2025) we noticed that any place publishes via POST requests on https://apis.roblox.com/universes/v1/*/places/* no longer increment version numbers. Just to confirm some details, we are correctly setting the versionType parameter to Published, and verified our universeId and placeId parameters are valid. It appears that manually publishing in Studio does correctly increment the version.
We have confirmed that updated content is being published correctly (the request actually returns HTTP 200, indicating a success), but it is now very difficult to determine if our publishing workflow has actually succeeded or if there was some kind of unreported error.
Expected behavior
Open Cloud endpoints should behave the same way as their counterpart actions in something like studio, including incrementing version numbers.
Hi poli,
Thanks for reporting this issue. I did some investigation and it looks like if you publish the same binary multiple times, sometimes it will return the same version number. I was able to reproduce this using both the open cloud endpoint and in Studio. If the contents of the binary are different, it should always generate a new version number. In activity history though, it looks like we track all publish events, even when the version number is not incremented, which may be a bit confusing, but it is technically accurate. A new version is not created for the publish, but that is because the version uploaded is identical to the latest version. I hope this helps!
Thanks for you looking into this! I’m aware of the behavior in which the version number is not incremented when duplicate binaries are published.
Looking into this further, we actually did have different code saved on production than what was actually published. I confirmed with my team, and nobody manually patched / added anything to the production place, so the changes were almost certainly saved (but not published) via Open Cloud; this is actually reflected in our activity history for the whole experience.
I noticed that once I manually published the changes via studio, the changes were finally published and the version was incremented. I’m wondering if this indicates a potential issue with publishing from Open Cloud? Does setting the parameter of versionType to Published no longer trigger a publish?