but don't assume everyone still having database errors are just mashing buttons. This is a back end issue, not user error.
I didn't assume anything, I was just giving my best advice to anyone still having issues as I'd noticed there had been no reply from fdev today.
And I never ever said user error was the problem, I implied device error was the problem, not the user, in fact, I assumed users were techno-able, and able to understand all suggestions without detailed instructions, I didn't treat anyone like they were the problem themselves.
And I get your opinion that's its a backend issue, but i had the same error for over 3 hours yesterday, and it wasn't resolved by Support or anything in the back end being changed. I still had the error after thier hotfix was applied when others who had the error were getting their completed transfer emails already.
The only thing that fixed it, was what I did myself on my own, not anything Fdev did.
So again, your opinion that it's backend, doesn't mean it is.. I thought it was too, until I realized chrome, maxthon, edge, ect, all browsers I had, on all my devices, including mobile, were simply not working and tossing the error. So I tried Firefox, making sure it was a fresh install on my phone, changed to my mobile data instead of wifi incase my IP at home was the issue, and made sure to accept all cookies on all pages that I opened, and then, FIRST TRY, it worked without any errors.
So there could be any number of non-user and non-backend issues that is simply between your device and their network that isn't communicating properly in some way, bad data, time out, dropped packets, wrong user signed in according to cookies even though does not appear wrong on your screen.... 10 000 non-backend fdev issues that might only be resolved by the user....
For example, your device might be storing 2 cookies for login status on Frontiers website, and potentially sending the wrong data with your transfer request, so the database is sending a denial response/database error to the user data being sent not matching whats in their database... anyways... too many possibilities for you to claim it's fdev sided responsibilityto fix, when litterally dozens of ppl fixed the same error without fdev yesterday