Error: Cast member is locked while proxy is in use
 

What does this error mean? This is the third of my players to join my campaign. I created all characters on my account and now I'm transferring control to my players. Characters are all level 2 and include Age of Ashes backgrounds.
Is this because it is a demo account rather than an apprentice? (I'll find out tomorrow what my players did.)
Is this because the character is on stage (I get another error what I try to remove the ranger and animal companion.)

https://herolab.online/campaign/C00Zpats/participants
appBuild: 60329BE
browser: Chrome
browserVersion: 80.0.3987.122
colorDepth: 24
screenSize: 1920x1080
availScreenSize: 1920x1050
platform: Win32
latestApiCalls:

RestCommand - /stage/get-json-bulk
success: true


RestCommand - /campaign/assign-basic-role
success: true


RestCommand - /campaign/get-capsule-bulk
success: true


RestCommand - /campaign/get-single
success: true


RestCommand - /cast/assign-pc-controller
success: false
error: Error: Cast member is locked while proxy is in use

latestRoutes:
/login
/select-character
/campaigns
/campaign/C00Zpats/overview
/campaign/C00Zpats/participants
Mon, 02 Mar 2020 06:58:24 GMT
Error
Cast member is locked while proxy is in use

Error: Cast member is locked while proxy is in use
at new t (https://herolab.online/static/js/mai...60.js:1:548534)
at Object.<anonymous> (https://herolab.online/static/js/mai...0.js:1:2074118)
at r (https://herolab.online/static/js/mai...0.js:1:1647856)
at Generator._invoke (https://herolab.online/static/js/mai...0.js:1:1648902)
at Generator.e.<computed> [as next] (https://herolab.online/static/js/mai...0.js:1:1648035)
at o (https://herolab.online/static/js/mai...0.js:1:2069367)

Solved. I had to transition stage, then I removed the character from the stage and I could then assign control.

As you discovered, when a cast member is actively on the stage, it is locked and cannot be manipulated. Only the separate version that's on the stage - the proxy - is able to be utilized.

That is a backend error message for consumption by the client-side developers and that was not intended to be viewed by users. We'll obviously need to get that sorted out.

Hey there. I thought that it had already been fixed, but yesterday I faced the same problem. Solved it by replacing the proxy I had with these proxies for market research. Tbh, I didn’t make it on purpose. It was the only option left, and it worked. It’s probably the most unique way of fixing that error. Still, I’m really glad it’s worked. So, hope my find will be helpful to some of you here too, guys. Btw, how did you spend this Christmas? Hope you had a great time. Let me know. Best wishes to you all.