I can say from experience that this almost certainly isn't the root cause and so won't make any difference - I updated mine (when the option was available) and the same error was returned until I went in through the 'base' site (which isn't now available).

I'm afraid, though it might very well be frustrating, it's going to be a case of waiting (and waiting, and waiting, and waiting) until A3 manages to sort this less than edifying mess out.

Acceptable? Absolutely not. Predictable? Probably. Reality? Definitely.