Calling it kafkaesque is giving it too much credit.
So I got no idea what to do to address it. I feel my best option is wait for it to get disabled and try to address it afterwards.
But just closing the bank account will stop auto billing (it's considered a decline). So if you closed the account, it would just stop paying for whatever it is, and then cloud may lock the gcp account until it's paid. (I'm not 100% sure what cloud does with unpaid invoices).
There’s a quote for your general class of query, and there’s a quota for how many can be in flight on a given server. It’s not necessarily about you specifically.
It just leaves a bad taste, and the second a competitor comes along that has an acceptable offering, then I'll move. Just ridiculous gaslighting behavior.
pls send feedback if this is helpful!
The only way we could get it resolved was to (somehow) get a real human at google on the phone because we're in some startup program or something and have some connection there. Then he put in a manual request to bump our quota up.
Google cloud is the most kafkaesque insane system I've ever had the misfortune of dealing with. Every time I use it I can tell the org chart is leaking.