If you create a set of records through the API, and those records kick off automations when a new record is made (in the table that the API is creating records in)...
Which completely negates the benefit of running through automation.
------------------------------------------------------------------------------------
Let's consider a scenario:
If this were to run in parallel (with an enterprise license with a degree of parallelizm of 10):
But since things run one by one, each one waiting for the full completion of the previous row before it will kick off the next bot run.....
-----------------------------------------------------------------------------------------------------------------------
You can see why parallel processing is so important.
(Note exactly a direct comparison; but you get the point)
-------------------------------------------------------------------------------------------------------------------------------
I would hope that things would process in parallel since the records were made through the API.
@MultiTech wrote:
I would hope that things would process in parallel since the records were made through the API
Well, at that point you would also be Enterprise.
Remember when we talked about this with someone on the team last year and said that API was actually not intended to be open outside Enterprise and it currently is but could be fixed anytime?
I've built functionality that depends on the API records being added in serial. I'm sure others have as well. That's always a big consideration for any change, is what existing things will it break. Not that parallelism here wouldn't be nice.
I wonder if the more important issue is the parallelism of the data source itself. Appsheet can't very well add records in parallel if the source itself can only process them 1 at a time.
User | Count |
---|---|
43 | |
26 | |
23 | |
14 | |
12 |