Failed to Retrieve Containment error
 

I copied a realm to use for a one off adventure this weekend, after I setup the plots, I tried to delete the info storyline from the original AP i copied from.

Now I cannot open the realm and get a
"Failed to Retrieve Containment error" every time I open.

I tried to load from backup but that just seems to have made matters worse.

Any ideas? Has anyone encountered this before?

I've never seen the error before.

It would be best to open a support ticket.

If you haven't made any other changes since you last synced, then you could delete your local database file and just download everything from the cloud again.

Did you get this fixed? i have a PC with the same issue and we cant fix it.

I now have a player with this error.

Both he and I have synced the realm - which is an old one he's looking at out of interest - and nothing seems to have fixed it.

He's also having trouble syncing a second older realm of mine, it's taking 25+ minutes, to the point where he cancelled it because it was taking too long and he had other things he wanted to do with his time.

Do we know why this happens, yet?

Log bugs people. Sticky threat in these forums.

I have logged the bug...I have sent an e-mail to Lone Wolf....I have posted on the FB page.

Still no support or answer to this.

I don't see any posts on our Facebook page, I did stumble across something in the user group, but it's not an official group. I'll see if I can get to the bottom of this for you.:)

@thrumpskin When you reported your bug and/or emailed support, did you receive an automated response with a case number? We can't seem to find your case in our bug tracking system.

For others reading this thread who are getting this error... please open a support ticket, which you can do through this form http://www.wolflair.com/root/bugrepo...ct=realm_works

Please provide the following information:

* Is it a player or GM who is receiving this error
* Did the person receive the error after upgrading Realm Works from an older version, or have they been using newer versions (e.g. build 239 or above) for a while and are just receiving this error now? For reference, build 239 was released on 4/7/2017.

Once we have this information we'll get you sorted out.

@SteveT

I did NOT get an auto response. My mistake on the user group vice your official FB page.

Sent another Bug Ticket just now.

Thanks for the help.