So I just transferred two characters to a new realm, one of them seems to be processing normally.
The other is showing an error and says “An error was encountered. Please come back later.”
That’s a rather vague error message and it already deducted the $$ from my b.net balance, so I’m wondering how much later am I supposed to come back and what’s going to happen?
When I was initially processing the xfer it had the option to “transfer with guild” and it was checked off by default and going to the realm I wanted. I thought it was a bit odd since it’s been a long time since I transferred my guild/guild master but what the heck, the option was there and everything looked good.
If trying to use this guild option was the cause of the error, please alert someone to this as I can’t imagine I’m the only one to ever run into this.
If anyone has had similar issues with an error, what should I expect? Will I have to wait out the 45m queue time like my successful transfer has? Will I get a refund of my b.net balance? Will I have to redo the transfer and wait in line again?
I’ll give billing a try, not sure if it is something they can fix but hopefully they can direct me to who can fix it if it’s not them.
The character appears stuck on his current realm, and logging into them again only temporarily clears the error message.
Lol, yeah no idea how I managed to break it so badly. My account page shows the transaction as “complete” in my transaction history. If I log into the character the error message goes away and even lets me do the initial steps for an xfer before getting stuck saying there is a character service is in process.
It also still has the check box for following the guild, even though the guild xfer was back in early Legion.
So two tickets yesterday, billing basically told me to wait “23 hours” before they could assist me.
So now my character is still stuck with some vague error, my b.net balance is still missing the cost of transfer+tax and now the ticket wait times are 3 times longer than yesterday when I had the problem.
I’m going to guess billing is not equipped to actually solve my problem on their own, which I tried to convey to them yesterday but who knows…
I’ll update this thread with a resolution whenever I get one for anyone who gets this error in the future.