Do you work with automations in your Base that are triggered by new or changed entries? Then please note the following: If you add or modify more than 50 entries per minute, it may happen that the desired automation actions are not started. The reason for this is the execution limit for automations.
The execution limit for automations
In SeaTable there is a limit to how often an automation can be executed per minute. Specifically, this is 50 automation runs per minute. The limit applies to each automation individually and is reset after one minute.
Normally, this limit can hardly be reached. It becomes critical, for example, if you import more than 50 rows into a table and want to start an automation for each new row .
In the future, there will be an error message if automations cannot be executed due to this limit.
Why is there such a limit?
Each automation consumes system resources, i.e. too many automations at the same time could overload the SeaTable Cloud server. This is to be prevented by the limit.
