I am using the OpenCloud API (https://apis.roblox.com/cloud/v2/users/USERID) to fetch a user’s profile. Unfortunately, whenever I try to set the value of the local secret’s key, it doesn’t save. I tried this multiple times with other keys and it still doesn’t work.
Hi @7eoeb, thank you for reporting the issue. I am trying to reproduce it. Could you please confirm whether jFYTX...SbHNB is the full content of secret you are saving? If not, would you mind send us privately the complete value?
Also, please note that the New Value input box will always appear empty, in case you were expecting it to be pre-filled.
The API key shown in the video was regenerated several days ago.
Yes, I know the New Value box will be blank.
When I set it the local secret and run the Http request, it returns:
"{"errors":[{"code":0,"message":"Invalid API Key"}]}
Thank you for providing the local secret value privately. You also mentioned a workaround where creating a new place and adding this local secret to that new place works. That’s very helpful information.
Could you also share with us the log files by following this these steps?
Close Roblox Studio.
Empty the log folder.
Open Roblox Studio, reproduce the error, then close Roblox Studio again.
Go back the log folder and send us all the newly generated *.log files.
Hi @7eoeb, we’ve improved Studio logging to include more information about local secrets. Would you mind installing the latest Studio build, reproducing the error, and sharing the log files with us again? This bug has been tricky to reproduce so we really appreciate your help.
I was quickly able to reproduce the error again in a new blank place using the same URL (https://apis.roblox.com/cloud/v2/users/1 ).
I generated a new API Key and copied it to my clipboard. I ran the URL in my browser (with the x-api-key header using a chrome extension). It worked like usual.
Then, I copied and pasted the new API Key value into the secret. Keep in mind this is the exact same key I copied originally from the dashboard (so it’s not like I saved the local key with an additional space or something)
We have identified that root cause as a platform limitation that restricts the total amount of data that can be stored for local secrets to approximately 2500 bytes.
One quick workaround you can try is to keep only the secrets that are necessary, remove unused entries, and shorten secret names where possible to stay within this limit, though we understand this is not applicable in all scenarios. We are active looking into a longer-term solution.