Every time I try to clear out my inventory by quickstocking everything into a shop, I get a 504 error. The items do eventually get moved, though it happens slowly, and I can actually refresh my inventory and watch the items disappear over the next 10-20 seconds after the crash.
This has been happening consistently for several months now. I don't know what's changed that could be causing it? Shop size shouldn't be a problem, because the shop is actually significantly smaller than it has been the past few years. And it happens all the time, even when the site is otherwise stable.
I haven't lost any items yet (as far as I know), but it's impossible to check for everything so I really don't know. I'd feel a lot more comfortable if I didn't get the error in the first place.
Does anyone else have this problem? Have the programmers acknowledged it yet?
(Note to the mods: I know there's another active thread about 504s, but I think this is a separate issue. That's why I'm posting it as its own thread.)

I have a shop with over 38k unique items, nearly 54k total, and I get the 504s every. single. time. I also impatiently refresh my inv watching the items go one by one, lol. I'm used to it by now, which is kinda sad. Oh, and it does only happen to bigger shops from what I can tell. I never get the errors when moving things into my smaller ones.
Like you said though, this didn't used to happen. It's only been the past recent months. Actually, I believe it first started around the server change time.
P.S. On a side note, I can assure you that, on my end at least, I never lose any of the items. I know this for a fact 'cause I'm keeping a checklist for hoarding on SL and I check afterwards every time to make sure my totals match up.
Art by ~ Sig by ~- I forgot about the server move. I was thinking this issue started around November, so that's probably what caused it. Good call.

i think it could be timeout limit between cloudflare and subeta server. the quickstock is taking too long to complete, and cloudflare think the connection is lost, even though subeta is still processing the request.