Hi Nigel,I guess the point I was confused on is that the server-side script also uses the dev credentials to generate an authToken, but I guess on the server side it creates a unique "session" ID, whereas from the client-side it does not. (Request: PLEASE INCLUDE THIS FACT IN THE NEXT DOCS. This wil...

Thanks for your input, that helps.Yes, setting the "Allow Duplicate User IDs" room setting does seems to have done the trick. Mostly.But I have to say, I didn't quite believe it until I saw the duplicate UserIDs for myself.I thought that because unique user names were being generated ("Daniel Lebor ...

So I tried modifying the CSR app so that it not only logged into each room session sequentially*, but instantiated the AdobeHSAuthenticator instances sequentially as well. Same results. As you can see from the screenshots, as each CSR app logs in, it ejects the CSR whom is already logged into the pr...

So I did as you suggested: changed the MXML instantiation of AdobeHSAuthenticator to actionscript instantiation, to occur every time a new session is started. But it doesn't work. The exact same thing happened.And I think I've nailed down the problem, because I finally have figured the predictabilit...

The customer app on the left is completely separate than the CSR app on the right. So the customer app logging back into the prelobby should not be triggering a Zombie Error in both Customer app AND the CSR app, as described above. And the Customer app logs in and out of rooms sequentially, there ar...

Here's another weird thing it's doing now which it didn't used to. When the connections hold, and I don't get thrown out of rooms as previously described, this now comes up:When the customer is logged into the CSR room, and the CSR removes the user from the room, the same login function used to logo...

And now I'm getting this:Tried it again and the Room Console logged in fine, but that was the first time I'd ever gotten that particular error from the room console...Joseph BaldersonFlex & Flash Platform Developerhttp://joeflash.ca

Okay, I think I finally caught it in the act, so to speak. With logs.First I added some event hooks and visual indicators for the connection status to the rooms in the CSR app:grey = not synchronized/disconnected;green = synchronized/connected;red = an error event.(see screenshots below)I did figure...

It could be that in using STATE_ENDED, the room lands up getting "stuck" in status ended mode when the CSR is booted from the room by the Room Console bug (assuming that's what it is), which could prevent the user from logging back in. But, as you've indicated, the CSR should not be getting booted f...

No worries about the code, just offering in case it helps you debug your Room Console.I'll add a few things to make the debug trace a little more descriptive in indicating events received, and I'll post it tomorrow when I'm in front of my machine again.Thanks again very much for all your help.Joseph...