Because you can’t purchase more Automations on the Pro Plan in the event you run out (like integromat/zapier), what happens to your workflow? Is everything halted?
Upgrading to enterprise would not be an option due to extreme price difference.
For example - Say I have my automations set for my entire workflow working great, but I accidentally trigger an automation that uses a ton of unnecessary automations… oops… my fault and understand and wish I can buy more to pay for that mistake, but I can’t.
Now I am out of automations and almost have an entire month left with zero automations :frowning: and all my workflows are stopped.
I just want to find out the “what if” and hope never end up in that situation :slightly_smiling_face:
So, this is precisely why there should be no limits on automations for paid users. Airtable should cherish users who avoid API and glu-factory integrations that pummel servers constantly seeking info about record changes and states. Automations are event-driven and because of this, they are very easy on servers - they fire when – AND ONLY WHEN – something actually changed. Compared with polling integrations, this is a minute fraction of the largely present integration model banging on Airtable today.
In fact, Airtable should be paying users to switch to internally-driven event-based automations.
If Airtable wants to encourage the community to continue to build heavy-handed polling architectures for data interchange they will continue to sustain automation caps.
I agree that this is a great question. I also agree that it would be great to be able to purchase more automation runs.
However, automations is still relatively new, and I suspect that these things take time to roll out.
@Bill.French, while I agree with you about automations within Airtable being less resource intensive versus the glu-factory integrations, I think that a lot of people are creating automations for things that they were not using glu-factories for, things that were not automated before at all.
Running out of automations is yet another factor that people need to take into account when making decisions about using an automation script versus using script app. There are no run limits on when using script app.
Good point. And it’s likely that the vast world of polling processes are not going to be recast with event-driven replacements for some time. But, this is on Airtable; they should have addressed this ages ago. So today …
Should they constrain new innovation by making it guesswork for customers if a new and innovative use of event automation will be (a) sustainable, and (b) affordable?
In my view, the past should not compromise Airtable’s ability to create competitive distance and the customer’s inability to assess or predict whether or not their innovations will fit a given budget.
Another dimension of this is in-platform and out-of-platform calls. Amazon is very clever about data movement across its network boundaries with far more expensive rates when data leaves their data center. They make it almost zero cost to perform compute operations inside the AWS domain. Other PaaS providers (like Airtable) should embrace this approach or force all of us to subsidize the bandwidth costs associated with the few customers who move data into and out of the Airtable realm.
Indeed, but this is a metric that few - even experienced developers - can easily predict. As such, it’s like building a leasing model where you are charged based on the number of times the engine’s cylinders actually fire. We don’t do that to consumers because they would never be able to relate to this metric. Instead, we use something relatable - like miles.
Indeed; same here. The outcome from an automation that fails because of a quota breach is no different than a SaaS platform that is down. And there’s no way to anticipate such “outage” and gracefully fail and recover.
A few notes here because this just happened to us.
I agree with @Bill.French’s comment about how Airtable should have a greater vested interest in supporting Airtable customers who are taking their platform to the max and spending hours and hours of time on their site. Automation runs limits should not be fixed to some arbitrary number, but perhaps proportional to the base size, the dashboards being used, APIs coming in and out, etc.
Upgrading to Enterprise for just a few days so we can keep our optimized operation going is a chore and quite a steep jump in terms of pricing.
I’ve reached out to a few folks to see what kind of support we can get given there are 8 days remaining.
This is precisely the surprise clients are not expecting.
BTW - Google manages quotas at 24 hour intervals. If you breach on any given day, by the next morning you are operational again and why I typically create self-healing processes. With a daily quota you can become aware of scale and activity in near-real-time even if you aren’t the account owner.
Airtable, pretty much, has this model completely wrong but I must also suggest that a lot of script/action creators have a few things wrong as well.
It’s absolutely insane & completely shortsighted that the people at Airtable thought that this was a good idea. The Airtable Team doesn’t give any way for users to purchase more automations in their current monthly cycle… but FORCES PEOPLE TO WAIT UNTIL THE NEXT MONTH FOR IT TO RESET?
Yeah, no thanks, Airtable… my clients will be sticking with Integromat because they can’t put their entire businesses on hold for a month, and Integromat knows how to treat their customers properly. If they run out of automations, Integromat lets them purchase more automations without shutting down operations for the remainder of the month.
And no, we’re not going to spend $3,000 to upgrade to enterprise to get a few extra automations for a few weeks.
None of this should surprise me. Airtable is the “half-baked platform of limitations”.
@Eriks_Reks1 If you need help migrating all of your automations over to Integromat — the superior automation platform with no limitations & an extremely low monthly cost — please feel free to contact me through my website at scottworld.com. I am both an expert Airtable consultant and a Registered Integromat Partner.
(Note that all of my Integromat links contain my personal referral code.)
I agree that the pricing model for automations (especially the inability to purchase a few more runs in a month) has problems. I also agree that developers need to be aware of these limitations when designing solutions that use Airtable automations. Whenever one of my clients is trying to decide between running a script automatically versus from a button, I always bring up this issue.
Integromat has been in business for longer than Airtable, and Airtable only started offering automations half a year ago. By all means, use Integromat now if you have business critical needs. But Airtable is working hard to build out its service, as evidenced by the new alpha features for running an automation on a schedule and having a find records action.
It does seem like Airtable is evolving quickly on this new feature. If they can resolve their pricing problems, they could take back a big chunk of business from Integromat — particularly for automations that people created that only dealt with Airtable itself (i.e. no integrations with external apps).