Airtable has created a harsh and silly brick wall to a deep customer dependency and reliable pathway to get work done. This constraint raises the total cost of ownership while forcing users to create complicated and often brittle solutions to get work done.
Bad Airtable, bad.
If you want to endear customers to your platform, find ways to eliminate surprises unless said surprise is a free fruit basket.
Commentary: Automation Optimization - It’s a Thing
No one ever discusses or ponders their data model, information architecture, or process automation in the context of optimizing such actions. I will bet, there are ways to build your actions in a way that could overcome this constraint. With power like Airtable event handlers and script automations also comes some responsibility to be prudent and smart.
@Marko.Petrovic mentioned the raw limit of 25 automations which I also don’t know off the top of my head, but I do know that automations can be “overloaded” much the way script functions can be designed to perform multiple computations.
Last week an Airtable client hit this exact brick wall; we took 11 separate automations and created a single agile automation that addressed all 11 actions.
Aggregating action processes is one dimension of automation optimization; there is also the number of times an automation fires and a variety of ways to streamline the pace.