To answer "what triggered it": nothing on your end. A subscription/billing event (for example an invoice cycle, or recovering from a failed/$0 invoice) was incorrectly bumping grandfathered Pro accounts to the newer 24 vCPU/GB limits version, which is exactly why it came back after we set you to 32 and even after you redeployed. You're on 32/32, and we have a fix in review that stops billing events from changing your limits version, so it won't reset again. Sorry for the runaround. — Angelo

Quick follow-up: the underlying fix just merged. The bug was that routine subscription/billing events were re-applying the newer limits version to grandfathered accounts like yours, which is why it kept coming back even after we set you to 32. That's now scoped so the limits version only changes on an actual cancellation, not on re-subscribe or billing cycles. Your 32/32 will stay put now, no more resets. Thanks for your patience through the back-and-forth. — Angelo