DataStore Error 509 on ProfileStore — "Data Store operations blocked while running on a Personal RCC"

[NoobMustafaHD (UnrealDev)]

Hello,

I’m currently using the ProfileStore module to manage player data in my Roblox experience. While testing, I encountered the following DataStore API error:

[ProfileStore]: DataStore API error (STORE:TEST; KEY:SESSION_757435813) - 509: Data Store operations blocked while running on a Personal RCC to prevent possible data corruption.

This error consistently appears during testing in one of my projects, while the same framework and scripts are functioning without any issues in other games using ProfileStore.

Steps I’ve taken so far:

• Verified that API services are enabled in the game’s settings.
• Confirmed that ProfileStore is correctly initialized and session keys are structured identically across my experiences.

Despite these checks, the error persists. My assumption is that the environment is defaulting to a Personal RCC (Roblox Cloud Client) server, which restricts DataStore access for safety reasons.

I’d appreciate any clarification or guidance.

Thank you in advance for your time and assistance.

[metatablecatmaid (metatablecat)]

Personal RCC refers likely to a local running version of “Roblox Compute Cloud”, their server software.

From what I’ve seen, this is an issue with DataStores themselves, not your code.

[Ill91 (ill)]

Getting the same issue myself, can’t test Datastore in Studio at all.

[agKing_21]

I’m also getting this issue at the current moment

[Claym1x (Emma)]

Try restarting/updating Roblox Studio

Strange studio error while saving data with datastore

I’ve just gotten this problem today, but only seems to be on a certain computer. Maybe your computer has something to do with it? EDIT: It’s happening on both now. EDIT2: I think I found the solution, it does this whenever there’s an update, try updating studio. It worked for me.

[NoobMustafaHD (UnrealDev)]

My Studio was fully up-to-date, and I had already tried restarting my computer. After further investigation, I discovered that the issue was caused by the experience being a group-owned experience.

Even though API Services appeared enabled in the settings, they were not actually active. It seems like toggling the setting had no effect for me as a developer, and the experience owner (group owner) had to manually reset the API Service setting for it to take effect properly.

I’ll be reporting this as a Studio bug. Thank you to everyone who took the time to help and respond — much appreciated!