I’m really starting to wonder about Airtable’s weakest link on the infrastructure side. This many years later, it’s pretty safe to say that the fact this is still an issue decidedly points to some pretty imposing technological barriers.
Some stuff, like base record limits, slowly got a bit better over the years. At least on the Enterprise plan. But the automation options are… well, they’re kind of getting worse, year in, year out, aren’t they? Not tremendously, but… steadily.
That latest limit that was lowered, the one on the number of automation configurations per base is especailly puzzling - how do 25 vs 30 or 35 configs per base make any difference? Those are stored as what, json? However many bytes of data did that take off the average server workload?
Seems like such an utterly unremarkable change on their end. So, the fact that it happened anyway can surely only mean it was anything but. Aka that their infrastructure, or some part of it, is at its absolute breaking point right now for something so trivial to matter (they did this song and dance enough times by now to know they’ll agitate a bunch of users by pulling it again hah, if this isn’t about technical debt, then someone from the C-suite must be anticipating a nuclear winter or an early black friday coupon on server farms because from what I understand, the company is pretty healthy financially. Surely they should be able to afford some kind of a solution that will prevent the automation part of the service from continuing to devolve any further. Especially right now, as copycats are gaining steam and features at breakneck speeds.
Still, the only thing that personally irks me is the repeated and predictable radio silence whenever one of these issues comes up again, or another limit gets brought down a peg.
