Board Game Arena

I don't know if it is just my computer or what but I keep getting this extremely annoying error that says error with notification service or something like that, and then when I go, it says this action is impossible, so I have to reload the page... and it turns out to be the other person's turn still and the other person hasn't gone yet, so it is sort of like my computer is telling the move that my opponent will do ahead of time, which is really weird. It starts getting annoying always having to press the reload button, and my computer is slow. I don't know if this could be fixed or not?

It's not only you.
It happens a lot at Caylus, + ressources displayed are wrong, like -1 cloth.
It's often and very annoying.

It affects everyone and I guess the administrators know and are working on it.

Losing a lot of points playing tzolkin due to missed actions. I take action, end turn, game does not register right action - very frustrating.

Coin-coin le Canapin wrote:It affects everyone and I guess the administrators know and are working on it.

They are working on it? It is getting more common for me now. Now almost every game I play, this happens. Sometimes I can just wait until the timeout thing goes away, and then I can do whatever I need to do in my turn.

Pisaac wrote: They are working on it?

Well, I said "I guess" not "I know"
At least they could shut down the site until the issue is fixed, I don't see the point of keeping BGA available in these circumstances.

Coin-coin le Canapin wrote:

Pisaac wrote: They are working on it?

Well, I said "I guess" not "I know"
At least they could shut down the site until the issue is fixed, I don't see the point of keeping BGA available in these circumstances.

Yes, and they can at least tell us what is happening.
Also, I was playing Can't Stop with the robot, and I had to relaunch that thing three times during one game! It kept stopping, and I had to reload or relaunch or Whatever! It's getting extremely frustrating!

Hi,

As you may have noticed, we manage to fix the issue temporarily on July 28th.

The problem got back on August 5th (with a maximum on August 12th).

Then we manage to set up an "almost permanent" fix. Since August 13th, there is very few errors of this type. As there hasn't been additional comments on this thread since August 12th it looks like we found the cause.

We are working on a last fix to clean the latest remaining "timeout" errors.

Thanks for your patience.