HTTP 409 (Conflict) when opening non team-create places with new collaborator permissions

[syntaxsyntaxsyntax (syntax)]

This has been an on-going issue with the new collaborator permissions for months and has been consistent with all groups that I have collaborator permissions in. If you try to access any places under a group with “Edit all group experiences” and “Edit & publish all group experiences” permissions, without those places having team-create on, you will not be able to access it and instead are prompted with the following error image:

This error only appears on places that do not have team-create on. Any places that do have team-create on will function as normal without this happening. Surprisingly enough, you can still publish through these places, just not edit them directly, which remains frustrating as I would prefer being able to edit any experiences quickly for rapid changes and fixes.

Expected behavior

I expect to be able to edit these places directly and not have to publish through them.

[EndoMarmot]

Experiencing this too.

[Herbz_Dev2106]

Unfortunately, I have also been experiencing this issue as well. As soon as I disabled Team Create and re-entered the place that I have been granted editing permissions to, I would keep encountering a HTTP 409 (Conflict). As of now, I am still encountering this issue even after uninstalling and re-installing Roblox Studio itself. Very annoying bug indeed.

[BPilot253]

I confirm this is also the case when trying to open a previous version of a place through the version history menu.

[EndoMarmot]

When trying to asset the place directly, i get the same error

https://assetdelivery.roblox.com/v2/assetId/16541340872
this happens on both v1/v2

{“errors”:[{“code”:409,“message”:“User is not authorized to access Asset.”}],“requestId”:“638797187586201540”,“IsHashDynamic”:false,“IsCopyrightProtected”:false,“isArchived”:false,“assetTypeId”:0}
{“errors”:[{“code”:0,“message”:“User is not authorized to access Asset.”}]}

these errors can be seen in my studio logs

2025-04-08T14:15:19.518Z,12.518865,6eacb000,6 [telemetryLog] ParallelDmTaskNames: RegisterCommandDataBridge;SoundJobManager-PreLoading;Package;PublishMediator-setupSignals;
2025-04-08T14:15:19.518Z,12.518867,6eacb000,6 [telemetryLog] PlaceSessionId: PlaceSessionScope:'cdbc5e8d-0eab-4958-bc30-95893f35ae3e-16541340872'
2025-04-08T14:15:19.518Z,12.518869,6eacb000,6 [telemetryLog] PerStateTraceId: 476d9adb-c00d-4721-a0d3-6afd45b71b53
2025-04-08T14:15:19.518Z,12.518871,6eacb000,6 [telemetryLog] WorkflowTraceId: 599bbdb8-0a1b-4089-b197-6169d77bd5d9
2025-04-08T14:15:19.518Z,12.518873,6eacb000,6 [telemetryLog] AllDmTasksSuccess: true
2025-04-08T14:15:19.518Z,12.518876,6eacb000,6 [telemetryLog] 'OpenPlaceDataModelTaskTelemetry' fields logging ends.
2025-04-08T14:15:19.520Z,12.520020,6ebd7000,6 [FLog::Output] Info: DataModel Loading https://assetdelivery.roblox.com/v1/asset/?id=16541340872
2025-04-08T14:15:19.533Z,12.533674,6f113000,6 [FLog::StudioDebuggerV2] DebuggerConnection(0x378850a10): Service provider changed (old 0x0, new 0x1420a35b0)
2025-04-08T14:15:19.533Z,12.533769,6f113000,6 [FLog::StudioDebuggerV2] DAPClient: Invoking method: setExceptionBreakpoints
2025-04-08T14:15:19.533Z,12.533827,6f113000,6 [FLog::StudioDebuggerV2] DAPClient: Invoking method: continue
2025-04-08T14:15:19.639Z,12.639690,6e1df000,12 [DFLog::HttpTraceError] HttpResponse(#127 0x318638220) time:139.9ms (net:139.9ms callback:0.0ms timeInRetryQueue:0.0ms)status:403 Forbidden bodySize:91 url:{ "https://apis.roblox.com/user-heartbeats-api/action-report" } ip:XXX external:0 numberOfTimesRetried:0
2025-04-08T14:15:19.639Z,12.639704,6f32b000,6,Error [FLog::UserHeartbeats] HTTP Request user-heartbeats-api/action-report failed: {"sessionId":"0f52601c-cf73-4336-8d29-173d345f362e","status":403,"message":"Unauthorized."}
2025-04-08T14:15:19.852Z,12.852022,6e0c7000,12 [DFLog::HttpTraceError] HttpResponse(#129 0x356673a20) time:331.6ms (net:331.5ms callback:0.0ms timeInRetryQueue:0.0ms)status:409 Conflict bodySize:75 url:{ "https://assetdelivery.roblox.com/v1/asset/?id=16541340872" } ip:XXX external:0 numberOfTimesRetried:0```

[weeek53]

How do you have access to this game? How is this game shared with you?

[EndoMarmot]

Creator roles via the community configuration. This is still an ongoing issue.

[weeek53]

Is this the toggle you are using

Do you have universeid and userids that this affects? Thanks

[EndoMarmot]

The creator of this post, a fellow developer of mine, SyntaxSyntaxSyntax - 78137915
Me - 4948213559, but this might change depending on my rank in the group
101waves - 1664450482 aka @101waves , a fellow developer of mine.

It doesnt work for this game

Clark County

[syntaxsyntaxsyntax (syntax)]

This is not the toggle we are using. As @EndoMarmot has specified in the reply above, we use Collaboration Roles to gain access to our production places. They show up under the following permissions set:

I want to emphasize again that the behavior we are facing is unintended as we are able to publish through them but not edit the places directly.

[EndoMarmot]

thanks for clarifying, my goat

[gion0015 (AirforceBackGion0015)]

Hello im gion0015, This has happend to my friend game: Nagi’s House.

He tried to collab me but failed.

I really think that you got uncollab or still collab we dont know.

Normally i have solution idk if it works: Try to uncollab and collab again press one of the configure or join the game and use shift + p if it does not freecam you have to say to your friends to uncollab and collab again, or if the configure is not working same thing say to ur friends to uncollab and collab again. and then try to refresh your recents or shared

[EndoMarmot]

Any update yet? This is still an ongoing issue that has severely hindered our team from working on the game.

I really appreciate your response.

[weeek53]

Thanks for the details here. I will be looking into this one.

[xGaLzZy (GaLzZy)]

Any update on this? I have the same issue with my Community’s Developer role…

[IAJ124adjwa (iceberq)]

The use of the new Roblox roles system appears to introduce this bug. As a temporary workaround, reverting to the legacy roles and permissions system is recommended.

[EndoMarmot]

Mr Weeek it has been 3 weeks since I was able to open the studio!!! Im cracking at the seams here man!

[weeek53]

Thanks for your patience, we have a fix ready for this and should be released this week. I’ll keep you updated.

[syntaxsyntaxsyntax (syntax)]

You are loved and appreciated and deserve everything in this world

[EndoMarmot]

Any update?