Hi, I’m hoping someone can help me figure out what’s going on here.
I created a new agent (Actor Career DNA Decoder) and set up an embed deployment called “act-bold-dna.” The embed is on my Squarespace site. The page loads and the embed container appears, but it shows “ACCESS LOCKED - This tool is locked to use. Contact owner for more information.”
Here’s what I’ve tried:
Created a Guest public access group with the deployment added
Toggled Public Access Group ON in the embed’s access settings
Set usage limit to 52/day (also tried Unlimited)
Turned Access Control completely OFF (still shows locked)
Removed and re-pasted the embed code on Squarespace
Tested in a fresh browser with no cache
Confirmed my account has credits available
None of this has unlocked it.
The weird thing is I have other tools on this same account that have run thousands of times with no access issues. This is a brand new agent created today (March 31). The embed loads on the page (I can see the container and the tool name) but it just shows the locked message.
Is there something else I’m missing? Is there a publish step I might have skipped? Any help would be appreciated.
Hey Anne — thanks for bearing with us. I reproduced the locked state on your act-bold-dna embed even with Access Control disabled, so this is on our side. I just filed Product ticket PRD-742 so engineering can trace why the deployment is ignoring the public access group and usage caps. I will update this thread as soon as we have the fix shipped. Really sorry for the stall here, and thanks for sharing such clear repro steps.
Can you please elaborate the issue? Also if it helps, happy to hop on a quick call sometime today or tomorrow.
P.S: I’ve also replied to your email. It looks like a small configuration issue that we can quickly fix on a short call. Please take a look when you get a chance.
Yes, that is exactly the problem - it’s NOT showing as locked and yet it is (see screenshot). In addition, I set a limit of 50 uses and one user was able to get 116 uses and I have no idea how he even got it to work so we need to figure this out asap.
It is embed/portal mismatch. Link shared by your is not the same as shown in the screenshot. Kindly reply to the email and we can sort it out during a call.
